メニュー
Claim a queued task, execute it, record the result on the task, and hand over.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/nicsuzor/academicOps --skill pullコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
| name | pull |
| description | Claim a queued task, execute it, record the result on the task, and hand over. |
Each task was vetted before it became available. Execute it faithfully: it is the whole of your obligation and the limit of your authority.
Work counts only once it is recorded on the task. In an ephemeral container or worktree your changes exist nowhere else — halt without completing the handover and they are destroyed.
Claim your task through the knowledge base and synchronise it with your internal TODO list.
The claimed task is your unit of delivery, children included. Existing children are input to your plan: execute them directly in sequence or in parallel where the work allows. The return contract attaches to the claimed task — one deliverable, with evidence and an output URL — never a spray of per-child deliverables.
Track every step and deliverable on your native task list, including all outstanding subtasks, then a verification step, and finally "Handover".
Execute the steps systematically, sequencing in parallel where the work allows.
Refuse and attempt. Refuse any choice not derivable with reasonable confidence from the axioms plus the context you were given — that is the same limit on your authority, applied to decisions. Attempt everything that does not depend on a refused choice, then take dump's partial path.
Failures are routine and provide valuable information.
Complete what steps you can and cut at a clean seam. Mark what is incomplete and why.
Check your work against the literal requirements and acceptance criteria set out in the task, and carry the evidence for each into the report you hand back — the brief's evidence bar is what your claims are admitted against. Technical compliance is not sufficient and quality assurance is not a checklist; the bar is excellence. Rectify what falls short.
Do not certify a task complete without certainty that it is delivered in full.
Invoke the dump skill. It records your work and lets the task proceed to the next stage.
dump skill or your work will be DESTROYED.Standing experiment protocol for the academicOps project — every piece of real work is also evidence about the framework. Use when starting framework work of any type, testing instructions blind, trialling a runtime mechanism, or reviewing how well the framework served a task just completed.
Creating diagrams in any style — Mermaid flowcharts (structured, code-based) or Excalidraw (hand-drawn, organic). Use style parameter to select.
Use when driving a framework run you intend to score — choosing a surface, dispatching a worker, or when asked to "debug a polecat", "run a polecat container interactively", "attach to a polecat session", "check polecat logs", or to verify that a change to plugins, hooks, lib/, skills, or the Dockerfile actually works inside a real container. Spins up a `polecat run` container under tmux for live interaction, says where the durable host-side session state lands, and walks the layered check that separates "installed in the image" from "actually fires".