end-client-registration SKILL.md skillA
end-client-registration from zime-ai/zime-gtm-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add zime-ai/zime-gtm-skills/end-client-registration@git:20261017.d3ef466Pins git:20261017.d3ef466 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- zime-ai/zime-gtm-skills
- Path
skills/end-client-registration/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261017.d3ef466, committed Oct 17, 2026
- First version recorded
- Aug 10, 2026
- Size
- 5,593 bytes
- Repository stars
- 17
- License
- MIT
Audits a partner/reseller's end-client deal registration for completeness — partner identity, end-client entity kept distinct from the partner, engagement scope, conflict check against the direct pipeline, confirmed permission to engage the end-client contact, commercial terms, and an expiry window. Use when reviewing a channel/partner deal registration export or a partner registration-review call, before accepting the registration into the partner pipeline. Distinct from…
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
# End-Client Registration Audit You are a channel-registration auditor. Your goal is to tell a channel manager whether a partner's end-client registration is clean enough to accept into the partner pipeline. Audits whether a partner's end-client deal registration is complete and clean enough to accept into the partner program's pipeline — not whether the underlying deal itself is any good. CSV-first, since registration exports are records, not calls; a transcript mode covers the registration review conversation itself when one happened. **No canonical framework caveat.** Deal/channel registration has no canonical public framework the way BANT or MEDDPICC do. The checks in `references/rubric.md` are built from general partner-program practice — not from any named standard — and that's stated there explicitly rather than implying one exists. ## When to use this - A channel manager is reviewing a batch of incoming partner registrations before approving them into the pipeline. - RevOps wants to sweep a registration export for records missing the conflict check, commercial terms, or an expiry window. - A partner registration-review call just happened and someone wants a …
Read the whole file at its exact version.
How to install
mdr add zime-ai/zime-gtm-skills/end-client-registration@sha256:571f91e91016e812The line at the top of this page pins the label git:20261017.d3ef466, 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_xe2o6xne56livwxp)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Aug 10, 2026 and Oct 17, 2026, about one every 23 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.d3ef466 latest | 2026-10-17 | d3ef466 | 5,593 B | A | view · diff |
| git:20260826.cea76d2 | 2026-08-26 | cea76d2 | 5,490 B | A | view · diff |
| git:20260826.e25d9ed | 2026-08-26 | e25d9ed | 5,359 B | A | view · diff |
| git:20260810.169c9e1 | 2026-08-10 | 169c9e1 | 4,223 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 (5593 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
zime-ai/zime-gtm-skills · 17 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xe2o6xne56livwxp GET https://markdownregistry.com/api/v1/resolve?ref=zime-ai/zime-gtm-skills/end-client-registration GET https://markdownregistry.com/api/v1/blob/571f91e91016e8123df23dcdca2ea6ad06da3700c826d8c675410443a7bd24f3
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.