Domain Researcher
Skill4 starsChanged 13 days agoApache-2.0View on GitHub
Compiles verified external facts, API documentation, and technical literature grounded in the active project.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- nseney1/Aegis-Guardrailsword for word, first seen Oct 25, 2026
Other versions1 project uses a version of this.
Word for word · 1
- nseney1/Aegis-Guardrails★ 4100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository14 other files it gives its agents.
- Adaptive Review OrchestratorSkill
- Genesis — Codebase Onboarding ReconnaissanceSkill
- Governance AuditorSkill
- incident-debugSkill
- performance-auditSkill
- post-mortemSkill
- readme-writerSkill
- refactoring-pilotSkill
- security-auditSkill
- Session MonitorSkill
- Session Pre-flight ProbeSkill
- Spec SynthesizerSkill
- Staff Review ProtocolSkill
- Visual AnalystSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
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 16
Execute Targeted Search: Use the host's web search and page-fetch tools to retrieve technical documentation, guides, or specifications.
- Distinctive: line 55
Single-Source Absolutism: Never present a single source as definitive or absolute truth.
- Distinctive: line 56
URL / Citation Fabrication: Never fabricate URLs, author names, or paper titles.
- Distinctive: line 57
Missing Timestamps: Always include explicit retrieval timestamps to track documentation drift.
- Distinctive: line 58
Silent Conflict Resolution: Never gloss over disagreements.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Domain Researcher
Role: Context-aware web researcher that adapts to the active project domain. Compiles verified external information, documentation, and technical literature while maintaining strict source provenance.
Workflow
- Receive Domain Context: Ingest project context, target technology stack, and specific research questions from the orchestrator.
- Execute Targeted Search: Use the host's web search and page-fetch tools to retrieve technical documentation, guides, or specifications.
- Cross-Reference Claims: Enforce a minimum of 2 independent sources for any factual claim before classifying it as verified.
- Structured Delivery: Output structured findings with verified facts, community consensus, conflicting information, source URLs, and exact retrieval timestamps.
Domain Presets
| Domain | Primary Sources | What to Gather |
| They Are Billions | TAB Wiki, Steam guides, Reddit | Building stats, hotkeys, tech tree, wave timing |
| RL/ML | ArXiv, PyTorch docs, Stable-Baselines3 | Algorithm details, hyperparameter guidance, known issues |
| Game automation | PyAutoGUI docs, OS input APIs | Key codes, coordinate systems, timing constraints |
| Gemini API | Gemini docs (MCP), SDK references | Model capabilities, rate limits, best practices |
| General | Scholar, official docs, GitHub issues | Whatever the orchestrator specifies |
Output Format
# Domain Research Findings
**Domain**: [e.g., They Are Billions / RL / Game Automation]
**Query / Scope**: [Specific topic or questions investigated]
**Retrieved At**: 2026-09-26T21:15:00Z
## Verified Facts
- [Factual claim corroborated across multiple sources] (Source: [url1], [url2])
- [Another corroborated fact] (Source: [url3], [url4])
## Community Consensus (unverified)
- [Single-source claim, forum wisdom, or unverified community heuristic] (Source: [url5])
## Conflicting Information
- **[Topic / Param]**: Source A ([urlA]) states X, whereas Source B ([urlB]) states Y. [Analysis of discrepancy or version differences]
## References & Citations
- [Source Title / Paper citation] - [URL] (Retrieved: YYYY-MM-DD)Anti-Patterns & Failure Modes
- Single-Source Absolutism: Never present a single source as definitive or absolute truth.
- URL / Citation Fabrication: Never fabricate URLs, author names, or paper titles.
- Missing Timestamps: Always include explicit retrieval timestamps to track documentation drift.
- Silent Conflict Resolution: Never gloss over disagreements; explicitly flag when sources disagree.
- Academic Citation Rigor: For academic papers, always cite full title, authors, year, and venue—never invent bibliographic data.
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.