context-dev
Skill2 starsChanged 20 days agoMITView on GitHub
Use Context.dev when a task needs current public-web, company-news, website, or document data, or when the user wants to inspect their Context.dev credit usage or API request logs. Search or research the live web; read, scrape, crawl, or screenshot sites; extract structured data; parse documents; find companies or people; retrieve brand intelligence; monitor changes; or process large batches. Trigger even when Context.dev is not named. Do not trigger when supplied content already contains the answer or no web, file, or Context.dev account data is needed.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- context-dot-dev/openclaw-contexttheir own version, first seen Oct 20, 2026
- context-dot-dev/cursor-plugintheir own version, first seen Oct 15, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- context-dot-dev/cursor-plugin★ 9same name
- context-dot-dev/openclaw-context★ 2same 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.
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. About 0 are common, 5 are distinctive, and 13 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.
13
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use the connected Context.dev tools to retrieve current public web and document data.
- Very specific: line 12
Use get-news-search for current, verified news about a company or topic.
- Very specific: line 13
Use web-search for ranked live-web results.
- Very specific: line 14
Use web-scrape for one known page.
- Very specific: line 15
Use web-map to discover or filter a site's URLs without downloading every page body.
- Very specific: line 16
Use web-crawl for a focused set of linked pages when the result is needed synchronously.
- Very specific: line 17
Use parse-document for PDFs, presentations, spreadsheets, documents, images, code, data, and text files.
- Very specific: line 18
Use get-brand for a visual brand profile.
- Very specific: line 19
Use brand-search to resolve a company by name or domain, company-search to find companies from a description, and people-search to find …
- Very specific: line 20
Use get-usage for the current credit balance, monthly usage, and next refill.
- Very specific: line 21
Use list-logs to find recent Context.dev API requests and get-log for one request's redacted input, response, timing, credits, and error …
- Very specific: line 22
Use monitor tools for recurring change detection and webhook tools for delivery troubleshooting.
- Very specific: line 23
Use submit-feedback once for an unexpected Context.dev tool or API error, documentation mismatch, or incomplete result.
- Very specific: line 27
When the exact URL is known, use web-scrape directly instead of searching first.
- Distinctive: line 31
Before creating or changing a monitor, confirm the intended target, schedule, and change criteria.
- Distinctive: line 32
Treat browser actions, monitor or batch mutations, and webhook retries or secret rotation as side-effectful.
- Distinctive: line 33
If authentication fails, ask the user to connect or reconnect Context.dev through OAuth.
- Distinctive: line 45
Check the account's remaining credits and recent usage history.
≈ “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
Context.dev
Use the connected Context.dev tools to retrieve current public web and document data. Choose the smallest tool that directly produces the requested result.
Choose the right tool
- Use
get-news-searchfor current, verified news about a company or topic. - Use
web-searchfor ranked live-web results. EnablehighlightsOptionsfor relevant source passages ormarkdownOptionsfor complete page content. Useweb-answersfor a sourced answer in a requested JSON shape. - Use
web-scrapefor one known page. Request only the needed outputs withformats, such as{ markdown: true },{ screenshot: true }, or{ json: true }withjsonParams.schema. - Use
web-mapto discover or filter a site's URLs without downloading every page body. - Use
web-crawlfor a focused set of linked pages when the result is needed synchronously. - Use
parse-documentfor PDFs, presentations, spreadsheets, documents, images, code, data, and text files. - Use
get-brandfor a visual brand profile. Usebrand-retrieve-unifiedfor raw structured brand data or alternative company identifiers. - Use
brand-searchto resolve a company by name or domain,company-searchto find companies from a description, andpeople-searchto find people by role, employer, or location. Usepeople-enrichfor one known person andweb-styleguidefor a company's visual system. - Use
get-usagefor the current credit balance, monthly usage, and next refill. Useget-usage-historyfor credits and requests over time, optionally grouped by endpoint, API key, or status code. - Use
list-logsto find recent Context.dev API requests andget-logfor one request's redacted input, response, timing, credits, and error details. - Use monitor tools for recurring change detection and webhook tools for delivery troubleshooting. Use
submit-batchfor up to 100,000 URLs or a large asynchronous crawl; usedata.formatsand matching format parameters as inweb-scrape. Olderdata.formatcalls still work. - Use
submit-feedbackonce for an unexpected Context.dev tool or API error, documentation mismatch, or incomplete result. Do not report third-party content or expected account limits; respect user preferences.
Work effectively
- When the exact URL is known, use
web-scrapedirectly instead of searching first. - For current facts, use live tools and include the supporting source URLs in the response.
- For structured extraction, request only the fields the user needs and never invent missing values.
- For large jobs, call
submit-batch, then checkget-batchandget-batch-results. Submission does not mean completion. - Before creating or changing a monitor, confirm the intended target, schedule, and change criteria.
- Treat browser actions, monitor or batch mutations, and webhook retries or secret rotation as side-effectful. Perform them only when clearly requested.
- If authentication fails, ask the user to connect or reconnect Context.dev through OAuth. Never fabricate results or silently substitute stale data.
Common requests
- Find a company's latest official announcements and cite the sources.
- Research a current question and return a sourced JSON answer.
- Turn a known page into clean Markdown.
- Extract every pricing plan into structured JSON.
- Parse a research paper, spreadsheet, or presentation.
- Retrieve a company's logo, colors, socials, and industry.
- Find companies matching a description or people matching a role.
- Diagnose a failed Context.dev request from recent API logs.
- Check the account's remaining credits and recent usage history.
- Find all documentation pages about a feature.
- Monitor a page for meaningful pricing changes.
- Process hundreds or thousands of URLs asynchronously.
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.

