Loading...
Loading...
Found 10,598 Skills
This skill should be used when the user asks to "initialize search", "set up semantic search", "enable qmd", "add search to secondbrain", or mentions wanting to enable semantic search capabilities for an existing secondbrain project.
Coordinates 9 specialized audit workers (security, build, architecture, code quality, dependencies, dead code, observability, concurrency, lifecycle). Researches best practices, delegates parallel audits, aggregates results into single Linear task in Epic 0.
Master of capital preservation and position sizing - combining Kelly Criterion, volatility targeting, correlation analysis, and drawdown management to survive and thrive in marketsUse when "risk management, position size, stop loss, drawdown, kelly, risk per trade, portfolio risk, volatility, max loss, trading, risk-management, position-sizing, kelly-criterion, drawdown, volatility, stop-loss, portfolio-risk" mentioned.
Expert negotiation coaching combining Harvard, Kellogg, Wharton, HBS, and FBI methodologies. Use when: (1) preparing for any negotiation (salary, contracts, deals, disputes), (2) during a negotiation for real-time tactics, (3) analyzing failed negotiations, (4) coaching someone through difficult conversations, (5) resolving conflicts. Covers: BATNA analysis, MESOs, tactical empathy, anchoring, reframing, and more.
Write and run Playwright E2E tests for Redpanda Console using testcontainers. Analyzes test failures, adds missing testids, and improves test stability. Use when user requests E2E tests, Playwright tests, integration tests, test failures, missing testids, or mentions 'test workflow', 'browser testing', 'end-to-end', or 'testcontainers'.
Use when user describes a complex project goal, wants to set up multiple skills at once, asks "what skills do I need for X", or needs to manage installed skill bundles. Triggers on multi-skill setup, skill combination, project bootstrapping, or batch skill management.
Use when `spec.md`, `plan.md`, and `tasks.md` exist and you need a read-only Spec Kit audit for consistency, requirement-to-task coverage, ambiguity, duplication, or constitution conflicts before implementation.
Specification-driven development with structured phases: Initialize, Plan, Tasks, Implement+Validate. Creates structured feature specs with traceability to requirements. Use when: starting projects, planning features, implementing with verification, or tracking decisions across sessions. Triggers on "map codebase", "initialize", "initialize project", "create feature", "plan", "tasks", "implement", "validate", "archive".
Power systems engineering covering grid modeling, power flow analysis, energy storage dispatch, demand response, and electricity market economics. Spans transmission/distribution planning to real-time operations. Use when "power flow|load flow|grid model, energy storage|battery dispatch|ESS, demand response|load management|peak shaving, electricity market|LMP|locational marginal price, grid stability|frequency|voltage, capacity planning|resource adequacy, unit commitment|economic dispatch, transmission|distribution|power system, " mentioned.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Use when asked to inspect video file metadata, get video duration, resolution, codec information, frame rate, or bitrate.
Decision-making framework for software development, Y Combinator / Silicon Valley style. Based on real principles from Paul Graham, Sam Altman, Michael Seibel, Patrick Collison, and Brian Chesky. Use when: - Developing features or products - Making technical decisions (what to do, how, when) - Prioritizing work (P0, P1, P2) - Evaluating whether to refactor or patch - Deciding on technical debt - Evaluating whether to add tests, CI/CD, or automation - Any architecture or engineering decision Triggers: development, code, feature, refactor, architecture, prioritize, technical decision, what to do first, technical debt, tests, CI/CD, sprint, backlog