consult-project-specialist SKILL.md skillA
consult-project-specialist 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-project-specialist@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-project-specialist/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260927.31de767, committed Sep 27, 2026
- First version recorded
- Aug 16, 2026
- Size
- 13,757 bytes
- Repository stars
- 22
- License
- none declared
Turn a single sales / consulting meeting into tracked work. Give it a meeting transcript or notes — pasted text, a Google Doc, or a Gemini Notes link — and it produces a structured Weekly Project Update, then lays down the three things the engagement needs: a numbered Google Drive project folder, a kickoff/context Doc inside it, and a CRM deal in Supabase with a meeting + links-note + one task per "What's Next" item. Trigger on /consult-project-specialist or when Peter says…
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
# Sales Project Specialist ```bash npx skills add https://github.com/peter-tu-zynkr/zynkr-skill-builder --skill consult-project-specialist ``` Peter has a sales or consulting meeting, comes away with a transcript or a pile of notes, and wants it to *become a tracked project* — not just a tidy summary. This skill does that in one shot: it reads the meeting, writes a **Weekly Project Update**, and then lays down the three things the engagement needs to live in the system — a **Drive project folder**, a **kickoff/context Doc** so whoever picks it up starts with context, and a **CRM deal** with a real activity timeline (the meeting itself, a note carrying the workspace links, and a task for each "What's Next" item). It runs **autonomously**: read → summarise → create → report. No mid-run confirmation. Each run is a fresh debrief, so it **always creates a new deal and a new folder** — there is no dedupe and no "append to the existing deal". If Peter runs it twice on the same meeting he gets two deals; that's intended (re-running is how you redo a botched capture). Override any inferred field by just telling it. ## How this differs from its neighbours …
Read the whole file at its exact version.
How to install
mdr add peter-tu-zynkr/zynkr-skill-builder/consult-project-specialist@sha256:ecb823bfe4278992The 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_qoq7zw5bec5dnfsm)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 16, 2026 and Sep 27, 2026, about one every 10 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260927.31de767 latest | 2026-09-27 | 31de767 | 13,757 B | A | view · diff |
| git:20260918.2429d96 | 2026-09-18 | 2429d96 | 13,651 B | A | view · diff |
| git:20260915.9dbdaae | 2026-09-15 | 9dbdaae | 12,943 B | A | view · diff |
| git:20260907.364596e | 2026-09-07 | 364596e | 11,899 B | A | view · diff |
| git:20260816.5c37a02 | 2026-08-16 | 5c37a02 | 11,128 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 (13757 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_qoq7zw5bec5dnfsm GET https://markdownregistry.com/api/v1/resolve?ref=peter-tu-zynkr/zynkr-skill-builder/consult-project-specialist GET https://markdownregistry.com/api/v1/blob/ecb823bfe42789924aba7d74c8a96379ef3e882eb435e5d05efe035e3bc3dd0d
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.