skill-ops-planner
Skill7 starsChanged 5 months agoMITView on GitHub
Create an operating policy and roadmap for a live portfolio of Claude Code skills. Use when the user asks to organize, govern, audit, measure, retire, or scale skills already used by a team or repository. Also trigger on "スキルの運用計画", "スキルポートフォリオ", "スキルロードマップ", "スキルを整理して".
In this repository140 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .codex/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- static/llms.txtllms.txt
- ask-codexSkill
- river-review-disciplineSkill
- skill-creatorSkill
- skill-optimizerSkill
- commandsSkill
- adversarial-reviewSkill
- review-teamSkill
- river-review-architectureSkill
- river-review-codeSkill
- river-review-docsSkill
- river-review-frontendSkill
- river-review-performanceSkill
- river-review-security-auditSkill
- river-review-securitySkill
- river-reviewSkill
- river-review-testingSkill
- unknown-coverage-reviewSkill
- Coverage and Failure Path GapsSkill
- Flaky Test Risk CheckSkill
- GitHub Actions Workflow Security ReviewSkill
- Standard Review Policy for DownstreamSkill
- Test Assertion Effectiveness 常に PASS するテストの検出Skill
- Test Presence for Changed CodeSkill
- Test Naming and StructureSkill
- テスト観点レビュー(差分ドリブン)Skill
- a11y Accessible Name BasicsSkill
- Agent Skill Bridge ReviewSkill
- Altitude Generalization GuardSkill
- API Compatibility and Test Gap ReviewSkill
- Assumption Resolution Trace Plan の前提解消トレーサビリティSkill
- Async Correctness 非同期処理の正しさ検証Skill
- Behavior-Structure Separation 振る舞い変更と構造変更の分離・外部挙動維持Skill
- Closure Scope Retention GuardSkill
- Component Variants / States Documentation コンポーネント状態の文書化Skill
- Configuration File ReviewSkill
- Cross-File Leakage リファクタ後の caller 側残骸検出Skill
- Design Source-of-Truth Conformance デザイン定義準拠Skill
- Design System Component Reuse GuardSkill
- Design Token EnforcementSkill
- Detector Detection Power 検査器の検出力の検証Skill
- Documentation Hygiene ドキュメント衛生Skill
- End-to-End Wiring 末端到達・貫通の検証Skill
- Existing-Pattern Conformance 既存パターン準拠の確認Skill
- Firebase Security Rules ReviewSkill
- Fix Scope Integrity 指摘対応ループのスコープ逸脱・前提破壊検出Skill
- GitHubレビューコメント対応(修正案つき)Skill
- Hallucinated Reference 幻覚的参照の実在確認Skill
- Hello Skill (Always-On Sample)Skill
- i18n Unused Key ReviewSkill
- Impact Evidence Coverage 影響・失敗系・外部依存の証拠充足Skill
- Independent Review SynthesisSkill
- Invisible Unicode Injection Scan 不可視 Unicode コード注入検出Skill
- Knowledge-to-Code Alignment 新知識のコード反映・設計知識の保全Skill
- Laravel Eloquent N+1 and Query Efficiency ReviewSkill
- Laravel Mass Assignment and Authorization ReviewSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 40
If any of the above cannot be determined:
- Distinctive: line 42
stop and ask the user for the missing information
- Distinctive: line 43
do not proceed to Phase 1 until at least active skills and current storage layout are confirmed
- Distinctive: line 44
if no inventory exists at all, output an inventory-first plan and stop
- Distinctive: line 129
Create a prioritized roadmap:
- Very specific: line 136
Use ${CLAUDE_SKILL_ROOT}/assets/skill-roadmap-template.md as the output structure.
- Distinctive: line 186
write abstract policy with no operating rules
- Distinctive: line 194
If the team has no current inventory:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Pattern declaration
Primary pattern: Pipeline Secondary patterns: Reviewer, Inversion Why: portfolio planning requires strict phase order (inventory → classify → policy → metrics → roadmap) with review checkpoints at each stage. Inversion is needed at Phase 0 to block progress when inventory data is insufficient.
Purpose
Plan how a team should operate a set of skills over time.
Your job is to define:
- portfolio structure
- ownership
- lifecycle stages
- evaluation policy
- rollout policy
- retirement policy
- review cadence
Phase 0: Portfolio gate
Before planning, identify:
- active skills
- target users or teams
- current pain points
- risk level by skill category
- current review process
- current storage layout
- current evaluation maturity
If any of the above cannot be determined:
- stop and ask the user for the missing information
- do not proceed to Phase 1 until at least active skills and current storage layout are confirmed
- if no inventory exists at all, output an inventory-first plan and stop
Phase 1: Inventory and pattern segmentation
For each skill, record:
- owner
- purpose
- invocation policy (auto vs manual)
- risk level
- primary pattern (Tool Wrapper / Generator / Reviewer / Inversion / Pipeline)
- secondary patterns
- current eval maturity
- review requirement
Output each skill as a structured record:
skill: <name>
owner: <person or team>
purpose: <one line>
invocation: auto | manual
risk: low | medium | high
primary_pattern: <pattern>
secondary_patterns: <patterns or none>
eval_maturity: none | basic | comprehensive
review: <cadence>Then group the portfolio by:
- responsibility type (knowledge / workflow / investigation / review / operational)
- risk type
- design pattern
Phase 2: Lifecycle policy
Define lifecycle stages:
- proposed
- experimental
- team-approved
- production
- deprecated
- retired
For each stage, define:
- entry criteria
- required eval coverage
- review requirement
- allowed blast radius
- logging requirement
- retirement signals (when to deprecate or retire)
Phase 3: Metrics and governance
Define portfolio metrics:
- trigger precision
- task success rate
- review pass rate
- rollback rate
- mean tool count
- failure recurrence
- stale skill count
Pattern portfolio metrics:
- count by primary pattern
- percentage of Inversion usage where ambiguity is common
- percentage of Generator skills with template coverage
- percentage of Reviewer skills with explicit rubric coverage
- percentage of Pipeline skills with checkpoint validation
- percentage of Tool Wrapper skills with maintained references
Also define:
- monthly review cadence
- change approval policy
- emergency disable policy
- documentation freshness policy
Phase 4: Roadmap
Create a prioritized roadmap:
- fix now
- standardize next
- automate later
- retire soon
Use ${CLAUDE_SKILL_ROOT}/assets/skill-roadmap-template.md as the output structure.
Prioritize by:
- impact
- risk
- maintenance burden
- adoption level
Phase 5: Review
Check against:
${CLAUDE_SKILL_ROOT}/references/review-default.md${CLAUDE_SKILL_ROOT}/references/portfolio-policy.md
Verify:
- policy is concrete enough to operate
- lifecycle stages have entry rules
- metrics are measurable
- ownership is clear
- retirement criteria exist
Output format
Return exactly these sections:
Current-state summary
Skill inventory model
Lifecycle policy
Governance rules
Metrics dashboard definition
Pattern portfolio
30-day roadmap
90-day roadmap
Risks and open decisions
Anti-patterns
Do not:
- write abstract policy with no operating rules
- ignore ownership
- ignore retirement
- require eval maturity that the team cannot sustain
- assume all skills should be auto-invoked
Failure handling
If the team has no current inventory:
- provide a lightweight bootstrap policy
- define a minimum viable governance model
- prioritize inventory, naming, and eval basics first
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

