Two skills, one dataset, different jobs
The skills page should make it obvious that one skill maintains the monthly pipeline while the other helps agents inspect and analyze the live dataset.
How developers actually use it
exploding-insights-sse
Use this skill when the goal is to refresh the source data, normalize the month, import D1, and redeploy the Worker.
exploding-insights-query
Use this skill when the goal is to query, compare, and analyze the live dataset that is already in D1.
exploding-insights-sse
Use this skill when the goal is to refresh the source data, normalize the month, import D1, and redeploy the Worker.
exploding-insights-query
Use this skill when the goal is to query, compare, and analyze the live dataset that is already in D1.
Open the repo where AGENTS.md is present
The repository already exposes the skills through AGENTS.md, so agent-compatible tools can discover them in the project context.
Call the skill by name or natural language
Users can mention the skill explicitly or ask for the outcome they want, and the agent can route to the correct skill.
Use the protected agent API on top of the live D1 dataset
Both skills ultimately rely on the same monthly dataset, but external agent traffic should come through the authenticated /api/agent/query and /api/agent/sse routes.
Example prompts
These prompts are good enough to show on the page because they make the job of each skill concrete.
What this page should clarify
Without this page, people understand the data exists but not how they should use it.
The sync skill is for maintaining the pipeline.
The query skill is for using the dataset after it is already live.
The API page and skills page should link to each other because technical users often need both.
Open the API page