Loading...
Loading...
Found 344 Skills
Execute tasks through systematic exploration, pruning, and expansion using Tree of Thoughts methodology with multi-agent evaluation
MUST READ before running any ADK evaluation. ADK evaluation methodology — eval metrics, evalset schema, LLM-as-judge, tool trajectory scoring, and common failure causes. Use when evaluating agent quality, running adk eval, or debugging eval results. Do NOT use for API code patterns (use adk-cheatsheet), deployment (use adk-deploy-guide), or project scaffolding (use adk-scaffold).
Customer-centric conversion rate optimization methodology based on "Making Websites Win" by Karl Blanks and Ben Jesson (Conversion Rate Experts). Use when optimizing websites, landing pages, funnels, improving conversion rates, analyzing why visitors don't convert, creating persuasive copy, designing A/B tests, auditing UX, or building customer-centric websites. Provides systematic CRO process, objection/counter-objection framework, and evidence-based optimization techniques.
LLM-as-judge methodology for comparing code implementations across repositories. Scores implementations on functionality, security, test quality, overengineering, and dead code using weighted rubrics. Used by /beagle:llm-judge command.
Screen and identify undervalued stocks with strong fundamentals using professional equity research methodology. Use when the user asks to find undervalued stocks, screen for cheap or bargain stocks, identify value investing opportunities, perform fundamental stock analysis, find stocks trading below intrinsic value, or requests a stock screener based on financial metrics like P/E ratio, debt-to-equity, free cash flow, or ROIC.
Create Product Requirements Documents (PRD) following SDD methodology - Layer 2 artifact defining product features and user needs
Guides LLM agents through large-scale coding tasks using a spec-driven, phase-by-phase methodology covering requirement definition, planning, algorithm design, and implementation with OOP principles and language-specific coding standards. Use when starting a new software project, implementing a complex feature, refactoring existing code, or when you need a disciplined step-by-step approach to any non-trivial coding task.
End-to-end project engineering — from understanding user intent to architecture design, incremental build with verification, and systematic debugging. Covers scheduled tasks (cron jobs), dashboards, web apps, APIs, scripts, and any software the user wants built. Replaces coder + preview-dev with a unified methodology.
Philip Tetlock's Superforecasting framework applied to a business decision, investment thesis, or strategic question. Spawns a team of specialist agents — Calibrator, Decomposer, Updater, Devil's Advocate, Scorekeeper — who each apply a different piece of the superforecasting methodology. The lead synthesizes into a calibrated probability estimate with Brier-scoreable predictions, explicit base rates, and an accountability structure for keeping score over time. Use when the user says "tetlock this", "what's the probability", "how confident should I be", "forecast this", "calibrate this", proposes a business thesis and wants probabilistic stress-testing, or wants to apply superforecasting to a decision. Works standalone or after /munger.
Product marketing, positioning, GTM strategy, and competitive intelligence. Includes ICP definition, April Dunford positioning methodology, launch playbooks, competitive battlecards, and international market entry guides. Use when developing positioning, planning product launches, creating messaging, analyzing competitors, entering new markets, enabling sales, or when user mentions product marketing, positioning, GTM, go-to-market, competitive analysis, market entry, or sales enablement.
Transform vague prompts into precise, well-structured specifications using EARS (Easy Approach to Requirements Syntax) methodology. This skill should be used when users provide loose requirements, ambiguous feature descriptions, or need to enhance prompts for AI-generated code, products, or documents. Triggers include requests to "optimize my prompt", "improve this requirement", "make this more specific", or when raw requirements lack detail and structure.
Perform 12-Factor App compliance analysis on any codebase. Use when evaluating application architecture, auditing SaaS applications, or reviewing cloud-native applications against the original 12-Factor methodology.