The one operator whose weekly report everyone actually reads.
An approved reporting skill: same structure, same rigor, every week, straight from Claude.
The method one person already has
Operators often build the same weekly report from dashboards, project updates, pipeline notes, product status, support queues, hiring plans, and leadership asks. AI helps, but the method and the logic usually stay with one operator.
With knacks, that operator publishes the reporting method, the COO approves it, it ships to every functional lead's Claude with nothing to install, and the skill library is its home. Afterward, the owner keeps it current. That is the knacks loop: Publish, Approve, Ship, Use, Improve.
Anatomy of the skill
| Method | Gather KPIs, pipeline, revenue, usage, support volume, project status, owner updates, risks, and the prior report, then write the operating narrative: executive summary, KPI deltas, leading risks, blockers, decisions needed, follow-up list. Run it before the weekly leadership meeting, board prep, or an operating review. |
|---|---|
| Reference files | Operating cadence, KPI definitions, current company priorities, escalation rules, approved reporting format. |
| Examples | Two past reports leadership rated as clear, alongside the raw inputs they were built from. |
| Tests | Every claim maps to a dashboard, owner update, ticket queue, or prior report; KPI definitions match the operating review; decisions are separated from information; trends compare against prior weeks. |
| Owner | COO, business operations lead, or chief of staff. |
| Version | Version history with a one line changelog, so everyone sees when KPI definitions or priorities last changed. |
What the team lead reviews
Does the skill use the same definitions leadership uses in operating reviews?
Does every claim map back to a dashboard, owner update, ticket queue, or prior report?
Does the report separate information from decisions leadership needs to make?
Does the skill compare against prior weeks instead of writing a disconnected snapshot?
Example output
Pipeline coverage improved, support backlog rose in enterprise accounts, and onboarding project slipped one week.
Approve temporary support allocation, decide whether to defer onboarding scope, and confirm sales hiring priority.
Enterprise ticket queue is becoming a renewal risk. Product dependency could delay onboarding milestone.
Support lead owns backlog plan, RevOps owns pipeline source cleanup, PM owns onboarding dependency update.
Kept current
When the operating cadence changes, the owner updates the skill once and every functional lead reports the new way the same day. Example: leadership adds a KPI.
No capture and no usage tracking, ever. knacks never sees chats, screens, or who runs what.
Why it matters
Operating reports are high-leverage because they shape leadership attention. An approved skill keeps reporting consistent, source-grounded, and easier to improve as the business changes, because there is one version with one owner instead of ten private variants.
Make operating reporting reusable.
Book a walkthrough and we will identify one reporting method that should become a company skill.
Book a walkthrough