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...
Discover Tools skills, compare source repositories and read the instructions for each workflow.
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.
Implement an opence change and keep tasks in sync.
Document learnings, capture repeatable workflows as skills, and prepare to compound an opence change.
Guide for adding new opence native skills to the workflow
Coordinate prompt and skill updates across related changes
Review an opence change with prioritized findings.
Learn how to create effective project skills following opence conventions.
Analyzes Makefiles to understand their targets and executes the appropriate make command based on user intent. Specializes in parsing self-documenting Makefiles that use the `##` comment convention.
Guides the creation of high-quality Pull Requests that adhere to repository standards, covering template discovery, drafting descriptions, and executing PR creation commands.
根據 Git Repository 的風格建立 Commit。當使用者要求,或 Agent 需要建立 Commit 時,必須使用此技能。
Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.
Use during verification phase when conducting thorough code reviews and providing constructive feedback based on universal software quality principles.
MUST use when interacting with Shortcut's project management platform to create, update, search, or retrieve stories, epics, iterations, teams, workflows, objectives, and documents.
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.