lead-signals SKILL.md skillA
lead-signals from superdesigndev/treg is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add superdesigndev/treg/lead-signals@git:20261101.393c42dPins git:20261101.393c42d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- superdesigndev/treg
- Path
src/treg/web/skills/lead-signals/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261101.393c42d, committed Nov 1, 2026
- First version recorded
- Sep 28, 2026
- Size
- 5,569 bytes
- Repository stars
- 7,162
- License
- a license file GitHub does not identify
Use when the user wants to find buyers, warm or hot leads, or in-market accounts; asks about buying signals, intent signals or trigger events; wants to know who is complaining about a problem, engaging with a post, hiring for a role, changing jobs, raising money or adopting a tool; or wants to monitor a topic, a competitor or a list of accounts for people ready to buy.
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
# Lead signals
A signal is a public fact that makes a conversation timely: someone complained about the problem you
solve, engaged with a post about it, hired for it, raised money, switched tools.
Runs on treg, through its MCP tools or the `treg` CLI; either is enough. Over MCP, each command
below maps onto a tool: `treg catalog search` is `catalog_search`, `treg catalog get` is
`catalog_get`, `treg call` is `call`. With neither, treg is not set up: {BASE}/llms.txt says how.
Install only if the human asked you to; otherwise tell them how and stop.
## The run
1. **Detect** raw signals for the user's buyer.
2. **Qualify.** Drop the noise; most runs discard more than half. A signal list is not a lead list.
3. **Contact.** Company → decision maker → work email, only for rows that survived.
4. **Hand back** a ranked list: person, company, the signal, *why now* in one line, source link, email
if found. State coverage plainly: "1,180 engaged, 800 emails found".
Default for "find buyers for X" or "monitor Y": search posts about the pain on LinkedIn, X and Reddit →
read the comments and reactions on the best posts → keep people whose title fits → roll them up by
…Read the whole file at its exact version.
How to install
mdr add superdesigndev/treg/lead-signals@sha256:d8f22b4ade61c80eThe line at the top of this page pins the label git:20261101.393c42d, 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_t2uijy7w5kulp7h4)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Sep 28, 2026 and Nov 1, 2026, about one every 17 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261101.393c42d latest | 2026-11-01 | 393c42d | 5,569 B | A | view · diff |
| git:20261027.d08ee08 | 2026-10-27 | d08ee08 | 5,393 B | A | view · diff |
| git:20260928.ce916f2 | 2026-09-28 | ce916f2 | 5,175 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 (5569 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
superdesigndev/treg · 7,162 stars · license a license file GitHub does not identify · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_t2uijy7w5kulp7h4 GET https://markdownregistry.com/api/v1/resolve?ref=superdesigndev/treg/lead-signals GET https://markdownregistry.com/api/v1/blob/d8f22b4ade61c80e2c9f827df999a07385c8db792751419990bd6b4ac262beb6
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.
More from superdesigndev/treg
Every file in superdesigndev/treg