zynkr-kms SKILL.md skillA
zynkr-kms 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/zynkr-kms@git:20260928.d21fb8dPins git:20260928.d21fb8d 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/3-operations/zynkr-kms/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260928.d21fb8d, committed Sep 28, 2026
- First version recorded
- Aug 26, 2026
- Size
- 24,423 bytes
- Repository stars
- 22
- License
- none declared
The knowledge-curator (WRITE) half of Peter's support loop: it turns resolved support threads into KB cards in the Zynkr platform 知識庫 (the source of truth), then mirrors every change to a Google Drive backup. After a support / inbound-sales ticket is resolved, zynkr-kms reads the thread, learns Peter's actual answer, and writes it as a clean, LLM-friendly card into the **Zynkr platform 知識庫** (platform.zynkr.ai/kb, via the `zynkr` MCP server) — the single source of truth since the 2026-07-15…
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
# Zynkr KMS — Support Knowledge Curator (platform KB + Drive mirror) ```bash npx skills add https://github.com/peter-tu-zynkr/zynkr-skill-builder --skill zynkr-kms ``` `/zynkr-support` *reads* the platform 知識庫 to draft replies. This skill is the other half of the loop: it **learns from resolved tickets and writes the answers back** so the KB heals and the drafter stops falling back to `[[NEEDS PETER]]` holding replies. You think like a **KMS specialist**, not a transcriber. For every resolved thread you reason through three lenses before anything is written: 1. **Intent taxonomy** — what *kind* of question is this? 2. **Where to write** — which **KB section** does it belong in, and is it a new card or an update? 3. **Structure for the LLM** — a canonical `fact` card, or a `qa` card that cites facts? The golden rule: **extract, never invent.** KB facts come only from what Peter actually wrote. A bad KB card silently poisons every future auto-reply, so the bar is high and **nothing enters the KB without Peter's approval.** > **This skill governs TWO stores, and the arrow between them only points one way.** > > ``` > Zynkr platform KB ──(mirror)──▶ Google Drive Docs …
Read the whole file at its exact version.
How to install
mdr add peter-tu-zynkr/zynkr-skill-builder/zynkr-kms@sha256:7a7bfeefa877b03aThe line at the top of this page pins the label git:20260928.d21fb8d, 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_zslei2avfkm4mnqe)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 26, 2026 and Sep 28, 2026, about one every 8 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260928.d21fb8d latest | 2026-09-28 | d21fb8d | 24,423 B | A | view · diff |
| git:20260927.31de767 | 2026-09-27 | 31de767 | 23,685 B | A | view · diff |
| git:20260918.2429d96 | 2026-09-18 | 2429d96 | 23,640 B | A | view · diff |
| git:20260826.b6cc57d | 2026-08-26 | b6cc57d | 22,932 B | A | view · diff |
| git:20260826.57828db | 2026-08-26 | 57828db | 23,198 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 (24423 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_zslei2avfkm4mnqe GET https://markdownregistry.com/api/v1/resolve?ref=peter-tu-zynkr/zynkr-skill-builder/zynkr-kms GET https://markdownregistry.com/api/v1/blob/7a7bfeefa877b03a4d6f398c6754a4f5e4c96864b00cbf0b7134af3c9a9b3027
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.