autonomous-investigation — Claude Code skill: a protocol
Sets the rules for research skills that run while you are away: question budget, a search plan, and Fact/Inference/Assumption labels on every claim.
npx skills add deanpeters/Product-Manager-Skills --skill autonomous-investigation -a claude-codeWhat autonomous-investigation does
This is a contract, not a report generator. The skill spells out how investigation skills should behave: the agent may ask at most a few clarifying questions, and once that budget runs out or nobody replies, it carries on and flags its guesses. An unattended run therefore slows down rather than stalling.
Work starts with a three-point plan: what gets searched, which kinds of sources, how facts will be told apart from interpretation. Then each key claim gets one label. Fact means a checkable URL is attached. Inference means the evidence is cited and you judge the jump. Assumption means a working guess kept for later validation. A separate gaps list holds whatever could not be found, and every domain names its own forbidden fabrications.
Section order stays fixed from run to run, so output N and output N+1 diff cleanly. Signal strength is graded by how many independent channels agree: one is a watch item, two make a working hypothesis, three or more justify briefing leadership. Collection stays within public sources, and the skill rules out pretexting or breaking terms you accepted.
What it helps with
- set up a competitive scan you can re-run quarterly without babysitting
- tell sourced facts apart from the model's guesses
- diff two runs and see what actually moved
- give several research skills the same behaviour
- cut a report down to the bullets a decision needs
Example prompts for the agent
- Run an autonomous investigation on the competitor's push into workflow automation, backing our Q3 roadmap bet.
- Show me your three-bullet search plan before you start collecting.
- What changed since last quarter? Diff this run against the previous one.
How to install autonomous-investigation
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill autonomous-investigation -a claude-code2Manually: put the files in place
~/.claude/skills/autonomous-investigation/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/autonomous-investigation/
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill autonomous-investigation -a codex2Manually: put the files in place
.agents/skills/autonomous-investigation/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill autonomous-investigation -a cursor2Manually: put the files in place
.cursor/skills/autonomous-investigation/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install deanpeters/Product-Manager-Skills autonomous-investigation2Manually: put the files in place
.github/skills/autonomous-investigation/SKILL.md1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill autonomous-investigation -a gemini-cli2Platform CLI
gemini skills install https://github.com/deanpeters/Product-Manager-Skills --path skills/autonomous-investigationManually: put the files in place
.devin/skills/autonomous-investigation/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill autonomous-investigation -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about autonomous-investigation
How do I install autonomous-investigation in Claude Code?
Run npx skills add deanpeters/Product-Manager-Skills --skill autonomous-investigation -a claude-code. The skill file lands at ~/.claude/skills/autonomous-investigation/SKILL.md.
What does autonomous-investigation do?
It defines the contract research skills follow: a capped question budget, a search-plan gate, Fact/Inference/Assumption labels, a stable output schema, and confidence stacking across independent channels.
How is it different from workshop-facilitation?
workshop-facilitation asks the user one question per turn and waits for an answer. Here the context comes from public sources, so a run can be scheduled: with no replies it continues on labelled assumptions.