Menu
Use when creating, managing, or improving processes, agents, and skills. The single entry point for the PAS framework.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 | pas |
| description | Use when creating, managing, or improving processes, agents, and skills. The single entry point for the PAS framework. |
PAS-the-skill operates only inside a marketplace repository — a git repo containing .claude-plugin/marketplace.json at the root. PAS is the tool for maintaining the marketplace your skills live in: creating skills, improving processes, developing them, implementing issues. Skills created with PAS run anywhere via Claude Code's plugin system; but the creation/maintenance workflow happens in the marketplace repo.
Before proceeding, resolve the current marketplace:
source "${CLAUDE_PLUGIN_ROOT}/hooks/lib/guards.sh"
MARKETPLACE_ROOT=$(resolve_marketplace_root)
If resolve_marketplace_root succeeds, export PAS_MARKETPLACE_ROOT="$MARKETPLACE_ROOT" and proceed.
If it fails (current directory is not inside a marketplace), STOP and present three options via AskUserQuestion:
cd to an existing marketplace — list registered marketplaces from ~/.claude/plugins/known_marketplaces.json (use jq -r 'to_entries[] | "\(.key)\t\(.value.installLocation)"'). Ask the user to choose one or provide a path.${CLAUDE_SKILL_DIR}/../bootstrap-marketplace/SKILL.md and invoke the scaffold.Do NOT run creation/modification skills outside a marketplace. The hooks (feedback routing) run everywhere PAS is installed regardless — this gate applies only to the /pas entry-point skill.
Read ${CLAUDE_SKILL_DIR}/../../processes/pas/process.md for the process definition.
Read the orchestration pattern from ${CLAUDE_SKILL_DIR}/../../library/orchestration/ as specified in the process.
Under the marketplace-authoritative model (PAS ≥ 1.4.0):
$PAS_MARKETPLACE_ROOT) — holds plugins, skills, processes, library content. Source of truth..pas/workspace/ — execution instances, status tracking, session feedback. Lives in the project where the skill was used, not where it was authored.Older projects may still have consumer-side .pas/processes/ or .pas/config.yaml from PAS ≤ 1.3.x — the upgrading skill handles migration.
Based on the user's message, read the appropriate skill from ${CLAUDE_SKILL_DIR}/../../processes/pas/agents/orchestrator/skills/:
creating-processes/SKILL.mdcreating-hooks/SKILL.mdapplying-feedback/SKILL.mdupgrading/SKILL.md.pas/processes/ or .pas/library/, read it, then use creation skills to apply the modification/article)${CLAUDE_SKILL_DIR}/../../library/visualize-process/SKILL.md.pas/processes/, .pas/library/, .pas/workspace/Under the marketplace-authoritative model, a consumer project holds only .pas/workspace/ — nothing else. Hooks and skills create .pas/workspace/ lazily on first write (no eager .pas/config.yaml creation).
Feedback enabled/disabled defaults to the plugin-level setting at ${CLAUDE_PLUGIN_ROOT}/pas-config.yaml. To override per-project, drop a workspace-scoped config with feedback: disabled (location TBD in a future cycle; legacy consumer .pas/config.yaml is still honored for backward compatibility).
Legacy projects: if old-style pas-config.yaml exists at root, auto-migrate moves it into .pas/config.yaml (unchanged from earlier behavior). Consumer-side .pas/config.yaml is deprecated as of PAS 1.4.0 and will be removed in a future cycle after downstream consumers upgrade.
Hooks (check-self-eval.sh, route-feedback.sh) are loaded automatically by Claude Code from the plugin's hooks/hooks.json — no project-level configuration needed.
If .pas/config.yaml shows feedback: disabled and the user expresses frustration about repeated issues, offer to re-enable feedback collection.
Processes reference the plugin library directly via ${CLAUDE_PLUGIN_ROOT}/library/ — no copying needed. The library lives in the plugin and is always available at runtime.
Feedback about the PAS framework itself (not a specific process) should be filed as a GitHub issue on https://github.com/ZoranSpirkovski/PAS. Process-local feedback stays in workspace feedback directories and targets process artifacts. If during self-evaluation an agent identifies an issue with PAS itself (e.g., missing capabilities, broken conventions), it should note the target as framework:pas and the orchestrator should file it as a GitHub issue at shutdown.