opportunity-scan
Scan how you actually work with your coding agent and surface what to encode next. Point it at ONE run's artifacts to find what would have prevented a specific failure (the reactive loop — 'that went wrong, what should change in the AI layer?'), or at a window of session logs to find recurring patterns worth building (the proactive scan). Agent-agnostic. Outputs a shape-only HTML report. Use to evolve your system from real usage.
coleam00 · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add coleam00/skills --skill opportunity-scan技能说明
name: opportunity-scan argument-hint: "<a run's artifacts | a logs dir + window> [your steer] [agent docs url]" description: "Scan how you actually work with your coding agent and surface what to encode next. Point it at ONE run's artifacts to find what would have prevented a specific failure (the reactive loop — 'that went wrong, what should change in the AI layer?'), or at a window of session logs to find recurring patterns worth building (the proactive scan). Agent-agnostic. Outputs a shape-only HTML report. Use to evolve your system from real usage."
Opportunity Scan — find what to change, from what actually happened
Reads your agent's own capabilities plus one target you choose, and recommends which primitive each finding should become. Agent-agnostic (Claude Code, Codex, PI, …). It maps what it finds to the full primitive palette (rules · skill · hook · subagent · MCP · automation/workflow), and it works for any agent because it learns that agent's capabilities first.
Two targets, one skill — this is the whole design:
- A run → the REACTIVE loop. Something just went sideways in a loop you ran. Point the scan at that run's artifacts and ask "what in the AI layer would have prevented this?" You fix the system, not the code.
- A window of logs → the PROACTIVE scan. Nothing is broken. Point it at weeks of sessions and ask "what do I keep doing by hand that should be encoded?"
Same skill, same output shape — you're just changing what it reads.
This is a discovery tool — what to change — NOT a quality eval (whether a built thing is good). Keep the two separate.
Inputs — required first, then optional
Read $ARGUMENTS as prose, not as positional slots. Only input 1 is required. Input 2 is free-form and will
contain spaces, so never split arguments on whitespace and never bind them by position — a steer typed without
quotes is still one steer. If something is missing, ask for it once, in a single message, not one question
at a time.
-
What to scan (required) — exactly one of:
- A RUN (reactive) — the artifacts one loop left behind: the plan, the implementation report, an RCA, the PR body, the review output, the commits/diff. Add that run's session log too if you can point at it. These are already scoped to the run, so there's no session-hunting to do.
- A WINDOW OF LOGS (proactive) — where your agent keeps session logs, plus how far back. Examples: Claude
Code →
~/.claude/projects/+~/.claude/history.jsonl; Codex →~/.codex/sessions/; PI → your extension's log dir. Default window: the last 2 weeks.
This choice is what makes the scan reactive or proactive. Nothing else changes.
-
Your steer (optional — ask once, accept "nothing specific") — one input, whose meaning follows the target:
- Scanning a RUN: the symptom you noticed, in your words — what the agent got wrong, what you had to correct, what annoyed you. You were there; don't make the scan re-derive from the artifacts what you can just say. (This is the "you just did X" of the one-sentence outer loop — the tooled version accepts the same X.) Keep it to the observation; working out why it happened is the scan's job, not yours.
- Scanning LOGS: the theme you care about — the kind of work you want to stop doing by hand, a quality bar you keep enforcing, a part of the loop that keeps costing you. Without it the scan just ranks by frequency, which is not the same as ranking by what matters to you.
Either way: you supply the steer, the target supplies the evidence.
-
The agent's own capability docs (optional — normally resolve this yourself) — so the scan knows what your agent can become (its real extension points). Work it out; do not ask first. Identify which agent you are running as and find its own extensibility docs (for Claude Code that is
code.claude.com/docs). Only ask if you genuinely cannot determine it, or if the user wants you pointed somewhere specific. Never assume a fixed set of extension points: read them from whatever docs you actually find.
Steps — keep them literal; this is the fragile part (meta-prompting)
-
Learn your own capabilities. Determine which agent you are running as and read its capability docs (input 3, which you normally resolve yourself). Write a short internal list of this agent's extension points (rules, skill, hook, subagent, MCP/tool, automation/workflow, whatever the docs describe). Use what the docs say — do not assume a fixed set.
-
Read the target — branch on what input 1 was:
- A RUN: read the artifacts in full — they're small, and the detail is the point. If input 2 named a symptom, start there: find it in the artifacts and verify it against what actually happened, rather than re-deriving from scratch what the user already told you. Then reconstruct the rest of the run: what was asked, what the agent did, where it went wrong, where it had to be corrected, what it assumed, what it skipped — the named symptom is the entry point, not a blinder. Read the diff last, as evidence rather than as the subject.
- A WINDOW OF LOGS: pull out what you actually did — recurring commands, repeated multi-step sequences,
repeated instructions/corrections, tools reached for, friction/retries. Aggregate, don't ingest: logs can
be huge — prefer the prompt/command-history file over raw transcripts, and reduce with shell tools
(
jq/grep/sort | uniq -c) so only frequencies and representative samples enter your context, never whole log files.
Either way: if you can't locate or parse the target, ask the user rather than invent.
-
Find what to change — the question differs by target:
- RUN (reactive): for each thing that went wrong or needed correcting, ask **"what in the AI layer