스킬 migrating-motoko-actors

📦

migrating-motoko-actors

Name: migrating-motoko-actors
Author: caffeinelabs

v0.2.6 콘텐츠 리비전 r1 안전 ⚙️ 외부 명령어🌐 네트워크 접근📁 파일 시스템 접근

Migrate Motoko Actors With Enhanced Migration Chains

Motoko canister upgrades can fail or lose data when state changes do not match migration inputs and outputs. This skill guides compatible changes, self-contained migrations, and validation for enhanced migration chains.

지원: Claude Codex Code(CC)

🥈 80 실버

Maintain this Skill? Claim it 🥈 80 실버

내 에이전트로 설치

이 요청을 에이전트에 복사하세요. 공식 Skill 페이지와 매니페스트가 포함되어 있습니다.

에이전트 요청

Review the Skillstore skill "migrating-motoko-actors" from https://skillstore.io/skills/caffeinelabs-migrating-motoko-actors.md and its manifest at https://skillstore.io/api/skills/caffeinelabs-migrating-motoko-actors/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.

에이전트가 읽기 쉬운 리소스

AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.

Markdown 상세 GET /skills/caffeinelabs-migrating-motoko-actors.md 서명된 manifest GET /api/skills/caffeinelabs-migrating-motoko-actors/manifest 서명된 lockfile GET /api/skills/caffeinelabs-migrating-motoko-actors/lockfile

테스트해 보기

"migrating-motoko-actors" 사용 중입니다. An enhanced migration project adds an optional assignee field to every stored task.

예상 결과:

Use an explicit migration that preserves existing task values and initializes each assignee as absent. Extend the pending migration if one already exists.

"migrating-motoko-actors" 사용 중입니다. A canister changes a stable numeric field from Nat to Int.

예상 결과:

This is usually a stable-compatible widening and does not need an explicit migration. Confirm the deployed signature and run the compatibility check.

"migrating-motoko-actors" 사용 중입니다. A canister renames artist to artists and changes the value from text to a set.

예상 결과:

Transform the old text value into a single-item set for the renamed field. Inline both state types and preserve all unrelated fields.

보안 감사

안전

v1 • 2026. 10. 2. 버전별 보고서 열기

All 77 static findings are false positives involving Markdown formatting, legitimate mops validation commands, official documentation links, and Motoko type notation. The relative import example explicitly prohibits project imports rather than performing path traversal. No evidence found of prompt injection, credential access, unauthorized data transmission, or malicious migration intent in the two reviewed files.

스캔된 파일

397

분석된 줄 수

검토 항목

오탐 무시됨

위험 요인

⚙️ 외부 명령어 (50)

🌐 네트워크 접근 (2)

SKILL.md:276 SKILL.md:277

📁 파일 시스템 접근 (1)

SKILL.md:43

가장 최근에 완료된 정적·의미론적 감사에서 확인된 보안 발견 사항이 감지되지 않았습니다. 이는 스킬에 부작용이 없음을 증명하지 않습니다.

감사자: codex

이 보고서 공유 및 인용

버전이 지정된 평가 보고서, 중립 배지, 임베드 카드 및 인용을 공유하세요. Skillstore는 근거를 보고하지만 이 Skill의 안전 여부를 판단하지 않습니다.

버전별 보고서 열기

보고서 링크 복사

https://skillstore.io/skills/caffeinelabs-migrating-motoko-actors/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 배지

[![Skillstore security assessment](https://skillstore.io/badges/skills/caffeinelabs-migrating-motoko-actors/security.svg)](https://skillstore.io/skills/caffeinelabs-migrating-motoko-actors?utm_source=security_passport_badge)

HTML 배지

<a href="https://skillstore.io/skills/caffeinelabs-migrating-motoko-actors?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/caffeinelabs-migrating-motoko-actors/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

임베드 카드

<iframe src="https://skillstore.io/embed/skills/caffeinelabs-migrating-motoko-actors.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

학술 인용 (APA · BibTeX · CFF)

APA 인용

caffeinelabs. (2026). migrating-motoko-actors security audit report (audit version 1) [Author version 0.2.6]. Skillstore. https://skillstore.io/skills/caffeinelabs-migrating-motoko-actors/audits/1

BibTeX 인용

@techreport{caffeinelabs-caffeinelabs-migrating-motoko-actors-2026,
  author = {caffeinelabs},
  title = {migrating-motoko-actors security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/caffeinelabs-migrating-motoko-actors/audits/1},
  note = {Author version 0.2.6}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "migrating-motoko-actors security audit report (audit version 1)"
version: "0.2.6"
type: report
authors:
  - name: "caffeinelabs"
date-released: "2026-10-02"
url: "https://skillstore.io/skills/caffeinelabs-migrating-motoko-actors/audits/1"
identifiers:
  - type: other
    value: "skillstore:caffeinelabs-migrating-motoko-actors:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore 점수

이 점수의 이유 증거 신뢰도: 중간

아키텍처

100

유지보수성

콘텐츠

커뮤니티

사양 준수

만들 수 있는 것

Understand stable state changes

Classify proposed field changes and identify when an enhanced migration file is necessary.

Write a migration module

Draft self-contained state transformations while preserving unchanged fields and using the existing pending migration.

Review upgrade readiness

Check chain ordering, deployed signatures, intentional data removal, and validation steps before releasing an upgrade.

이 프롬프트를 사용해 보세요

Classify a state change

My project uses enhanced Motoko migrations. Classify these stable field changes as implicit or explicit: [changes]. Explain each decision.

Plan a new field

Add this stable field in my enhanced migration project: [field and type]. Review [existing chain] and propose initialization without modifying applied migrations.

Transform stored records

Using [old fields], [new fields], and [business rules], draft a self-contained Motoko migration. Preserve unchanged state and explain every default and discarded field.

Audit an upgrade plan

Review [migration plan], [deployed signature], and [mops configuration]. Check stable compatibility, chain ordering, pending limits, fresh installation, and data preservation. Propose validation steps.

모범 사례

Derive old state from the preceding migration; use empty state only for a new chain, not a legacy conversion.
Keep applied migrations unchanged and fold new work into the pending file.
Run compatibility checks before building and test the upgrade with representative state.

피하기

Do not add a migration for a stable-compatible change or an identity transformation.
Do not apply the enhanced-chain initializer rules to plain actors without a migration chain.
Do not import project types into frozen migration files or discard fields unintentionally.

자주 묻는 질문

When is an explicit migration required?

In enhanced migration projects, use one for renamed, removed, narrowed, transformed, or newly added stable fields.

Can I change field mutability without a migration?

Yes. Changing var to let, or the reverse, is usually stable-compatible.

Where should migration files live?

Read the chain directory in mops.toml. The default location in this guide is src/backend/migrations/.

Why must migration types be inlined?

Project type imports can change and invalidate historical transformations. Inline old and new types; core and mops package imports are permitted.

How do I initialize a new stable field?

Under enhanced migration, declare its type in the actor and supply its value from the migration output. Plain actors follow different initialization rules.

Does this skill deploy my canister?

It does not include a deployment script. It guides migration authoring, compatibility checks, and builds; deployment still requires your project workflow.