agentleFS
Sign inStart free
peter-tu-zynkrpeter-tu-zynkr/zynkr-skill-builder/skills/0-strategy/planning-evidence-pack/SKILL.md

planning-evidence-pack

Skill21 starsChanged 48 days agoNo licenceView on GitHub

The "looking back in numbers" scoreboard for a Zynkr planning cycle (H1 / H2 / YE). Seeds KPIs from the session workbook's Pre-work by LOB tab + the OKR tracker's KRs, routes each to ONE readable source (Main Tracker 完成 counts · planning-tracker-sync's `tracker-snapshots` tab · OKR status · Calendar event counts by title pattern · Gmail Fireflies recap counts · numbers the user pastes; zynkr-gm's kpi-map.md when installed), writes a `Scoreboard` tab (KPI · source · <cycle>-start · <cycle>-end · Δ · note) into the cycle workbook or a new hub Sheet, plus the five-tile numbers-slide text. Unreadable → 「（待補）」+ the source needed; never estimates; read-only against every source. Trigger on /planning-evidence-pack or "數字回顧", "把這個週期的數字拉出來", "做 scoreboard", "KPI 計分板", "上半年／全年數字", "evidence pack", "looking back in numbers", "pull the numbers for the offsite". Distinct from planning-prework-pack (consumes the scoreboard), planning-tracker-sync (weekly agenda + snapshots — a source here), zynkr-gm (founder's weekly GM brief + KPI-variance asks; owns 「GM 週報 / 這週重點 / H2 進度盤點 / KPI 有沒有 off target」), planning-1on1-annual-digest (one person's year), and project-status-update (owns bare 「週報」).

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 3 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free