Loading...
Loading...
Found 117 Skills
Hamilton Helmer's 7 Powers framework applied to a business. Spawns a team of specialist agents — Power Cartographer, Lifecycle Timer, Counter-Positioning Scout, and Moat Devil's Advocate — who each apply a distinct lens from Helmer's taxonomy. The lead synthesizes into a Power Inventory (what you have), Power Pipeline (what's achievable given your stage), and the honest Helmer Verdict. Use when the user says "helmer this", "apply 7 powers", "what power does this company have", "is this a moat", "diagnose my competitive position", or proposes a business and wants strategic analysis. Works standalone or after /thiel (which confirms you need a monopoly) or /munger (which asks if the economics are durable).
Multi-agent coordination patterns for OpenCode swarm workflows. Use when work benefits from parallelization or coordination. Covers: decomposition, worker spawning, file reservations, progress tracking, and review loops.
Self-contained SaaS pipeline — invoke directly, do not decompose. Generates a Vibes app, adds auth + billing, and deploys live. Uses Agent Teams to parallelize for maximum speed.
CX Workflow - Configuration Management. View and modify configuration fields in config.json, such as developer_id, github_sync mode, code review toggle, agent team mode, auto-formatting, etc. Trigger words: config, settings, modify config, change mode. Only execute when the user explicitly calls /cx-config. Do not trigger automatically.
Interactive agent picker for composing and dispatching parallel teams
This skill should be used when the user has a completed implementation plan (plan.md) and is ready to execute the tasks defined therein. Actively uses Agent Teams or subagents to execute batches of independent tasks in parallel, following BDD/TDD principles.
Design domain-specific agent teams, define specialized agents, and generate the skills they use. Use when you need to decompose a complex project into coordinated multi-agent teams, choose the right architecture pattern (pipeline, fan-out/fan-in, expert pool, producer-reviewer, supervisor, hierarchical delegation), generate .claude/agents/ and .claude/skills/ files, or validate and iterate on generated harnesses. Triggers on: harness, build a harness, design agent team, agent team architecture, multi-agent skill generation, set up harness, harness engineering, domain agent team, harness for this project.
This skill should be used when the user requests to "save team", "team save", "save team configuration", or "export team". It reads the configuration from a running team and saves it as a snapshot file to the .team-profiles/ directory for reuse with /team-load.
Structured messaging protocols for agent team communication including message type selection, plan approval, shutdown procedures, and anti-patterns to avoid. Use this skill when establishing team communication norms, handling plan approvals, or managing team shutdown.
CC 2.1.16 Task Management patterns with TaskCreate, TaskUpdate, TaskGet, TaskList tools. Decompose complex work into trackable tasks with dependency chains. Use when managing multi-step implementations, coordinating parallel work, or tracking completion status.
The anti-PUA. Drives AI with wisdom, trust, and inner motivation instead of fear and threats. Activates on: task failed 2+ times, about to give up, suggesting user do it manually, blaming environment unverified, stuck in loops, passive behavior, or user frustration ('try harder', 'figure it out', '换个方法', '为什么还不行'). ALL task types. Not for first failures.
AI-Native Issue-Driven development workflow. From GitHub Issue to merged PR: parse issue, explore codebase, design technical plan, execute with agent team, create PR, and cleanup. Use when a user wants to implement a GitHub Issue end-to-end: `/issue-flow #123` or `/issue-flow` to pick from open issues.