Loading...
Loading...
Found 8,750 Skills
Creates or updates professional-grade agent skills (SKILL.md + optional scripts/references/assets) with strict validation and an iterative generator↔critic workflow. Use when: you want a new skill, want to refactor an existing skill for clarity/token-efficiency, or want to reach an A-grade rubric score.
Handle HR workflows — onboarding, announcements, and employee comms.
Email marketing automation for HubSpot/Klaviyo/Mailchimp (and similar ESPs): design trigger-based lifecycle workflows (welcome, onboarding, nurture, win-back, cart abandonment), define segmentation + suppression/frequency policies, troubleshoot deliverability (SPF/DKIM/DMARC, one-click unsubscribe, list hygiene), and measure incrementality/ROI (holdouts, RPE, retention economics).
Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team of 2+ agents with different specializations, (2) Defining task routing and lifecycle (inbox → spec → build → review → done), (3) Creating handoff protocols between agents, (4) Establishing review and quality gates, (5) Managing async communication and artifact sharing between agents.
Scaffold or continue a software project with a Harness-style workflow. Use when the user wants a new app or repo, a structured bootstrap, or milestone-driven execution from PRD through implementation. Supports greenfield and existing codebases across web, iOS, CLI, agent, and desktop projects.
Dispatch a swain artifact to a GitHub Actions runner for autonomous implementation via Claude Code Action. Creates a GitHub Issue with the artifact content and triggers the workflow for background execution. Use when the user says 'dispatch', 'send to background agent', 'run this autonomously', 'GitHub Actions', or wants to hand off a SPEC for autonomous implementation.
Use this skill when building workflow automations with Zapier, Make (Integromat), n8n, or similar no-code/low-code platforms. Triggers on workflow automation, Zap creation, Make scenario design, n8n workflow building, webhook routing, internal tooling automation, app integration, trigger-action patterns, and any task requiring connecting SaaS tools without writing full applications.
Use this skill alongside figma-use when the task involves translating an application page, view, or multi-section layout into Figma. Triggers: 'write to Figma', 'create in Figma from code', 'push page to Figma', 'take this app/page and build it in Figma', 'create a screen', 'build a landing page in Figma', 'update the Figma screen to match code'. This is the preferred workflow skill whenever the user wants to build or update a full page, screen, or view in Figma from code or a description. Discovers design system components, variables, and styles via search_design_system, imports them, and assembles screens incrementally section-by-section using design system tokens instead of hardcoded values.
Interpret buying signals and prioritize accounts for outreach. Use when analyzing intent data, prioritizing accounts, reading buying signals, tracking job changes, using intent topics, scoring leads, deciding who to contact first, or building signal-based outreach workflows. Do NOT use for building prospect lists (use /sales-prospect-list), enriching contacts (use /sales-enrich), or general Apollo platform help (use /sales-apollo).
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for queues, async workers, cron jobs, delayed tasks, retry behavior, worker-only config drift, and payload-to-side-effect chains. Use when the user asks to trace a queue payload, inspect async job execution, explain worker-only behavior, follow retries or dead-letter handling, or connect an enqueued item to a later file, cache, email, or privilege-bearing side effect. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
Flodesk integration. Manage Users, Subscribers, Emails, Workflows. Use when the user wants to interact with Flodesk data.
RootFi integration. Manage data, records, and automate workflows. Use when the user wants to interact with RootFi data.