troubleshooting-motoko-migrations
Troubleshoot Motoko Migration Failures
Motoko migration errors can conflict with current source code and put deployed state at risk. This reference explains diagnostics and forward-only repairs while preserving migration history.
Instalar com meu Agente
Copie esta solicitação para o seu Agente. Ela inclui a página canônica do Skill e o manifesto.
Review the Skillstore skill "troubleshooting-motoko-migrations" from https://skillstore.io/skills/caffeinelabs-troubleshooting-motoko-migrations.md and its manifest at https://skillstore.io/api/skills/caffeinelabs-troubleshooting-motoko-migrations/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Seu Agente ainda deve apresentar o plano e solicitar qualquer confirmação exigida pela política de segurança.
Recursos legíveis por agentes
Use estes links quando um agente de IA, crawler ou script precisar de contexto limpo em vez de ler a página completa.
Testar
Usando "troubleshooting-motoko-migrations". A write to an applied migration failed while adding a stable field.
Resultado esperado:
- The read-only file represents deployed history and must remain unchanged.
- Express the field addition in a new migration that transforms the current state.
- Confirm the new migration supplies the field before deployment.
Usando "troubleshooting-motoko-migrations". The first migration in a converted project has a non-empty OldActor.
Resultado esperado:
- A non-empty baseline is expected when state predates the enhanced migration chain.
- Preserve the conversion baseline and existing values rather than replacing them with an empty state.
- Compare the baseline with the deployed stable signature if diagnostics remain unexplained.
Usando "troubleshooting-motoko-migrations". The build and checker pass, but installation fails with IC0505 on a long migration chain.
Resultado esperado:
- The diagnostic may indicate that stable-type history exceeds the platform custom-section limit.
- Successful build checks alone do not establish that the artifact can be installed.
- Stop adding migrations and report the platform limit rather than deleting history or retrying the same artifact.
Auditoria de segurança
SeguroAll 37 static findings are false positives: 35 match Markdown backticks, and two misclassify canister installation diagnostics as system reconnaissance. The reference discourages permission bypasses, migration history rewrites, and unsafe configuration changes. No evidence found of prompt injection, credential collection, exfiltration, or malicious execution.
Fatores de risco
⚙️ Comandos externos (35)
Compartilhar e citar este relatório
Compartilhe o relatório de avaliação versionado, o badge neutro, o cartão incorporável e as citações. A Skillstore apresenta evidências sem decidir se este Skill é seguro.
Copiar link do relatório
https://skillstore.io/skills/caffeinelabs-troubleshooting-motoko-migrations/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportBadge Markdown
[](https://skillstore.io/skills/caffeinelabs-troubleshooting-motoko-migrations?utm_source=security_passport_badge)Badge HTML
<a href="https://skillstore.io/skills/caffeinelabs-troubleshooting-motoko-migrations?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/caffeinelabs-troubleshooting-motoko-migrations/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Cartão incorporável
<iframe src="https://skillstore.io/embed/skills/caffeinelabs-troubleshooting-motoko-migrations.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Citações acadêmicas (APA · BibTeX · CFF)
Citação APA
caffeinelabs. (2026). troubleshooting-motoko-migrations security audit report (audit version 1) [Author version 0.1.5]. Skillstore. https://skillstore.io/skills/caffeinelabs-troubleshooting-motoko-migrations/audits/1Citação BibTeX
@techreport{caffeinelabs-caffeinelabs-troubleshooting-motoko-migrations-2026,
author = {caffeinelabs},
title = {troubleshooting-motoko-migrations security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/caffeinelabs-troubleshooting-motoko-migrations/audits/1},
note = {Author version 0.1.5}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "troubleshooting-motoko-migrations security audit report (audit version 1)"
version: "0.1.5"
type: report
authors:
- name: "caffeinelabs"
date-released: "2026-10-02"
url: "https://skillstore.io/skills/caffeinelabs-troubleshooting-motoko-migrations/audits/1"
identifiers:
- type: other
value: "skillstore:caffeinelabs-troubleshooting-motoko-migrations:audit:1"
description: "Skillstore immutable audit report identifier"
Pontuação do Skillstore
Por que esta pontuação Confiança das evidências: MédioO que você pode criar
Explain Unexpected Compatibility Errors
Trace checker fields absent from current source to the deployed stable signature and identify the appropriate pending migration changes.
Review a Converted Project Baseline
Review a non-empty first migration baseline and preserve legacy state when maintaining a converted or forked project.
Investigate Installation Failures
Assess IC0505 installation errors, chain growth, and protected configuration without bypassing platform controls.
Teste estes prompts
Explain this Motoko migration diagnostic: [diagnostic]. Identify likely causes, needed evidence, and safe next steps without changing files.
A write failed on this migration: [filename]. Review [deployment history] and [requested state change]. Distinguish pending from applied changes and propose a forward-only repair.
Review [first migration], [current actor declarations], and [deployed stable signature] for a converted project. Explain the baseline and flag assumptions before proposing changes.
Compare [diagnostics], [migration chain], [mops configuration], and [deployed stable signature]. Assess history consistency and installation risks. Preserve protected configuration and produce an escalation report for unresolved mismatches.
Boas práticas
- Compare diagnostics with the deployed stable signature, not only local source or version history.
- Preserve applied migration identities and consolidate related unapplied changes into one pending migration.
- Keep actor bodies static and stable types lean; escalate unexplained signature mismatches before deployment.
Evitar
- Editing, renaming, deleting, or changing permissions on frozen applied migrations to bypass a failure.
- Replacing a converted baseline with empty state or reseeding fields that contain live data.
- Relaxing protected configuration, removing the chain, or treating successful build checks as proof of installability.
Perguntas frequentes
When should I use this skill?
Does it automatically repair or deploy a canister?
Why does the checker mention fields absent from current source?
Can I edit an already-applied migration?
Can an enhanced migration project return to legacy persistence?
Does a successful build and check guarantee installation?
Detalhes do desenvolvedor
Autor
caffeinelabsLicença
MIT
Versão do autor
v0.1.5
Revisão da Skillstore
r1
Referência
a127f0a133fc1587fa1a973bd2251d5de5be4f4e
Atualidade da manutenção
02/10/2026
Uso
0 downloads · 0 visualizações
Estrutura de arquivos
📄 SKILL.md