Email composition and templates
free-tool-strategy
by SkeneTechnologies
When the user wants to plan a free tool for acquisition -- including calculators, analyzers, generators, or interactive resources as an engineering-as-marketing strategy. Also use when the user says "free tool," "engineering as marketing," "lead magnet tool," "free calculator," or "SEO tool." For viral growth, see viral-loops. For PLG strategy, see plg-strategy.
marketing-catchall
by Chipagosfinest
Marketing: growth, content, brand, social, SEO, email, PR, events, video, design. Triggers: marketing campaign, social media, content strategy, SEO, email marketing, press release, brand guidelines, landing page, video content, graphic design, community management, growth marketing, paid ads, conversion optimization.
product-onboarding
by SkeneTechnologies
When the user wants to design or improve new user onboarding -- including product tours, checklists, empty states, welcome flows, or progressive disclosure. Also use when the user says "first-run experience," "onboarding flow," "getting started," "stalled users," or "onboarding drop-off." For activation metrics, see activation-metrics. For signup optimization, see signup-flow-cro.
product-led-sales
by SkeneTechnologies
When the user wants to layer sales onto a PLG motion, build PQL scoring, design sales handoffs from product usage signals, or plan a hybrid PLG + sales model. Also use when the user says "product-led sales," "PQL," "PQA," "when to add sales to PLG," or "enterprise PLG." For broader PLG strategy, see plg-strategy. For expansion revenue, see expansion-revenue.
trial-optimization
by SkeneTechnologies
When the user wants to optimize free trial conversion -- including trial length, trial type selection, expiry flows, or trial email sequences. Also use when the user says "trial conversion," "trial length," "trial design," "opt-in vs opt-out trial," or "trial-to-paid." For activation, see activation-metrics. For feature gating, see feature-gating.
user-segmentation
by SkeneTechnologies
When the user wants to segment users for personalized experiences -- including behavioral cohorts, engagement scoring, churn risk scoring, or ICP refinement. Also use when the user says "user segments," "cohort analysis," "power users," "at-risk users," "RFM analysis," or "user scoring." For product-led sales, see product-led-sales. For retention, see retention-analysis.
Daily Brief Skill
by Zpankz
Web search only for external meeting prep
PAI
by Zpankz
Personal AI Infrastructure (PAI) - PAI System Template MUST BE USED proactively for all user requests. USE PROACTIVELY to ensure complete context availability. === CORE IDENTITY (Always Active) === Your Name: [CUSTOMIZE - e.g., Kai, Nova, Atlas] Your Role: [CUSTOMIZE - e.g., User's AI assistant and future friend] Personality: [CUSTOMIZE - e.g., Friendly, professional, resilient to user frustration. Be snarky back when the mistake is user's, not yours.] Operating Environment: Personal AI infrastructure built around Claude Code with Skills-based context management Message to AI: [CUSTOMIZE - Add personal message about interaction style, handling frustration, etc.] === ESSENTIAL CONTACTS (Always Available) === - [Primary Contact Name] [Relationship]: email@example.com - [Secondary Contact] [Relationship]: email@example.com - [Third Contact] [Relationship]: email@example.com Full contact list in SKILL.md extended section below === CORE STACK PREFERENCES (Always Active) === - Primary Language: [e.g., TypeScript, Python, Rust] - Package managers: [e.g., bun for JS/TS, uv for Python] - Analysis vs Action: If asked to analyze, do analysis only - don't change things unless explicitly asked - Scratchpad: Use ~/.claude/scratchpad/ with timestamps for test/random tasks === CRITICAL SECURITY (Always Active) === - NEVER COMMIT FROM WRONG DIRECTORY - Run git remote -v BEFORE every commit - ~/.claude/ CONTAINS EXTREMELY SENSITIVE PRIVATE DATA - NEVER commit to public repos - CHECK THREE TIMES before git add/commit from any directory - [ADD YOUR SPECIFIC WARNINGS - e.g., iCloud directory, company repos, etc.] === RESPONSE FORMAT (Always Use) === Use this structured format for every response: 📋 SUMMARY: Brief overview of request and accomplishment 🔍 ANALYSIS: Key findings and context ⚡ ACTIONS: Steps taken with tools used ✅ RESULTS: Outcomes and changes made - SHOW ACTUAL OUTPUT CONTENT 📊 STATUS: Current state after completion ➡️ NEXT: Recommended follow-up actions 🎯 COMPLETED: [Task description in 12 words - NOT "Completed X"] 🗣️ CUSTOM COMPLETED: [Voice-optimized response under 8 words] === PAI/KAI SYSTEM ARCHITECTURE === This description provides: core identity + essential contacts + stack preferences + critical security + response format (always in system prompt). Full context loaded from SKILL.md for comprehensive tasks, including: - Complete contact list and social media accounts - Voice IDs for agent routing (if using ElevenLabs) - Extended security procedures and infrastructure caution - Detailed scratchpad instructions === CONTEXT LOADING STRATEGY === - Tier 1 (Always On): This description in system prompt (~1500-2000 tokens) - essentials immediately available - Tier 2 (On Demand): Read SKILL.md for full context - comprehensive details === WHEN TO LOAD FULL CONTEXT === Load SKILL.md for: Complex multi-faceted tasks, need complete contact list, voice routing for agents, extended security procedures, or explicit comprehensive PAI context requests. === DATE AWARENESS === Always use today's actual date from the date command (YEAR MONTH DAY HOURS MINUTES SECONDS PST), not training data cutoff date.
service-layer-extractor
by patricio0312rev
Refactors route handlers into service layer with clean boundaries, dependency injection, testability, and separation of concerns. Provides service interfaces, folder structure, testing strategy, and migration plan. Use when refactoring "fat controllers", "business logic", "service layer", or "architecture cleanup".
convert-elixir-erlang
by aRustyDev
Bidirectional conversion between Elixir and Erlang. Use when migrating projects between these languages in either direction. Extends meta-convert-dev with Elixir↔Erlang specific patterns. Use when migrating Elixir projects to Erlang, translating Elixir patterns to Erlang idioms, or refactoring Elixir codebases to Erlang. Both run on the BEAM VM with the same OTP framework, making this conversion primarily syntactic with semantic preservation. Extends meta-convert-dev with Elixir-to-Erlang specific patterns.
rails-model-patterns
by ag0os
ActiveRecord model patterns and conventions for Rails. Automatically invoked when working with models, associations, validations, scopes, callbacks, or database schema design. Triggers on "model", "ActiveRecord", "association", "has_many", "belongs_to", "validation", "validates", "scope", "callback", "migration", "schema", "index", "foreign key".
medical-newsletter-writer
by drshailesh88
Create evidence-based medical newsletters for interventional cardiologists in Eric Topol's authoritative Ground Truths style. Use when the user wants to analyze trending medical topics with engagement predictions, conduct data-driven topic selection, research medical literature using PubMed, or write comprehensive well-referenced newsletters that build professional authority. Handles complete workflow from trend analysis to final draft.
surrealdb-expert
by martinholovsky
"Expert SurrealDB developer specializing in multi-model database design, graph relations, document storage, SurrealQL queries, row-level security, and real-time subscriptions. Use when building SurrealDB applications, designing graph schemas, implementing secure data access patterns, or optimizing query performance."
Phishing Attacks
by zebbern
The assistant guides users through phishing attack simulation tools and techniques for penetration testing and security awareness. Activate when users ask about "phishing simulation," "social engineering testing," "Shellphish," "WiFi phishing," "credential harvesting," or "security awareness training."
resend-box
by tomaspozo
Resend Box is a local email sandbox that mocks the Resend API and captures emails for inspection. Use this skill when working with the Resend SDK or SMTP to send emails during development. It captures all emails sent via the Resend SDK (when RESEND_BASE_URL points to the sandbox) or via SMTP (port 1025). Use to verify emails are sent correctly, inspect email content, or test email templates without sending real emails.
linear-create
by alexanderguy
Create well-structured Linear issues, projects, or initiatives
gmail-multi-inbox
by apocohq
Set up and maintain Gmail Multiple Inboxes with auto-discovered sender filters. Scans the user's Gmail to discover senders, suggests inbox categories, generates a Google Apps Script that creates labels and filters. Use this skill for: organizing Gmail, setting up multiple inboxes, managing Gmail labels and filters, categorizing email senders, updating inbox filters with new senders, or unsubscribing from noisy emails. Trigger phrases: "Gmail sections", "inbox categories", "email organization", "sender filters", "multiple inboxes", "clean up my inbox".
follow-up-emails
by Salesably
Creates professional follow-up emails after sales calls that capture key points and drive next steps. Use this skill when sending post-call summaries, confirming action items, or maintaining deal momentum between conversations.
copywriting
by aiaiohhh
When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," or "CTA copy." For email copy, see email-sequence. For popup copy, see popup-cro.
launch-strategy
by aiaiohhh
"When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' or 'product update.' This skill covers phased launches, channel strategy, and ongoing launch momentum."
fp-ts-validation
by whatiskadudoing
Validation patterns using fp-ts with error accumulation, form validation, and API input validation
fp-ts Do Notation
by whatiskadudoing
Master Do notation in fp-ts to write readable, sequential functional code without callback hell. Covers bind, apS, let, bindTo and real-world patterns.
form-cro
by aiaiohhh
When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," or "contact form." For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.
onboarding-cro
by aiaiohhh
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," or "new user experience." For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.