curiosity-loops
Use when facing a significant decision (career pivot, product direction, technical choice) and feeling stuck or indecisive, when seeking contextual advice rather than generic recommendations
Discover DevOps skills, compare source repositories and read the instructions for each workflow.
Use when facing a significant decision (career pivot, product direction, technical choice) and feeling stuck or indecisive, when seeking contextual advice rather than generic recommendations
Use when AI agents frequently hit dead ends, when reliability is the main constraint on scaling utility, or when general model improvements don't solve specific blockers
Leadership is a dynamic range. When confidence in team direction is low, temporary tactical micromanagement is the correct move—not autonomy. Teach the framework, then pull back.
Use when designing AI agent products, defining roadmaps for agentic workflows, or evaluating how to evolve AI from passive tool to proactive partner in software development
A JTBD interviewing technique to reconstruct the customer's timeline and uncover causal mechanisms behind a purchase. Resembles criminal investigation—penetrate surface-level answers to find the struggling mome...
A three-part structural framework for building a scalable company—Foundation (Founding Documents), Posts & Beams (Supporting Structures), and Mechanicals (Operating Cadence). Use when moving from PMF to scaling...
A quality control mechanism with a designated interviewer from outside the hiring chain who has veto power to ensure candidates raise the bar (better than 50% of current employees in role). Amazon's talent dens...
Use after drafting positioning statements, before writing website copy, or when marketing language sounds corporate rather than human
Use when building AI-powered products or agents, when raw model intelligence isn't enough to solve user problems, or when designing the architecture for agentic workflows
Fear creates exaggerated negative predictions. When gripped by fear, bet that the opposite will happen if you act against it, then take action. Use for high-stakes decisions that feel emotionally dangerous.
Use when running experiments on platforms where user value compounds over time, when growth teams claim credit for revenue that would have happened anyway, or when short-term wins don't translate to long-term v...
A leadership cadence where the CEO/Leader reviews actual work (designs, prototypes, copy) weekly rather than just metrics or status slides. Use when feeling product quality is slipping or team is moving too slo...
A goal-setting mental model where leaders increase the target by 10x to force teams to abandon current processes and use first-principles thinking. Use during annual planning when teams default to safe, increme...
Use in power-law businesses like platforms or VC, when conversion rate optimization shrinks your funnel, or when efficiency metrics block potential outlier winners
Review your calendar, color-code activities by energy impact (Green/Red), and systematically delegate draining tasks to maximize time in your Zone of Genius.
A roadmap for marketplace domination. Level 1: Focus on a "thimble" to maximize Happy GMV. Level 2: Tip the market via growth loops. Level 3: Dominate to capture economic rents. Not all GMV is equal.
Use when designing futuristic agentic workflows, when wanting AI to proactively act on team communications, or when eliminating the bottleneck of formal specifications
Focus on Input Metrics (selection, price, speed) rather than Output Metrics (revenue, stock price). Inputs are controllable and causal; outputs are lagging. Amazon's flywheel philosophy.
Use when dealing with ecosystems, network effects, or high-uncertainty environments where the right answer cannot be known in advance, when rigid planning consumes more value than it creates
Diagnose team problems by checking structural issues (goals/roles) at the surface before diving deep into personality conflicts. 80% of team problems are structural, not personal.
Project-specific patterns, conventions, and learnings for docker-containers. Triggers: "project patterns", "how does this project", "project conventions", "local setup", "build order", "test setup", "project-sp...
This skill should be used when the user asks to "collaborate with Codex", "use Codex for planning", "get Codex review", "delegate to Codex", "Codexと協調", "Codexにレビューを依頼", "Codexに計画を作成させたい",...
Create an opence plan and scaffold change artifacts.
Archive a completed change and apply spec updates to the main specifications.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.