Explorar skills

Use when writing tests, structuring test suites, choosing test boundaries, or debugging test quality issues like flakiness, over-mocking, or brittle tests. Also use when deciding between unit/integration/E2E tests, when tests break during refactoring (sign of testing implementation details), or when test setup exceeds 20 lines. Covers AAA structure, DAMP naming, mock boundaries, and the testing py

Use when implementing any feature or bugfix, before writing implementation code. Also use when touching test files (*.test.*, *.spec.*, *_test.go), when plan tasks have tdd="true", or when the user says "test first", "write tests", "TDD", or "red green refactor". If you're about to write production code without a failing test, this skill applies.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies. Also use when multiple test files fail with different root causes, multiple subsystems are broken independently, or you want agents to work concurrently on separate problem domains. If tasks touch different files and don't share state, this skill applies.

A/B testing strategy and implementation for funnel pages. Defines what to test, how to structure variants, statistical significance thresholds, and common testing patterns.

Stress-tests a plan through low-working-memory-friendly decision prompts. Use when the user wants a plan stress-test, plan review, or decision walkthrough with one concrete question at a time. Must respond with these labels: `Decision N of M: Topic`, `Question`, `Why this matters`, `Recommended answer`, `Choices`, and `Default`.

Voice — text-to-speech and transcription. Triggers on /agent:voice, /agent:voice status, /agent:voice setup, /agent:voice test, "configurar voz", "prueba voz", "voice setup", "speak this", "read this aloud", "transcribe audio".

Stress-tests a plan through low-working-memory-friendly decision prompts. Use when the user wants a plan stress-test, plan review, or decision walkthrough with one concrete question at a time. Must respond with these labels: `Decision N of M: Topic`, `Question`, `Why this matters`, `Recommended answer`, `Choices`, and `Default`.

Minimal skill for testing context fork behavior. Do not use in production.

Run deterministic OpenSkills end-to-end validation across runtime tests and example agents, then report tool calls, activation behavior, and regressions.

Exploit-DB and searchsploit reference — EDB→Metasploit module mappings, PoC reliability rubric, CVSS tier quick reference, and searchsploit usage patterns

CVSS 3.1 vector examples, executive summary template, full technical finding template, and remediation language bank for pentest reports

Removes files installed by /optimus:init and /optimus:permissions from the project. Compares each file against plugin templates and classifies as unmodified, likely generated, or user-modified. Always asks before deleting. Git-tracked files are noted as recoverable. Tests are never touched. Monorepo and multi-repo aware. Use for clean reinstall or to stop using optimus.