본문으로 건너뛰기
cccskills
무료GitHub에 공개

ops-run-the-operating-rhythm

Use when the user wants a weekly, monthly, or quarterly business review set up, asks how the business is doing this period, or hands over numbers for a review pack.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

실행 점수 미검증

설치 방법 보기

포함된 파일(1)

  • SKILL.md3.0 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Run the operating rhythm

Use this when the user wants a weekly business review (WBR), monthly business review (MBR), or quarterly business review (QBR) set up, asks how the business is doing this period, or hands over numbers for a review.

What you need first

The cadence (weekly, monthly, quarterly), the KPI set with targets, the numbers from connected sources or pasted exports, and the open actions from the last review.

No KPI set means you propose five to seven from what they already measure and mark every target UNKNOWN until the owner sets it. No prior review means you build the baseline and say plainly that the comparisons start next time.

Read what exists before you build anything

Say back what you found: the last review date, actions open and overdue, and which KPIs have targets and which do not. Never rebuild a rhythm they already run.

Fix the period and say it out loud

Name the days this review covers and the days it compares against. Never compare a partial period to a full one.

Build the pack

  • KPIs against target, with red/yellow/green (R/Y/G) on each, tagged INPUT (controllable, leading) or OUTPUT (lagging result). Every review carries at least two to three input metrics.
  • The top three movers, each with a one-line cause.
  • What shipped against the plan.
  • What is stuck, and who owns it.
  • The decisions needed, with options and a recommendation on each.

Every line carries FACT, INFERENCE, or UNKNOWN. Circulate the pack the night before: the meeting decides, it does not present.

Run the agenda in this order

Numbers (ten minutes), stuck items (ten minutes), decisions (fifteen minutes), actions (five minutes).

The review is exception-based. Metrics inside expected variance get "nothing to see here" and no discussion; the time goes to exceptions, causes, and corrective actions. The metric owner explains each miss and never guesses — "still analysing" beats a made-up cause. A decision without an owner and a date is not a decision.

Close the loop

Write the decision log. Carry open actions forward with new dates. Name the one thing that matters most before the next review. Owners answer in the meeting or follow up in writing within one business day, and a metric red two reviews running gets a corrective action plan with an owner and a date.

Rules

Never invent a metric, a target, or a decision. Never email or post the pack anywhere without the owner's yes.

Save dated under reviews, one folder per cadence. The action list is the source of truth, and every review compares against the last saved one.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Write ad variants that each test one idea, within platform limits and supported claims.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Significant-Gravitas의 스킬 모두 보기

이 스킬의 문제 신고