菜单
Upload files and reference them correctly in Mighty specs/tasks/decisions. Use when asked to attach screenshots, logs, PDFs, or other file artifacts and ensure they are represented in both rich text and graph evidence links.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Upload local screenshot/video artifacts from agent runs and return renderable file embeds (`![[file ...]]`) plus `mighty-file:` refs for thread UI previews.
Use when the user uploads files or a .zip archive (like user research or logs). Describes how to locate attached files in the sandbox, extract archives if necessary, synthesize findings, and save results back to Mighty.
Record durable architectural or policy choices with `mt decision`. Use when choosing between alternatives, setting lasting constraints, superseding an accepted decision, or capturing significant rationale while context is fresh.
Use when a workstream needs a reviewable deliverable, especially a GitHub PR. Covers `mt pr` for the normal PR-backed path, `mt artifact create` for existing deliverables, and the workstream delivery contract that hands PRs into review and merge gates.
Use when asked to write, migrate, or organize long-form Mighty docs, or decide whether something should be a doc or a spec/task/decision. Covers `mt doc` authoring, doc types, and when guides or runbooks should live in the Mighty graph instead of standalone repo markdown.
Use Mighty-native eval primitives from external repos. Covers the native eval record model, local or hosted write-back flows, and when to reach for the deeper `external-evals` skill for framework-specific mapping.
| name | evidence |
| description | Upload files and reference them correctly in Mighty specs/tasks/decisions. Use when asked to attach screenshots, logs, PDFs, or other file artifacts and ensure they are represented in both rich text and graph evidence links. |
Use this workflow when a spec/task/decision needs concrete file evidence (screenshots, exports, logs, docs).
mt file upload <path>
Notes:
mt upload <path> is also supported.file_id and ref (mighty-file:<file_id>).![[file <file_id>]][[file <file_id>]]Use the block form for screenshots and visual evidence unless inline is explicitly preferred.
Attach artifact evidence to the relevant entity (spec/task/decision):
mt link --from <id> --rel documented_by --to-type file --to-ref mighty-file:<file_id> -d "Screenshot or supporting artifact"
If the file is primary implementation/test evidence, use the relation that best matches intent (implemented_by, tested_by, etc.).
mt file download <file_id>mt file download --spec <spec-id>mt file download --spec <spec-id> --out-dir .mighty/filesmt show <id> should surface the file reference/evidence link.![[file ...]] or [[file ...]].