whetstone-signal SKILL.md skillA
whetstone-signal from coolxeo/grok-bot-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add coolxeo/grok-bot-skills/whetstone-signal@git:20261113.fadcb52Pins git:20261113.fadcb52 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- coolxeo/grok-bot-skills
- Path
skills/ads/whetstone-signal/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261113.fadcb52, committed Nov 13, 2026
- First version recorded
- Oct 27, 2026
- Size
- 11,627 bytes
- Repository stars
- 8
- License
- MIT
Use this when ad campaigns that let the platform pick the audience (Meta Advantage+, Google Performance Max, Google Demand Gen, or similar) bring plenty of cheap leads, signups, or clicks that rarely turn into revenue. Helps you choose the conversion event the algorithm should chase, score and send back higher quality conversions, and check the results against your own backend numbers. Also use it when setting up a new automated campaign and deciding what to optimize for.
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
# Whetstone Signal Automated ad campaigns pick the audience for you. They look for people similar to the ones who already converted. The setting still in your hands is what counts as a conversion. If that is "filled in a form," the system gets very good at finding form fillers, including the ones who never pick up the phone. This skill sharpens that target. You pick an event closer to revenue, make sure it happens often enough for the platform to learn, and send it back with a value attached. Then you check your own sales numbers to confirm the change helped. ## When to use - Cost per lead looks good but sales says most leads are junk. - A new Advantage+, Performance Max, or Demand Gen campaign needs an optimization goal. - The platform reports more conversions than your CRM or database can find. - You want value-based bidding but have no honest values to send. - Retargeting or prospecting keeps reaching existing customers or staff. Skip it when the account has fewer than about 10 conversions a week of any kind. Fix traffic or offer first. ## Inputs to ask for Ask for these before you recommend anything. If the user cannot answer one, …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_xo5b2dxtyfik32kv/8366c4601dc37a677ba4bc7aef9c2e518207a5c0a3199b557ad79588fa45b3c3.json
Then /plugin install whetstone-signal@markdownregistry-xo5b2dxtyfik32kv in Claude Code. It installs git:20261113.fadcb52, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add coolxeo/grok-bot-skills/whetstone-signal@sha256:8366c4601dc37a67The line at the top of this page pins the label git:20261113.fadcb52, 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_xo5b2dxtyfik32kv)
3 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in coolxeo/grok-bot-skills/whetstone-signal since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of whetstone-signal from somewhere else? Ask it: where did my whetstone-signal come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 3 versions of this file, between Oct 27, 2026 and Nov 13, 2026, about one every 8 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261113.fadcb52 latest | 2026-11-13 | fadcb52 | 11,627 B | A | view · diff |
| git:20261113.cf8e7f6 | 2026-11-13 | cf8e7f6 | 11,644 B | A | view · diff |
| git:20261027.b3b547b | 2026-10-27 | b3b547b | 11,530 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/whetstone-signal/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (11627 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
coolxeo/grok-bot-skills · 8 stars · license MIT · pushed 2026-11-14 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xo5b2dxtyfik32kv GET https://markdownregistry.com/api/v1/resolve?ref=coolxeo/grok-bot-skills/whetstone-signal GET https://markdownregistry.com/api/v1/blob/8366c4601dc37a677ba4bc7aef9c2e518207a5c0a3199b557ad79588fa45b3c3
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 coolxeo/grok-bot-skills
Every file in coolxeo/grok-bot-skills