Skill example

Weekly operating report skill.

A weekly operating report skill turns repeated reporting work into a governed workflow: KPIs, movement, blockers, risks, owner updates, decisions needed, and a consistent leadership narrative.

Company skills / Weekly operating report

The private workflow

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 prompt and logic usually stay with one operator.

Skill contract

Weekly operating report skill
TriggerWeekly leadership meeting, board prep, operating review, functional review, or Monday exec update.
InputsKPIs, pipeline, revenue, usage, support volume, project status, owner updates, risks, decisions, prior report.
ContextOperating cadence, KPI definitions, current company priorities, escalation rules, approved reporting format.
OwnerCOO, business operations lead, or chief of staff.
PermissionsLeadership, operations, finance, RevOps, and relevant functional owners.
OutputExecutive summary, KPI deltas, leading risks, blockers, owner updates, decisions needed, follow-up list.

Review checklist

KPI definitions

Does the skill use the same definitions leadership uses in operating reviews?

Source discipline

Does every claim map back to a dashboard, owner update, ticket queue, or prior report?

Decision clarity

Does the report separate information from decisions leadership needs to make?

Trend memory

Does the skill compare against prior weeks instead of writing a disconnected snapshot?

Example output

Executive summary

Pipeline coverage improved, support backlog rose in enterprise accounts, and onboarding project slipped one week.

Decisions needed

Approve temporary support allocation, decide whether to defer onboarding scope, and confirm sales hiring priority.

Risks

Enterprise ticket queue is becoming a renewal risk. Product dependency could delay onboarding milestone.

Owner follow-up

Support lead owns backlog plan, RevOps owns pipeline source cleanup, PM owns onboarding dependency update.

Monitoring signals

ReuseOperating reports generated from the approved format.
QualityLess rework from leadership and fewer unclear asks.
DriftKPI definitions, priorities, or meeting cadence changed.

Why it matters

Operating reports are high-leverage because they shape leadership attention. A governed skill keeps reporting consistent, source-grounded, and easier to improve as the business changes.

Make operating reporting reusable.

Book a walkthrough and we will identify one reporting workflow that should become a company skill.

Book a walkthrough