Total 46,960 skills
Showing 12 of 46960 skills
Sense accessibility barriers with gentle awareness. Listen to the forest, scan for obstacles, test the paths, guide toward inclusion, and protect all wanderers. Use when auditing accessibility, testing for a11y, or ensuring inclusive design.
Docker development environment CLI. Use for managing containers (start/stop/restart), executing commands in services, viewing logs, and running project scripts from kool.yml.
Research and use customer language across Product and Marketing. Sales Safari methodology for finding watering holes, extracting pain language, and creating "OH YEAH!" resonance.
Process large datasets efficiently using chunk(), chunkById(), lazy(), and cursor() to reduce memory consumption and improve performance
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.
Compare FinOps metrics across multiple repositories in an organization
Use this skill when working on infrastructure, DevOps, CI/CD, Kubernetes, cloud deployment, observability, or cost optimization. Activates on mentions of Kubernetes, Docker, Terraform, Pulumi, OpenTofu, GitOps, Argo CD, Flux, CI/CD, GitHub Actions, observability, OpenTelemetry, Prometheus, Grafana, AWS, GCP, Azure, infrastructure as code, platform engineering, FinOps, or cloud costs.
The drum sounds. Bear and Bloodhound gather for safe data movement. Use when migrating data that requires both careful movement and codebase understanding.
X (Twitter) algorithm rules, viral strategies, and article best practices. Boost engagement, avoid reach death, write posts that actually perform.
Capture AI agent sessions in your git workflow. Use for setup, rewinding to checkpoints, exploring session history, and troubleshooting.
McKinsey-style issue tree framework for breaking down complex problems into MECE (Mutually Exclusive, Collectively Exhaustive) components. Use when users need to decompose strategic questions, structure analysis, create work plans, or prepare for case interviews. Apply hypothesis-driven approach to problem-solving.
WHEN: User is writing HTML/templates with Tailwind CSS classes, styling components, configuring Tailwind themes, asking about Tailwind utilities or patterns, or working with any project that uses Tailwind CSS WHEN NOT: Non-Tailwind CSS questions, general HTML/CSS without Tailwind context, questions about other CSS frameworks (Bootstrap, etc.)