القائمة
Turn a recent human-agent interaction into a portable workflow description.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Use when working with source control for a project within /home/user/workspace/code or code-agent.
Work through a proposal by starting a tracked /goal, reading the proposal, breaking it into milestone-sized tasks, and delegating each implementation milestone to fresh subagents instead of implementing directly in the main agent. Use when the user wants proposal-driven execution with explicit progress tracking and milestone-by-milestone delegation.
Draft new proposal documents for a codebase in the local proposal style. Use when the user wants a new proposal written before implementation, or wants an idea turned into a structured design/proposal document with motivation, problem statement, proposal, non-goals, verification, and success criteria.
Manage npm package dependencies in this environment. Use when adding or updating npm packages, editing package.json/package-lock.json, or when network access must be constrained to `run-in-nw-sandbox -- npm install --no-scripts [--save | --save-dev] -- package-spec ...` followed by `npm rebuild` outside the sandbox.
How to use the run-in-nw-sandbox helper to run commands with network access
Manage Rust/Cargo dependencies in this environment. Use when adding, updating, or fetching crates, editing `Cargo.toml`, or working within the constraint that the only approved network command is `cargo fetch` via `run-in-nw-sandbox`.
استنادا إلى تصنيف SOC المهني
| name | extract-reusable-process |
| description | Turn a recent human-agent interaction into a portable workflow description. |
| disable-model-invocation | true |
Analyze the recent human-agent interaction and infer the reusable process behind it.
Produce a generic skill description that teaches another agent how to carry out the same kind of work with a human in a different context. Capture the purpose, workflow, decision points, tradeoffs, iteration pattern, and expected output shape.
Do not summarize the specific conversation. Do not mention project-specific names, files, tools, or domain facts unless they are essential examples. Abstract them into general roles and actions.
The description should be actionable: after reading it, a human and agent should be able to collaborate through a similar process and produce a similar type of result.
