From cklph-eos
Pick and run 5-15 weekly leading metrics that predict outcomes, with a number, target, owner, and weekly trend per row. Use when setting up team metrics, doing a weekly metrics review, or when a number is off two weeks running and needs to become an issue.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cklph-eos:scorecardThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A scorecard is a small set of weekly leading metrics. Each row — **number, target, owner, weekly trend.** Five to fifteen rows. Reviewed in five minutes at the weekly sync.
A scorecard is a small set of weekly leading metrics. Each row — number, target, owner, weekly trend. Five to fifteen rows. Reviewed in five minutes at the weekly sync.
You need lagging metrics for the board. You need leading metrics to actually change anything. The scorecard is leading. If your scorecard is lagging, you're driving by looking in the mirror.
Don't confuse them. A scoreboard with 40 rows is a dashboard, and no one reads it.
One bad week is noise. Two in a row is a pattern. Route it to issues-ids in the same weekly-sync. Don't talk about it during the scorecard block; surface it and move on.
Setting up team metrics. Weekly metrics review. A number is off and needs surfacing. "What should we actually be measuring?"
Pairs with weekly-sync (the 5-minute scorecard block lives there) and issues-ids (where off-target metrics get solved).
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub chykalophia/cklph-marketplace --plugin cklph-eos