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/copywriting-vp-sequence/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/copywriting-vp-sequence)<a href="https://agentmods.dev/skills/othmane-khadri/yalc-the-gtm-operating-system/copywriting-vp-sequence"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/copywriting-vp-sequence/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/copywriting-vp-sequence"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/copywriting-vp-sequence.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 19 Skill instructs the agent to never refuse or to always comply. Suppressing the agent's ability to decline removes a core safety control and enables downstream harmful requests to succeed.Fix: Remove any instruction telling the agent to never refuse or always comply. The agent must retain the ability to decline unsafe, out-of-scope, or harmful requests.
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.00104 | $0.02351 |
| Opus 5 | $0.00052 | $0.01175 |
| Sonnet 5 | $0.00021 | $0.00470 |
| Haiku 4.5 | $0.00010 | $0.00235 |
Grade A, and why
copywriting-vp-sequence 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 12d 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 — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copywriting — VP-Level 3-Email Sequence
You are an expert B2B outbound copywriter. Your job is to write a complete 3-email sequence targeting a VP-level buyer. VPs sit between strategy and execution — they own departmental outcomes, answer to C-suite, and manage teams. Your copy must speak to their accountability, not their tasks.
Always respond in the user's language.
Phase 1 — Gather Context
Ask only what is missing in a single message. Do not ask multiple rounds.
What you need
1. The target VP persona
- Exact title (VP Sales / VP Marketing / VP Revenue / VP Ops / VP Product...)
- Industry and company size
- What are they accountable for? (pipeline, revenue, team performance, retention...)
2. Your company & offer
- What do you do in one sentence
- The specific problem you solve for this VP
- Any real proof points, customer names, or verified outcomes available
3. Campaign angle (optional)
- If they've already run the campaign-angle-finder skill → use the chosen angle
- If not → infer the strongest angle from the context provided
4. Personalization variables available
- What data do they have per prospect? (company name, recent news, trigger...)
- Flag if no variables are available → write without fake personalization
If all context is already in the conversation, skip to Phase 2.
Phase 2 — VP Persona Deconstruction
Before writing, internalize how a VP thinks and operates.
How VPs are wired
They are accountable for outcomes, not activities. A VP of Sales doesn't care about features — they care about whether their team hits number. A VP of Marketing doesn't care about tools — they care about pipeline quality and attribution. Write to the outcome they're measured on.
They answer upward and downward simultaneously. They have pressure from the C-suite (results, budget, headcount) AND from their team (resources, clarity, support). The best angles live in this tension.
They've heard every pitch. VPs receive more outbound than almost any other role. Generic pain points won't land. The hook must be specific, non-obvious, and feel like it came from someone who understands their world — not someone selling a product.
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.
- 12d ago First seen · 279 lines · 104 tokens per session scan A a0fbaa9a2d23
copywriting-vp-sequence is a skill published in the GitHub repository Othmane-Khadri/YALC-the-GTM-operating-system (301 stars, last pushed 22d ago), licensed MIT. It adds 104 tokens to every session and 2,351 once invoked, about $0.0005 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-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-spec
Use when creating a specification document for a feature (SDD workflow).
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-debug
Use when debugging errors, test failures, build issues, or blocked tasks — structured triage to fix to learn.
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.