菜单
Use when creating a new local skill or fixing an existing skill that was saved to the wrong skills tree. Symptoms - a skill was written under ~/.claude/skills, the active setup uses ~/.agents/skills, or skill instructions still reference the old path convention.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Audit godmode skills, agents, and plugin files for internal consistency, broken references, stale commands, and cross-skill contradictions. Use when asked to "introspect", "audit the skills", "review godmode", or after adding new skills.
Use at the start of every conversation to orient to available skills and workspace rules. Replaces superpowers entirely. Triggers on session start, "/godmode", or "what skills do you have".
Generate and maintain a `.ctx/godmode/memory-bank/` directory that captures project context backed by source code. The memory bank is injected into prompts via lifecycle hooks and updated incrementally as work progresses. Use when starting a new project, onboarding to an unfamiliar codebase, or when context drift is detected.
Patterns and techniques for adding governance, safety, and trust controls to AI agent systems in Rust. Use this skill when building agents that call external tools, implementing policy-based access controls, adding semantic intent classification to detect dangerous prompts, creating trust scoring systems for multi-agent workflows, building audit trails, or enforcing rate limits and content filters. Covers policy composition, tool wrappers, trust decay, and JSONL audit trails — all in Rust.
Parse git history into structured changelogs. Use to generate release notes, audit commit conventions before tagging, or integrate with `godmode release` workflow.
Dead code detector for Rust workspaces. Finds unused public API surface, orphaned test helpers, stale feature flags, and plugin artifacts referencing removed CLI subcommands. Cross-references pub exports against call sites across the workspace.
| name | agents-skill-save |
| description | Use when creating a new local skill or fixing an existing skill that was saved to the wrong skills tree. Symptoms - a skill was written under ~/.claude/skills, the active setup uses ~/.agents/skills, or skill instructions still reference the old path convention. |
Use this when you need to save a new skill into the active local skills tree, or when an existing skill still points at the older ~/.claude/skills/ layout.
It is especially useful after creating a skill from session work and needing to place it in the right directory the first time.
# 1. Confirm the active skills tree
ls -la ~/.agents ~/.agents/skills
# Use Glob tool: glob '/Users/joe/.agents/skills/**/SKILL.md'
# 2. Inspect the existing skill content before changing it
sed -n '1,260p' /path/to/SKILL.md
# 3. Create the destination directory for the skill
mkdir -p ~/.agents/skills/<skill-name>
# 4. If the skill was saved to the wrong tree, move it
mv ~/.claude/skills/<old-path>/SKILL.md ~/.agents/skills/<skill-name>/SKILL.md
# 5. Patch stale path references inside skill docs
# Replace ~/.claude/skills/... with ~/.agents/skills/...
# Remove invented personal namespaces unless the tree already uses them
# 6. Verify the final file
sed -n '1,220p' ~/.agents/skills/<skill-name>/SKILL.md
| Symptom | Fix |
|---|---|
~/.agents/skills exists but the new skill was written under ~/.claude/skills | Move the file into ~/.agents/skills/<name>/SKILL.md and remove the misplaced copy |
Skill text still mentions ~/.claude/skills/ | Patch the instructions so future skill writes follow the active tree |
Unsure whether to use a personal namespace like joe/ | Do not invent one unless the existing ~/.agents/skills/ tree already uses it |
| Parent directory does not exist | Create it first with mkdir -p ~/.agents/skills/<skill-name> |
| Not sure whether a manifest must be updated | Check ~/.claude/plugins/ and ~/.agents/ metadata only if the current setup actually uses registration |