스킬 writing-motoko

📦

writing-motoko

Name: writing-motoko
Author: caffeinelabs

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

Write Modern Motoko Backends

Outdated Motoko examples can cause compiler errors and unsuitable backend designs. This skill provides modern language references, modular actor patterns, and mops dependency workflows.

지원: Claude Codex Code(CC)

⚠️ 38 나쁨

Maintain this Skill? Claim it ⚠️ 38 나쁨

설치 전에 중지하고 확인을 요청하세요.

계획을 검토하고 파일을 변경하기 전에 사용자의 명시적 동의를 받으세요.

내 에이전트로 설치

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

에이전트 요청

Review the Skillstore skill "writing-motoko" from https://skillstore.io/skills/caffeinelabs-writing-motoko.md and its manifest at https://skillstore.io/api/skills/caffeinelabs-writing-motoko/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

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

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

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

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

테스트해 보기

"writing-motoko" 사용 중입니다. How should I organize a blog canister with mutable users and posts?

예상 결과:

Keep entity types in the schema module and domain methods in separate user and post modules.
Inject only required state into each API mixin, and keep the actor as the composition root.
Return immutable views. Restrict public lists to published posts and authorize access to drafts.
Initialize durable state through the configured migration chain before running compiler checks.

"writing-motoko" 사용 중입니다. A Nat-keyed map operation reports that the compiler cannot determine compare. What should I check?

예상 결과:

Import the core Nat module in the file performing the map operation.
Map operations resolve their implicit comparator from the imported key-type module.
Verify the operation signature, then rerun the mops check after fixing the import.

"writing-motoko" 사용 중입니다. Which return type should a booking endpoint use for expected caller errors?

예상 결과:

Return a typed result with an immutable success view and an error variant.
Use separate error tags for authorization failures, unknown rooms, and occupied slots.
Reserve traps for broken invariants and options for normal absence.

보안 감사

높은 위험

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

All 383 static findings are false positives involving Markdown backticks, language identifiers, relative module imports, or the mops documentation link. Three semantic risks affect example applications: unrestricted timer scheduling, unpublished post visibility, and anonymous callers sharing todo ownership. No evidence found of malicious execution, credential exfiltration, or audit-directed prompt injection.

스캔된 파일

2,684

분석된 줄 수

검토 항목

오탐 무시됨

확인된 보안 우려 사항 (3)

높음

examples.md:619-637

Unrestricted Recurring Timer Controls

Public startPeriodicCleanup schedules recurring work without authorization and overwrites timerId without cancelling earlier timers. Any caller can accumulate background jobs or stop cleanup.

Both public controls lack caller checks, and each start replaces the handle without cancelling the previous recurring timer. This enables resource abuse if deployed.

중간

examples.md:163-175 examples.md:184-191 examples.md:281-283

Public Query Exposes Unpublished Posts

New posts start unpublished, but getAllPosts returns every post through toView, including content and author details. This bypasses draft visibility if publication controls access.

The public query has no publication filter or caller restriction, and the projection includes content. Confidentiality impact depends on the application's intended draft policy.

중간

examples.md:673-702

Anonymous Callers Share Personal Record Ownership

addTodo stores caller as owner without rejecting anonymous callers. Unrelated anonymous clients share that principal and can read or toggle each other's anonymous-owned todos.

All three endpoints rely on caller equality without an anonymous check. Anonymous clients therefore satisfy the same ownership condition despite being unrelated users.

위험 요인

⚙️ 외부 명령어 (50)

📁 파일 시스템 접근 (14)

examples.md:118 examples.md:157 examples.md:200 examples.md:201 examples.md:245 examples.md:246 examples.md:291 examples.md:292 examples.md:579 SKILL.md:145 SKILL.md:313 SKILL.md:314 SKILL.md:325 SKILL.md:333

🌐 네트워크 접근 (1)

SKILL.md:54

감사자: codex

이 보고서 공유 및 인용

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

버전별 보고서 열기

보고서 링크 복사

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

Markdown 배지

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

HTML 배지

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

임베드 카드

<iframe src="https://skillstore.io/embed/skills/caffeinelabs-writing-motoko.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). writing-motoko security audit report (audit version 1) [Author version 0.2.9]. Skillstore. https://skillstore.io/skills/caffeinelabs-writing-motoko/audits/1

BibTeX 인용

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

CITATION.cff

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

Skillstore 점수

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

아키텍처

100

유지보수성

콘텐츠

커뮤니티

사양 준수

만들 수 있는 것

Build a First Motoko Service

Use modern syntax and shared API types to organize a small backend into domain modules, mixins, and actor state.

Repair Backend Compile Errors

Compare failing collection calls, imports, and conversions against the supplied signatures and diagnostic guidance.

Align APIs With Client Bindings

Define immutable response views and caller-scoped endpoints before using generated backend bindings in a client application.

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

Explain Modern Motoko

Explain query versus update functions and shared response types for a simple Motoko todo service. Use this skill's supported toolchain assumptions.

Design a Modular Backend

Design a Motoko backend for [domain]. Separate types, domain helpers, API mixins, and actor state. Identify authorization rules and migration prerequisites.

Fix a Compiler Diagnostic

Resolve [compiler diagnostic] in [source excerpt]. Verify relevant core signatures, preserve behavior, and propose focused mops checks without changing platform-managed flags.

Implement Caller-Scoped Services

Implement [service] using injected state, immutable views, and typed errors. Reject anonymous personal-record access. Bound privileged operations and include negative authorization tests.

모범 사례

Verify toolchain versions and uncertain core APIs against the supplied references before implementing changes.
Define backend authorization and visibility policies, then test anonymous, unauthorized, and repeated privileged calls.
Use mops for dependency changes, iterate with compile checks, and build only after checks pass.

피하기

Copying example services into production without reviewing authentication, publication rules, and recurring resource costs.
Guessing JavaScript-style collection methods or mixing deprecated base APIs with modern core conventions.
Changing persistent actor state without migration guidance or manually editing dependency lockfiles.