planning-session-synth SKILL.md skillA
planning-session-synth from peter-tu-zynkr/zynkr-skill-builder is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add peter-tu-zynkr/zynkr-skill-builder/planning-session-synth@git:20260918.2429d96Pins git:20260918.2429d96 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- peter-tu-zynkr/zynkr-skill-builder
- Path
skills/0-strategy/planning-session-synth/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260918.2429d96, committed Sep 18, 2026
- First version recorded
- Aug 17, 2026
- Size
- 27,032 bytes
- Repository stars
- 22
- License
- none declared
Same-day digestion of a Zynkr planning offsite (H1 / H2 / year-end): turn the session transcript + whiteboard photos into the Main Tracker's working tabs — verbatim 「② 白板原文」 (pen colour + 判讀信心 高/中/低), the MECE re-cut 「③ 去重與歸類決策」 + 「④ MECE 檢查」 with every merge/split/move ruling written down, the 「<cycle> 回顧總結」 retro table with 5 重點結論, the README tab, a normalized item list handed to planning-tracker-builder, and the recap mail as a Gmail DRAFT (never sent). Trigger on /planning-session-synth or…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Planning Session Synth ```bash npx skills add https://github.com/peter-tu-zynkr/zynkr-skill-builder --skill planning-session-synth ``` The offsite ends with a whiteboard nobody can search and a transcript nobody will re-read; this skill turns both into the Main Tracker the same evening — verbatim board rows first, then a MECE re-cut whose every merge/split/move is a written, disputable ruling, then the retro table and the recap mail. It is for the founder (or whoever facilitated) on the day of an H1 / H2 / year-end planning session, before the memory of what a scrawl meant has faded. Unlike "summarise this meeting", it transcribes before normalising, marks every uncertain reading, applies last cycle's rulings as precedent, and flags the LOBs the room forgot instead of inventing items for them. --- ## How this differs from its neighbours - **planning-tracker-builder** — downstream: takes this skill's normalized item list, adds the room's owner / 重要×緊急 decisions, builds the SOR tab (`<cycle> 專案項目`) with lint. This skill stops at the item list unless told to write the SOR tab; when this run created the cycle's tracker, the builder fills its empty SOR tab in place …
Read the whole file at its exact version.
How to install
mdr add peter-tu-zynkr/zynkr-skill-builder/planning-session-synth@sha256:67f5e65e8a891119The line at the top of this page pins the label git:20260918.2429d96, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_polv4bxwkce426do)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Aug 17, 2026 and Sep 18, 2026, about one every 16 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260918.2429d96 latest | 2026-09-18 | 2429d96 | 27,032 B | A | view · diff |
| git:20260817.b18664b | 2026-08-17 | b18664b | 26,324 B | A | view · diff |
| git:20260817.1bd05ad | 2026-08-17 | 1bd05ad | 21,944 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (27032 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
peter-tu-zynkr/zynkr-skill-builder · 22 stars · license none declared · pushed 2026-10-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_polv4bxwkce426do GET https://markdownregistry.com/api/v1/resolve?ref=peter-tu-zynkr/zynkr-skill-builder/planning-session-synth GET https://markdownregistry.com/api/v1/blob/67f5e65e8a8911198aa986f652f2527fdc76f0381b4951af7c22dd5373e9d377
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.