القائمة
Upload local screenshot/video artifacts from agent runs and return renderable file embeds (`![[file ...]]`) plus `mighty-file:` refs for thread UI previews.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
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.
| name | artifacts |
| description | Upload local screenshot/video artifacts from agent runs and return renderable file embeds (`![[file ...]]`) plus `mighty-file:` refs for thread UI previews. |
Use this when a run produces local files (screenshots, recordings, logs) and the final response should show those artifacts directly in the Mighty message UI.
ls -l /tmp/agent-browser-local-stack.png
If files are missing, state that explicitly and do not claim upload success.
mt file upload <path>
Capture:
file_idref (mighty-file:<file_id>)mighty-file:<file_id> in final_result.artifacts (or equivalent artifact list).mighty-file:<file_id> (do NOT wrap it in markdown backticks).![[file <file_id>]]
Use block embeds for screenshots/videos so thread UI can render previews.
When work is tied to a spec/task/decision, add a graph evidence edge:
mt link --from <id> --rel documented_by --to-type file --to-ref mighty-file:<file_id> -d "Run artifact"
mt file download <file_id> --out-dir /tmp![[file <file_id>]].