메뉴
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 직업 분류 기준
Guide for creating, configuring, and leveraging Mighty actions (action_def), specifically focusing on sandbox_command bindings and the use of setup/teardown commands to execute safe repo-local operations. Use when users ask to define actions, leverage setup_commands/teardown_commands, or understand the action execution model.
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.
Use the `mt` tool to work with this repo’s Mighty graph: run `mt prime` at session start; prefer `mt search`/`mt tree`/`mt show` before reading code; create specs/decisions/tasks and link evidence; triage `mt inbox`; and close out with `mt closeout` then `mt commit`. For full workflow + templates, run `mt prime`.
Plan work using Mighty (mt) by creating/updating specs and recording decisions, then spawning/structuring implementation tasks. Use when asked to plan/outline/break down a change, draft a spec (feature/rule/invariant/bug), record an ADR-style decision, or turn a fuzzy request into a structured Mighty spec tree with linked tasks.
Track and execute implementation work using Mighty (mt) tasks, with progress comments, linked evidence, recorded decisions, and clean closeout. Use when asked to fix a bug, implement a feature/refactor, or “work through” changes in code while keeping Mighty tasks/specs/decisions updated.
| name | file-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 ...]].