consult-bug-ticket SKILL.md skillA
consult-bug-ticket 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/consult-bug-ticket@git:20260927.31de767Pins git:20260927.31de767 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/2-sales-consultant/consult-bug-ticket/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260927.31de767, committed Sep 27, 2026
- First version recorded
- Aug 2, 2026
- Size
- 13,785 bytes
- Repository stars
- 22
- License
- none declared
Turn a client bug report — a Gmail thread, a forwarded mail, or pasted text — into tracked work in one pass: a well-formed GitHub issue in the right repo (routed via a local bug-routing-config.md), a CRM follow-up task on the client's deal, and a threaded acknowledgment reply left as a Gmail DRAFT (never sent). Trigger on /consult-bug-ticket or when Peter says "開 bug 單", "把這封信開成 issue", "回報這個 bug", "客戶回報問題", "file this bug", "turn this bug mail into a ticket", "log this defect and reply", 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
# Consult Bug Ticket ```bash npx skills add https://github.com/peter-tu-zynkr/zynkr-skill-builder --skill consult-bug-ticket ``` When a client reports a defect — in a delivered assistant, in the platform, on the website — the report tends to die in the inbox. This skill turns one bug report into three artifacts in a single pass: a **well-formed GitHub issue** in the right repo, a **CRM follow-up task** on the client's deal so the sales side sees the open loop, and a **threaded acknowledgment reply** waiting as a Gmail draft so the client knows they were heard. It is deliberately gated: nothing external is written until Peter approves the target repo, issue title, complete body, and severity at one hard gate. The public issue and the private CRM record carry *different* halves of the story — company + defect in the issue, person + thread in the CRM task — by design. ## How this differs from its neighbours - **zynkr-support** — drafts KB-based ANSWERS to product questions (the READ side of the support loop). When a support mail turns out to be a DEFECT in a delivered assistant or product, THIS skill is the write-side that takes over: …
Read the whole file at its exact version.
How to install
mdr add peter-tu-zynkr/zynkr-skill-builder/consult-bug-ticket@sha256:c307e3a0e378857cThe line at the top of this page pins the label git:20260927.31de767, 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_rt76gkivv5sivrvb)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 2, 2026 and Sep 27, 2026, about one every 14 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260927.31de767 latest | 2026-09-27 | 31de767 | 13,785 B | A | view · diff |
| git:20260918.2429d96 | 2026-09-18 | 2429d96 | 13,757 B | A | view · diff |
| git:20260907.364596e | 2026-09-07 | 364596e | 13,669 B | A | view · diff |
| git:20260816.5c37a02 | 2026-08-16 | 5c37a02 | 13,766 B | A | view · diff |
| git:20260802.b6bfb04 | 2026-08-02 | b6bfb04 | 13,756 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 (13785 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_rt76gkivv5sivrvb GET https://markdownregistry.com/api/v1/resolve?ref=peter-tu-zynkr/zynkr-skill-builder/consult-bug-ticket GET https://markdownregistry.com/api/v1/blob/c307e3a0e378857ccf50fd4dcac1a9365835b22e2d40ba89d61c5d1ce5376c9b
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.