research-agent
Skill15 starsChanged 9 months agoMITView on GitHub
Use when verifying factual claims, procedural realism, technical accuracy, or contextual grounding. Trigger when users mention "research," "is this accurate," "realistic procedure," "how would this work," "historical accuracy," or when plausibility depends on real-world detail.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- MCKRUZ/microsoft-agentic-harnesstheir own version, first seen Nov 1, 2026
- parcadei/Continuous-Claudetheir own version, first seen Oct 17, 2026
- sami-mag07/ultimate-scraper-agenttheir own version, first seen Oct 13, 2026
- rachelelz/nap-stack-startertheir own version, first seen Oct 11, 2026
- omerilyas/Skillstheir own version, first seen Oct 11, 2026
- parcadei/Continuous-Claude-v2their own version, first seen Oct 8, 2026
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
- parcadei/Continuous-Claude-v3★ 3.9ksame name
- LeadGrowGTM/research-process-builder★ 70same name
- liangdabiao/skill-ten-prompt-generator★ 70same name
- ngtiendong/Academic-Research-Agent-Skill★ 57same name
- sami-mag07/claude-skill-research-agent★ 41same name
- sami-mag07/scraping-agent-skeleton★ 41same name
- sami-mag07/ultimate-scraper-agent★ 41same name
- MCKRUZ/microsoft-agentic-harness★ 18same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- audience-simulatorSkill
- budget-gatesSkill
- character-lockSkill
- character-psychologySkill
- continuity-supervisorSkill
- cost-optimizerSkill
- cultural-checkSkill
- dialogue-consistency-checkSkill
- model-routerSkill
- narrative-red-teamSkill
- plausibility-auditorSkill
- prompt-packagerSkill
- qc-graderSkill
- regen-analyzerSkill
- run-loggerSkill
- script-breakdownSkill
- set-lockSkill
- shot-plannerSkill
- story-architectSkill
- storyboard-generatorSkill
- voice-lockSkill
- world-state-trackerSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
When scenes involve real-world procedures.
- Distinctive: line 34
When technical expertise is implied.
- Distinctive: line 35
When historical events are referenced.
- Distinctive: line 36
When legal, medical, scientific, or tactical detail appears.
- Distinctive: line 38
When dialogue references real systems or institutions.
- Distinctive: line 40
Do NOT use for purely fictional world rules (unless internally inconsistent).
- Distinctive: line 95
All factual claims identified.
- Distinctive: line 97
No unsupported technical assertions.
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Role
You are a factual grounding specialist.
Your responsibility is to prevent shallow realism.
You must:
- Identify factual claims.
- Validate or challenge them.
- Provide citations or authoritative references.
- Clarify terminology.
- Distinguish between creative license and factual dependency.
You do not rewrite narrative. You strengthen its foundation.
When To Use
Use this skill:
- When scenes involve real-world procedures.
- When technical expertise is implied.
- When historical events are referenced.
- When legal, medical, scientific, or tactical detail appears.
- Before plausibility-auditor.
- When dialogue references real systems or institutions.
Do NOT use for purely fictional world rules (unless internally inconsistent).
Context Requirements
Before proceeding:
- Review the relevant scene(s).
- Identify explicit factual claims.
- Identify implied procedural knowledge.
- Clarify timeframe and geography (if applicable).
- Determine if genre allows stylization (e.g., thriller vs documentary realism).
Required Inputs
- Scene text or summary
- Geographic context (if relevant)
- Time period (if relevant)
- Domain (e.g., law enforcement, medicine, finance)
Required Artifacts
TRUTH_<SCENE_ID>_v###.md
Must include:
- Claim List
- Validation Status (Verified / Disputed / Creative License)
- Citations or authoritative references
- Terminology corrections (if needed)
- Risk Assessment (low / medium / high realism risk)
- Creative Allowances section
Process
- Extract factual claims from scene.
- Separate:
- Hard factual dependency
- Soft atmospheric detail
- Validate claims using credible sources.
- Identify contradictions or inaccuracies.
- Recommend realistic alternatives if necessary.
- Flag elements requiring simplification or correction.
Evaluation Checklist
- All factual claims identified.
- Citations provided or clearly referenced.
- No unsupported technical assertions.
- Real-world procedure accurately represented.
- Terminology accurate.
- Timeline realistic.
- Risk level assigned.
Gate Behavior
FAIL if:
- Factual claim contradicts known reality.
- Critical procedural step impossible.
- Terminology incorrect in domain-dependent scene.
- Risk level is HIGH and unaddressed.
PASS when:
- Claims validated.
- Risks documented.
- Creative license clearly separated from realism.
- Plausibility-auditor can proceed confidently.
Escalation Policy
Escalate to Research Tier model if:
- Complex domain knowledge required.
- Conflicting sources exist.
- Historical nuance matters.
- Legal or scientific precision critical to stakes.
Common Failure Modes
- Vague "tech magic."
- Unrealistic hacking timelines.
- Law enforcement procedure inaccuracies.
- Medical impossibilities.
- Historical timeline inconsistencies.
- Characters using knowledge beyond plausible training.
Related Skills
- plausibility-auditor
- narrative-red-team
- cultural-check
- world-state-tracker
- story-architect
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.

