Update to Context.dev

SKILL.md line diff

--- before
+++ after
@@ -1,48 +1,45 @@
 ---
 name: context-dev
-description: "Use Context.dev for tasks that need live public-web or document data: web search; scraping known URLs to Markdown, HTML, or images; sitemap discovery and crawling; schema-based extraction; PDF and Office parsing; company logos, colors, socials, and industry; website style guides, fonts, screenshots, monitoring, or large URL batches. Trigger even when Context.dev is not named. Do not trigger for questions answerable from supplied text, private account data, or tasks that need no web or file retrieval."
+description: 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 API request logs. Search or research the live web; read, scrape, crawl, or screenshot sites; extract structured data; parse documents; retrieve brand or people 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.
 ---
 
 # Context.dev
 
-Use the connected Context.dev tools to retrieve current public web and file data. Prefer the smallest tool that directly produces the requested result.
+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 `web-search` when the user needs current information and does not provide the exact source URL.
-- Use `web-scrape-markdown` to read, summarize, or analyze one known URL.
-- Use `web-scrape-html` only when raw DOM structure, attributes, scripts, or markup are required.
-- Use `web-scrape-images` to discover image assets and `web-screenshot` for a rendered page image.
-- Use `web-scrape-sitemap` to discover or search a site's URLs without fetching every page body.
-- Use `web-crawl` for a focused set of linked pages when results are needed synchronously.
-- Use `web-extract` when the user wants structured fields such as products, pricing, jobs, locations, or company facts.
+- Use `get-news-search` for current, verified news about one company.
+- Use `web-search` for ranked live-web results. Enable `highlightsOptions` for relevant source passages or `markdownOptions` for complete page content. Use `web-answers` for a sourced answer in a requested JSON shape.
+- Use `web-scrape` for one known page. Request only the needed outputs with `formats`, such as `{ markdown: true }`, `{ screenshot: true }`, or `{ json: true }` with `jsonParams.schema`.
+- Use `web-map` to discover or filter a site's URLs without downloading every page body.
+- Use `web-crawl` for a focused set of linked pages when the result is needed synchronously.
 - Use `parse-document` for PDFs, presentations, spreadsheets, documents, images, code, data, and text files.
-- Use `get-brand` for a visual brand profile from a domain. Use `brand-retrieve-unified` for raw structured brand data or lookups by name, email, ticker, ISIN, transaction descriptor, or direct URL.
-- Use `web-styleguide` and `web-fonts` to inspect a site's visual system and typography.
-- Use `web-naics` or `web-sic` for industry classification.
-- Use the monitor tools for recurring change detection. Use the batch tools for large asynchronous jobs or many URLs.
+- Use `get-brand` for a visual brand profile. Use `brand-retrieve-unified` for raw structured brand data or alternative company identifiers.
+- Use `brand-search` to find a company, `web-styleguide` for its visual system and typography, and `people-enrich` for a person profile.
+- Use `list-logs` to find recent Context.dev API requests and `get-log` for one request's redacted input, response, timing, credits, and error details.
+- Use monitor tools for recurring change detection, webhook tools for delivery troubleshooting, and batch tools for large asynchronous jobs.
+- Use `submit-feedback` to report a Context.dev bug, documentation mismatch, or agent friction when requested.
 
 ## Work effectively
 
-1. When the exact URL is known, use the corresponding scrape or extract tool instead of searching first.
-2. For current facts, use live web tools and retain the source URLs in the answer.
-3. For structured extraction, define the narrowest schema that matches the user's requested fields. Do not invent missing values.
-4. For large jobs, call `submit-batch`, then use `get-batch` and `get-batch-results`. A successful submission is not a completed job.
-5. For monitor requests, inspect existing monitors when useful and confirm the intended target, schedule, and change criteria before creating or changing one.
-6. Treat browser actions, monitor mutations, and batch mutations as side-effectful. Only perform them when the user has clearly requested that action.
-7. If authentication fails, tell the user to connect or reconnect Context.dev through OAuth. Do not fabricate results or silently substitute stale data.
-
-## Match common requests
-
-Invoke Context.dev for requests such as:
-
-- "find the latest official announcements about this company"
-- "summarize this page" or "turn this URL into Markdown"
-- "extract every pricing plan as JSON"
-- "parse this research paper or presentation"
-- "get this company's logo, colors, socials, and industry"
-- "find all documentation pages about authentication"
-- "watch this page for meaningful pricing changes"
-- "scrape these hundreds of URLs and give me the results"
-
-Do not invoke Context.dev when the answer is already present in user-provided content, the task concerns private workspace data from another connected service, or no public web or file retrieval is required.
+1. When the exact URL is known, use `web-scrape` directly instead of searching first.
+2. For current facts, use live tools and include the supporting source URLs in the response.
+3. For structured extraction, request only the fields the user needs and never invent missing values.
+4. For large jobs, call `submit-batch`, then check `get-batch` and `get-batch-results`. Submission does not mean completion.
+5. Before creating or changing a monitor, confirm the intended target, schedule, and change criteria.
+6. Treat browser actions, monitor or batch mutations, webhook retries or secret rotation, and feedback submission as side-effectful. Perform them only when clearly requested.
+7. 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.
+- Diagnose a failed Context.dev request from recent API logs.
+- Find all documentation pages about a feature.
+- Monitor a page for meaningful pricing changes.
+- Process hundreds or thousands of URLs asynchronously.