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

zynkr-gm

Skill21 starsChanged 49 days agoNo licenceView on GitHub

The GM operating-rhythm skill for a small company run from Google Docs/Sheets. Reads the source-of-record chain in precedence order (strategy alignment section → H2 project tracker (status SOR) → the ops team's weekly log → OKR & KPI tracker → per-function progress sheets), derives per-item state (ends-soon · overdue · undated · propose-done · direction-unlabelled), and produces a fixed-shape WEEKLY GM BRIEF: runway line first, the ≤3 things only the GM can unblock, two clocks, P0/P1 status by LOB, per-owner rollup, KPI off-target + asks, decisions register, deliberately-not-this-week, machine health. Delivers as a Gmail draft (interactive) or an auto-sent email (the Monday cloud routine rendered from this skill). Trigger EAGERLY on "/zynkr-gm", "zynkr-gm week", "GM 週報", "這週重點", "本週 focus", "本月重點", "what should I focus on this week", "as a GM what will I do this week", "week focus", "month focus", "GM brief", "run the GM pass", "哪些 P0 delay 了", "KPI 有沒有 off target", "H2 進度盤點", "幫我盤一下 H2 專案", or any ask for a company-level (not one project's) week/month focus, progress roll-up, or KPI variance. BOUNDARY — do NOT hijack: /project-status-update (one project's weekly status email from its own tracker), /consult-status-report and /consult-governance (consulting portfolio), /admin-governance (file-level Drive↔local index drift), /admin-meeting-prep (per-meeting packets), /skill-finder (which skill for a task), /planning-tracker-sync (the TEAM weekly tracker block, nudges and snapshots — it consumes this skill's derived-state rules, but the founder brief stays here), the rest of the planning suite 0.03-0.10 (a planning CYCLE: pre-work, offsite synthesis, tracker build, OKR reconcile), /curate-livestream-transcripts (it produces the notes this skill only health-checks). This skill reads broadly and writes narrowly: it never edits the tracker, the onboarding master doc, or another owner's doc.

The file

Show its rules and text

We split this skill into the rules it gives an agent

20 rules. About 0 are common, 14 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈14

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    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