القائمة
Scan a PAS project and fix any gaps between its current state and what the installed plugin version expects.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when creating a local agent for a pas-clief workspace. Walks the user through naming the agent, defining its role, listing its skills, and writing CLAUDE.md and CONTEXT.md from templates. The agent lands in `library/agents/<name>/`.
Use when drafting and publishing a newsletter issue. Walks research → draft → publish phases, using the writer agent. Example library process for pas-clief — copy or extend it for your own use.
Use when applying a workspace's drafting conventions to written output — voice, format, sentence rhythm, the things that make output feel like it belongs to this project. Reads the workspace's style notes if any and adjusts the draft accordingly.
Use when line-editing a draft for clarity and economy. Tightens sentences, removes filler, rewrites awkward constructions, ensures every sentence earns its keep. Apply this skill on the final pass before output.
Use when an agent needs to gather sources or background information from the web for a topic. Produces a concise sources file with URLs, summaries, and the most relevant excerpts.
Use when checking that a pas-clief workspace is current with the latest plugin conventions, or when migrating from an older version. Walks a checklist of structural and template changes and offers to apply each.
| name | upgrading |
| description | Scan a PAS project and fix any gaps between its current state and what the installed plugin version expects. |
Declarative upgrade: define what PAS expects, scan the project, fix gaps. No version tracking needed — just "does your setup match what the current plugin expects?"
The current PAS plugin expects these conditions. Each item has a check and a fix.
.pas/workspace/ exists. No .pas/config.yaml, no .pas/processes/, no .pas/library/. Feedback defaults read from the plugin-level ${CLAUDE_PLUGIN_ROOT}/pas-config.yaml..pas/config.yaml + possibly .pas/processes/ with old process copies..pas/config.yaml (backward-compat still honored), but delete .pas/processes/ / .pas/library/ if they shadow skills that now come from an installed plugin. Back up first. Verify each process: if the plugin marketplace ships the same process, delete the consumer copy..pas/workspace/ exists and contains execution state.workspace/ at project root.workspace/ to .pas/workspace/./pas:pas, cwd is inside a marketplace repository (has .claude-plugin/marketplace.json at its root)./pas:pas from inside your marketplace instead; hooks still route feedback from anywhere).bootstrap-marketplace skill to scaffold one..pas/library/ directory (processes reference ${CLAUDE_PLUGIN_ROOT}/library/ directly).pas/library/ or library/ with copied plugin skills${CLAUDE_PLUGIN_ROOT}/library/, then remove the local library copy. Back up to .pas/library.bak/ before deleting..claude/skills/*/SKILL.md files reference ${CLAUDE_PLUGIN_ROOT}/library/orchestration/ for lifecycle and patterns.pas/library/orchestration/ or library/orchestration/${CLAUDE_PLUGIN_ROOT}/library/ in each thin launcherprocess.md lifecycle sections reference ${CLAUDE_PLUGIN_ROOT}/library/orchestration/lifecycle.md.pas/library/orchestration/lifecycle.mdprocess.md.bak suffixed locations