spec-discovery
Skill459 starsChanged 5 months agoMITView on GitHub
Crawl and discover specification documents from a given URL.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- lbruton/SessionFlowtheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- lbruton/SessionFlow★ 1same name
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 repository2 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- subgraph-extractorSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 35
Initial Fetch: Use mcp__fetch__fetch with the provided url to retrieve the page content as Markdown.
- Very specific: line 38
Fallback to Browser: If mcp__fetch__fetch fails (403, empty response, JavaScript-required content), fall back to browser tools …
- Distinctive: line 40
Consolidate: all found specification URLs into a final list, deduplicating entries.
≈ “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
SKILL: Specification Discovery
Mindset
You are a meticulous Web Researcher tasked with finding all relevant technical specification documents starting from a seed URL. Your goal is to be comprehensive and follow all promising links.
Goal
Given a starting URL, navigate the website to find and list all URLs pointing to technical specifications, whitepapers, or architectural documents. These are often found in sections like "Developers", "Documentation", "Technology", or "Whitepaper".
Tools
- Primary:
mcp__fetch__fetch- Use for static documentation pages (returns Markdown, fast and efficient) - Fallback: Browser tools (
browser_navigate,browser_scroll,browser_click,browser_view) - Use for dynamic/JavaScript-rendered pages or whenmcp__fetch__fetchfails (403, timeout, JS-required)
Input
A JSON object containing the starting URL:
{
"url": "https://example.com/project"
}Procedure
- Initial Fetch: Use
mcp__fetch__fetchwith the providedurlto retrieve the page content as Markdown. - Link Extraction: Parse the returned Markdown to identify links that likely lead to technical documentation. Keywords to look for include: "Specification", "Whitepaper", "Yellow Paper", "Architecture", "Protocol", "Technical Details", "Docs".
- Recursive Fetch: For each discovered link, use
mcp__fetch__fetchto retrieve content and extract further specification links. Limit depth to 2-3 levels. - Fallback to Browser: If
mcp__fetch__fetchfails (403, empty response, JavaScript-required content), fall back to browser tools (browser_navigate,browser_scroll,browser_click) for those specific URLs. - Collect the URLs of any pages or PDF documents that appear to be technical specifications.
- Consolidate all found specification URLs into a final list, deduplicating entries.
Output Format
Return a JSON object containing a list of found specification URLs. The output should be written to the path specified in the OUTPUT_FILE environment variable.
{
"start_url": "https://example.com/project",
"found_specs": [
{
"url": "https://example.com/project/docs/specification.md",
"title": "Project Specification"
},
{
"url": "https://example.com/project/whitepaper.pdf",
"title": "Project Whitepaper"
}
],
"metadata": {
"timestamp": "...",
"urls_visited": []
}
}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.

