Skip to content
cccskills
FreePublished on GitHub

report-spec

Turn a request for a report or a dashboard widget into something buildable: the question it answers, the metric and its definition, where the data comes from, the query shape, and what it will not answer. Use when a new report or dashboard is requested, when an existing one needs a metric added or changed, when a widget is asked for in a sentence and needs pinning down, or when two reports disagree about the same number.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Report spec

Goal

A spec somebody can build against without a follow up conversation, and a number that means the same thing next quarter as it does today.

Procedure

  1. Get the question behind the request. A request for a chart of complaints per site is really a question about which sites need attention, and the answer might not be that chart.
  2. Define the metric precisely: the numerator, the denominator, the window, the grain and the filters. Check memory/conventions/metrics.md first, since the same word usually already means something here.
  3. Say where each field comes from, which table or endpoint, at what grain, refreshed how often. A metric assembled from two sources with different refresh cadences will disagree with itself.
  4. Check the grain before designing the query. If the join can produce more rows than entities, every total downstream is inflated, and this is the defect that survives review because the numbers look plausible.
  5. Decide where it is computed. In the pipeline, in the query, or in the reporting layer. Computing the same metric in two places is how two reports end up disagreeing.
  6. Say what it will not answer, so nobody reads a cause into a count.
  7. Note the cost: how heavy the query is, how often it runs, and whether it needs its own pipeline step rather than running live.

Boundaries

  • Never ship a metric whose definition has not been agreed and written down.
  • Never compute a metric in a second place because it is easier than reusing the first.
  • Never build an audience-facing report on a source you have not checked the refresh cadence of.
  • Never include another audience's data in a scoped report, in any aggregate.
  • Do not build it as part of specifying it. The spec is the deliverable here.

What to record

Write every agreed definition into memory/conventions/metrics.md with its numerator, denominator, window, source and the date it was agreed, and note where it is computed. When two reports are found disagreeing, record the cause there too, because the same pair will disagree again after the next change.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Plan or review software architecture through a small expert panel. Use when the user explicitly asks for architecture planning, system design, technical strategy, an architecture assessment, a design review, or a system health review. Do not use for ordinary PR review, debugging, or implementation.

The English summary is being prepared. Showing the original description.

nanocoai/nanoclaw-templates20Updated Sep 16, 2026

Thorough, consistently formatted competitor and product research. Produces a structured "About" doc, a "Recent News" log, and a row in a tracking spreadsheet. Use whenever the user researches a company or competitor, builds or updates a competitor doc, compares products, or logs a competitor to the tracker.

The English summary is being prepared. Showing the original description.

nanocoai/nanoclaw-templates20Updated Sep 16, 2026

Household assistant for a whole family. Runs a morning brief, plans meals and builds grocery lists (hunting the best prices), looks ahead at the week's logistics, stays on top of the kids' school, watches prices on things the family wants, and helps book appointments and reservations. Use it for anything that keeps the family's day or week running. Trigger even on implicit asks - "what's on today", "what do the kids have this week", "what should we make for dinner", "add milk to the list", "when's the dentist", "did anything come from school", "remind me about the permission slip", "watch this jacket and tell me if it drops", "book us a table Friday".

The English summary is being prepared. Showing the original description.

nanocoai/nanoclaw-templates20Updated Sep 16, 2026

Reporting workflow for a working journalist, using web research and Apify's X scraper (social signals). Onboards the journalist, monitors their beat and builds digests, evaluates story pitches, finds and vets sources, and prepares interviews. Use for any newsroom task, such as "what's new on my beat", "is this pitch any good", "who should I talk to about X", "prep me for this interview", or "turn these notes into a draft".

The English summary is being prepared. Showing the original description.

nanocoai/nanoclaw-templates20Updated Sep 16, 2026

Check that the scheduled data work behind the reports actually ran and produced something sensible: the daily reshaping scripts, the API pulls, the tables the reports read from. Use each morning before anyone opens a report, when a report looks wrong and nobody knows whether it is the data or the query, after a schema or API change, when a new audience or source is added to the pipeline, or when a scheduled job failed or finished suspiciously fast.

The English summary is being prepared. Showing the original description.

nanocoai/nanoclaw-templates20Updated Sep 16, 2026

Write the SQL or MongoDB query that answers a question and keeps answering it: the right grain, no fan out, parameterised window, checked against something known. Use when a number is needed that no report carries, when an existing query returns something that looks wrong, when a query is slow or expensive, or when somebody asks for a one off pull.

The English summary is being prepared. Showing the original description.

nanocoai/nanoclaw-templates20Updated Sep 16, 2026

See all skills by nanocoai

Report a problem with this skill