Borrowing it
Nothing to install: this file belongs to Othmane-Khadri/YALC-the-GTM-operating-system. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Othmane-Khadri/YALC-the-GTM-operating-system/main/.claude/skills/lemlist/cta-designer/SKILL.mdgit clone --depth 1 https://github.com/Othmane-Khadri/YALC-the-GTM-operating-systemWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/othmane-khadri/yalc-the-gtm-operating-system/cta-designer)<a href="https://agentmods.dev/skills/othmane-khadri/yalc-the-gtm-operating-system/cta-designer"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/cta-designer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/othmane-khadri/yalc-the-gtm-operating-system/cta-designer"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/cta-designer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00150 | $0.01442 |
| Opus 5 | $0.00075 | $0.00721 |
| Sonnet 5 | $0.00030 | $0.00288 |
| Haiku 4.5 | $0.00015 | $0.00144 |
Grade A, and why
cta-designer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CTA Designer — Permissionless Value Promise (PVP)
The core idea
Most outreach dies at the CTA. "Would you be open to a 30-minute call?" is high friction, seller-centric, and creates a binary lose/lose: the prospect either ignores it or commits to something they don't want yet.
A Permissionless Value Promise (PVP) flips this. The CTA itself delivers standalone value — an insight, a resource, a benchmark, a question — that the prospect finds genuinely useful before buying anything. They reply because they're curious, not because you pressured them.
A good PVP CTA:
- Gives something useful with no strings attached
- Doesn't mention your product or pitch anything
- Implies no obligation ("happy to share if useful")
- Is specific to their context (their industry, role, trigger, or pain)
- Requires a simple yes or short reply — not a calendar commitment
Step 1 — Gather context
Before generating CTAs, check the conversation for any existing context:
- ICP / company type: industry, size, growth stage
- Persona: role, seniority, their core pain
- Trigger: recent event (funding, hiring, tech change, job change, etc.)
- Your offer: what problem you solve and how
- Channel: email, LinkedIn DM, voice note
If critical context is missing (especially the persona's pain or your offer), ask 1–2 targeted questions. Never generate generic CTAs — specificity is what makes PVPs work.
Step 2 — Generate 5 PVP CTAs
Produce 5 CTAs across different angles. For each, write:
- The CTA itself (ready to paste into an email/message)
- Type (see below)
- Friction (🟢 Low / 🟡 Medium)
- Why it works (1 sentence)
Aim for at least 3 with 🟢 Low friction. Never propose a "book a call" CTA — that can come after the reply.
CTA Types
1. Insight CTA
You share a specific, public observation about their company or industry and offer to send a deeper analysis.
"I noticed [Company] has been [expanding into X / hiring heavily for Y / doing Z]. Put together a quick breakdown of how similar companies are handling [related pain]. Happy to forward it — useful or not?"
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 13d ago First seen · 126 lines · 150 tokens per session scan A e714d9c1d759
cta-designer is a skill published in the GitHub repository Othmane-Khadri/YALC-the-GTM-operating-system (301 stars, last pushed 23d ago), licensed MIT. It adds 150 tokens to every session and 1,442 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
cn-check
Install and run the Continue CLI (cn) to execute AI agent checks on local code changes. Use when asked to "run checks", "lint with AI", "review my changes with cn", or set up Continue CI locally.
kn-spec
Use when creating a specification document for a feature (SDD workflow).
kn-handoff
Use when a feature crosses repository boundaries and one side must hand work to the other - generates a self-contained frontend-to-backend brief or backend-to-frontend API contract.
kn-flow
Use when orchestrating a full Knowns spec or task wave through planning, implementation, review, integration, and verification, optionally using sub-agents when scopes are parallel-safe.
kn-research
Use when you need to understand existing code, find patterns, search project knowledge, investigate current external facts, or explore a large codebase before implementation.
kn-debug
Use when debugging errors, test failures, build issues, or blocked tasks — structured triage to fix to learn.