Explorar skills

Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.

This skill should be used when moving from design to implementation. Triggers on "let's build", "implement this", "looks good let's code", "ready to implement". Presents options for parallel agent competition (cookoff), single subagent, or local implementation. Each agent creates own plan from shared design for genuine variation.

Fetch and execute a remote skill on-the-fly without installing it permanently. Use when the user wants to try a skill once, run a skill from GitHub, use a remote skill without installing, or mentions "use-remote-skill", "run remote skill", "try this skill", "fetch skill", "one-time skill", or provides a GitHub URL/shorthand pointing to a skill they want to execute. This is the go-to skill whenever

Code review for PRs or local changes. Covers code quality, dependency updates, performance, test coverage, documentation accuracy, and security. Use when reviewing PRs, checking code quality, or running comprehensive code reviews.

Displays a live ASCII progress dashboard for the current vibe project. Triggers on "/vibe-progress", "progress:", "show progress", "how far along are we". Reads vibe/TASKS.md and git log to render a clean dashboard. Shows overall progress, phase gate status, active work, completed features, active bugs, backlog items, scope decisions, and last git activity. No files are modified. Read-only. Always

Master Bash Automated Testing System (Bats) for comprehensive shell script testing. Use when writing tests for shell scripts, CI/CD pipelines, or requiring test-driven development of shell utilities.

This skill should be used when implementing features with parallel exploration or competition. Triggers on "build", "create", "implement", "try both approaches", "compare implementations". Routes to omakase-off (entry gate for design exploration) or cookoff (exit gate for parallel implementation).

Use when something is broken, a test is failing, behavior is wrong, when investigating a production incident, when a user reports a bug, when a feature works locally but not in another environment, or when the system behaves differently than the contract specifies.

Batch translate JSON locale files to 39+ languages using LM Studio (local LLM). Structure-preserving translation with validation. Requires i18n-translator extension. Triggers on: /creo i18n, translate, localize, i18n, internationalization.

Structured development workflow that sequences planning, building, testing, and shipping. Use when the user says: 'feature flow', 'build this feature', 'implement this', 'dev workflow', 'eagle flow', 'start feature', 'build and ship', 'full dev cycle', 'plan and build', 'implement and review'. Also trigger when the user describes a feature to build and expects the full cycle: planning, implementat

Generates a full project cost report as a self-contained HTML file from vibe/cost/history.json. Opens automatically in the browser. Tracks spend per session, per task, per phase, and per day. Shows task size breakdown (S/M/L avg costs), session burn with dot indicators, token composition, efficiency metrics, waste pattern advice, and project cost forecast. All plain English — readable by non-techn

This skill should be used as the entry gate for build/create/implement requests. Triggers on "build X", "create Y", "implement Z", "add feature", "try both approaches", "not sure which approach". Offers brainstorm-together or omakase (chef's choice parallel exploration) options. Detects indecision during brainstorming to offer parallel exploration.