GitHub
ai-teammate-model
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
☆ 2View skill
Testing & security AI Skills
Discover Testing & security skills, compare source repositories and read the instructions for each workflow.
Categories: Testing & security
Testing & security Clear filters
Browse skills
GitHub
causal-interview-protocol
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...
☆ 2View skill
GitHub
house-operational-architecture
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...
☆ 2View skill
GitHub
bar-raiser-hiring-mechanism
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...
☆ 2View skill
GitHub
bar-test-positioning
Use after drafting positioning statements, before writing website copy, or when marketing language sounds corporate rather than human
☆ 2View skill
GitHub
three-layer-agent-stack
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
☆ 2View skill
GitHub
fear-and-anger-decision-filter
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.
☆ 2View skill
GitHub
long-horizon-holdout
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...
☆ 2View skill
GitHub
in-the-details-review-loop
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...
☆ 2View skill
GitHub
add-a-zero-heuristic
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...
☆ 2View skill
GitHub
absolute-volume-framework
Use in power-law businesses like platforms or VC, when conversion rate optimization shrinks your funnel, or when efficiency metrics block potential outlier winners
☆ 2View skill
GitHub
energy-audit-and-zone-of-genius
Review your calendar, color-code activities by energy impact (Green/Red), and systematically delegate draining tasks to maximize time in your Zone of Genius.
☆ 2View skill
GitHub
hierarchy-of-marketplaces
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.
☆ 2View skill
GitHub
chatter-driven-development
Use when designing futuristic agentic workflows, when wanting AI to proactively act on team communications, or when eliminating the bottleneck of formal specifications
☆ 2View skill
GitHub
controllable-inputs-framework
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.
☆ 2View skill
GitHub
gardening-mindset
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
☆ 2View skill
GitHub
waterline-model
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.
☆ 2View skill
GitHub
project-experience
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...
☆ 2View skill
GitHub
codex-collaboration
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に計画を作成させたい",...
☆ 2View skill
GitHub
opence-plan
Create an opence plan and scaffold change artifacts.
☆ 2View skill
GitHub
opence-archive
Archive a completed change and apply spec updates to the main specifications.
☆ 2View skill
GitHub
opence-work
Implement an opence change and keep tasks in sync.
☆ 2View skill
GitHub
opence-compound
Document learnings, capture repeatable workflows as skills, and prepare to compound an opence change.
☆ 2View skill
GitHub
native-skill-addition
Guide for adding new opence native skills to the workflow
☆ 2View skill
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.