context-extract
Skill9 starsChanged 3 months agoMITView on GitHub
Extract schema-shaped JSON from websites with Context.dev. Use when the user wants structured records such as products, pricing plans, rankings, jobs, events, tables, listings, or explicitly requests JSON that follows a schema.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- xfstudio/skillstheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- xfstudio/skills★ 9same 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 repository10 other files it gives its agents.
- connect-context-devSkill
- context-batchesSkill
- context-brandSkill
- context-crawlSkill
- context-devSkill
- context-monitorSkill
- context-parseSkill
- context-scrapeSkill
- context-searchSkill
- logolinkSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use the Context.dev web-scrape MCP tool with formats: { json: true } and jsonParams.schema when a known webpage must return a predictable …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Extract structured web data
Use the Context.dev web-scrape MCP tool with formats: { json: true } and jsonParams.schema when a known webpage must return a predictable JSON shape rather than free-form text.
Workflow
- Define the smallest JSON Schema that contains only the fields the user needs.
- Give every field a clear description that distinguishes similar values.
- Make fields optional or nullable when the source may omit them.
- Pass the relevant URL and request only the JSON format.
- Validate that the response follows the requested schema before presenting it.
Preserve source semantics. Tied ranks such as =19, ranges such as 101-150, and unavailable scores are legitimate source values; do not silently convert or invent them.
Extraction does not remove site pagination. Discover additional pages with web-map, then use a batch when many page URLs must be processed. Use web-scrape with formats: { markdown: true } when the user only needs readable text.
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.

