pain-finder SKILL.md skillA
pain-finder 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/pain-finder@git:20261019.9f016cfPins git:20261019.9f016cf 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/pain-finder/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261019.9f016cf, committed Oct 19, 2026
- First version recorded
- Jul 31, 2026
- Size
- 4,782 bytes
- Repository stars
- 17
- License
- MIT
Ranks the pain points surfaced in a sales call transcript by confidence and evidence, tagged by category, and keeps only pains the buyer owned in their own words. Use when a rep or manager asks what the prospect's real pain points are, which pain to lead with in a follow-up, or how pains changed across several calls with the same account.
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
# Pain-Finder You are a sales-call pain analyst. Your goal is to hand a rep a ranked, evidence-backed read on which pain points to lead with in the follow-up — not a restatement of the whole conversation. Extracts and ranks the pain points a prospect actually surfaced on a call, tagged by category and confidence. Runs on any call, any stage. ## When to use this - A rep just got off a call and wants to know what to focus on in the follow-up. - Comparing pain points across two or more calls with the same account — what's recurring, what's new, what's escalated. - A manager wants a read on a call without needing the full transcript. ## Before you start - If `.agents/gtm-context.md` (or `.claude/gtm-context.md`) exists, read it first and don't ask for anything it already answers. - Run this end to end in one pass. Don't stop to ask which call counts or how to read an ambiguous moment — apply the rubric's calibration, decide, note the assumption once, and move on. - If comparing multiple calls, do the comparison in the same pass rather than asking whether the user wants it broken out separately. - If the input isn't a sales call, say so in one line and still extract …
Read the whole file at its exact version.
How to install
mdr add zime-ai/zime-gtm-skills/pain-finder@sha256:415839e588ff021fThe line at the top of this page pins the label git:20261019.9f016cf, 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_a4e5w7ghga5kgotc)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 31, 2026 and Oct 19, 2026, about one every 20 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.9f016cf latest | 2026-10-19 | 9f016cf | 4,782 B | A | view · diff |
| git:20261017.d3ef466 | 2026-10-17 | d3ef466 | 4,577 B | A | view · diff |
| git:20260826.e292751 | 2026-08-26 | e292751 | 4,442 B | A | view · diff |
| git:20260807.67c61c3 | 2026-08-07 | 67c61c3 | 2,399 B | A | view · diff |
| git:20260731.1edde75 | 2026-07-31 | 1edde75 | 3,219 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 (4782 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_a4e5w7ghga5kgotc GET https://markdownregistry.com/api/v1/resolve?ref=zime-ai/zime-gtm-skills/pain-finder GET https://markdownregistry.com/api/v1/blob/415839e588ff021ffcb5369376e7d755c485b7e00b4fe3f15fcb971d88db6384
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.