Claude recently released Skills. So we built the biggest skills database for GTM. And I’m sharing it for free - you literally copy + paste into Claude. Outbound • email-infra – checks deliverability basics so you don’t nuke domains • list-building – builds ICP lists + exclusions + prioritization • copywriting – writes sequences that don’t sound like templates • clay-operations – enrichment + waterfall logic + clean field mapping RevOps • inbound-orchestration – capture → qualify → route → follow-up flows • lead-routing – ownership rules, SLAs, edge cases, round robin • lifecycle-model – MQL/SQL/SAO definitions + required fields • pipeline-reporting – weekly exec view: created, influenced, velocity ABM • account-selection – fit + signals → tiering • persona-mapping – buying roles, pains, triggers, proof points • linkedin-ads – structure, testing plan, creative direction • ads-outbound-signaling – sync ads → outbound And those are just a few. We’re constantly updating the database with new Skills + improved versions. How to use them - Copy/paste the Skills I send you into Claude - Tell it what you need - It reads the Skill, then helps you execute That’s it. No complex setup. No API keys. No code. Just copy, paste, ask. Comment “Claude” and I’ll send you free access.

Everyone's going crazy about Claude skills. Nobody talks about the architecture that makes them work. A skill without a framework around it is just a fancy prompt that drifts after 2 sessions. Here's how to actually structure Claude Code so it compounds: Every project needs 5 layers: 1) Identity - one file that's always loaded. Tells Claude who it is, what the rules are, and where to route tasks. 2) Rules - guardrails that load automatically based on what folder you're working in. No manual prompting. 3) Skills - step-by-step workflows. Only activated when a task matches. Not everything loads at once - that's the point. 4) Agents - sub-agents running on cheaper models. Research, code review, QA. Each one isolated, each one focused. 5) Memory - persistent state across sessions. What Claude learned yesterday, it remembers today. That's the foundation. But here's where it gets powerful. Separate the brain from the muscle. The brain (governance) holds your SOPs, quality standards, and blueprints. It audits. It reviews. It enforces consistency. The muscle (operations) does the actual work. Ads, outbound, content, RevOps. Key rule: working agents never modify their own instructions. They file improvement proposals. The brain reviews. You confirm. Changes go live. That's how the system learns without drifting. Inside operations, 3 layers: 1) Knowledge - strategy and methodology. Playbooks. Never touches live APIs. 2) Execution - bots and scripts. Real operations. Never makes strategic calls. 3) Context - i.e: per-client data. Completely isolated from each other. Each layer loads its own rules automatically based on where you're working. What this gives you: → Every skill gets built the same way → Rules fire without you thinking about it → Memory carries forward (no re-explaining every session) → Every correction you make compounds over time → Destructive actions get blocked before they run This is the difference between "I use Claude Code" and "Claude Code powers my GTM." I built a full framework - folder structure, governance loops, knowledge tiers, self-improvement cycle, everything. Comment "FRAMEWORK" and I'll send it.