Set up, configure, and use Mushi Mushi — the AI-powered QA platform for automatic bug detection, user story mapping, TDD scenario generation, and PDCA auto-improvement. Use when setting up Mushi, configuring SDK/CLI/MCP, managing API keys, or asking how any Mushi feature works.
Given a benchmark repository URL (agentic envs like arc-agi, memory/eval benchmarks like longmemeval, QA/code/tool-use benchmarks, etc.), orchestrate the creation of a full Claude Code plugin that benchmarks the current harness setup against it. Wraps the babysitter:babysit skill with the benchmark-plugin-creator…
Operate only in authorized scope: bug bounty targets explicitly in scope, owned systems, defensive reviews, or labs. Decline or pause on requests involving unauthorized access, stealth, persistence, service disruption, credential abuse, real data theft, or abuse of third-party systems.
Proves that agent work is actually done: each claim becomes a ledger row with a gate that was executed, captured raw evidence, and a status a builder is not allowed to write for itself. Use when a technical result must be auditable later — shipping or migrating something users depend on, a change whose failure is…
TDD-first spec management for AI coding workflows. Use this skill when the user explicitly mentions specs, forging, or structured planning: says "forge", "forge a spec", "write a spec for X", "create a spec", "plan X as a spec", "resume", "what was I working on", "spec list/status/pause/switch/activate", "implement…
A test-suite generation workflow for software projects. It includes static checks, unit tests, integration tests, end-to-end tests, coverage reports, type checking, linting, security scanning, and dead-code detection.
Test an Android app on a real phone or an emulator using adb. Use when the user wants to install an APK they just compiled, walk through the app's screens, check the on-screen text, reproduce a bug, capture screenshots, read crash logs, or set up an Android testing environment from scratch. Covers both a physical…
Run the pytest suite, report pass/fail counts and coverage, and identify untested code. Use when the user asks to run tests, check test coverage, or verify that changes didn't break anything.
Testing strategies including unit tests, integration tests, E2E tests, mocking, coverage analysis, and TDD workflow. Trigger when users need help writing tests, choosing testing frameworks, implementing mocking strategies, or setting up test infrastructure.
Use when a branch, worktree, local app, or cloud-agent task needs a staged test environment without disturbing the main checkout, especially for browser-facing web app work. Helps agents choose and set up the right strategy for browser/app testing across JavaScript/TypeScript, Python, PHP, Docker Compose, local…
CLI for driving an Android emulator (AVD) over adb. Use when the user needs to connect to an emulator (attach to a running one or boot/manage an AVD), tap/swipe/type on the UI, read the UI/accessibility tree, take screenshots or screen recordings, capture logcat, capture HTTP(S) requests in-process (Frida OkHttp hook…
A test-first review process for new research ideas, trading strategies, paper topics, models, architectures, or data pipelines. TDD means defining tests or checks before building the idea.
Adversarial verification of code changes. Tries to break implementations rather than confirm they work. Produces structured PASS/FAIL/PARTIAL verdicts with evidence. Use when verifying code changes, after non-trivial implementations, before reporting task completion, or when asked to check if something works.
Review Odoo addon code for correctness, security, performance, migrations, tests, and official Odoo coding guidelines. Use when reviewing Odoo modules, diffs, pull requests, or changed files involving models, fields, XML views, data, controllers, reports, OWL/assets, manifests, access rules, record rules, or OCA…
Evidence-driven codebase hardening. Audits security (OWASP Top 10:2025), supply chain (inventory vs SBOM vs SLSA v1.2), reliability (OTel + operational limits), tests (sandboxed tiers), and accessibility (WCAG 2.2 AA). Every finding is quoted, matrix-scored, and cited. Does not fix. Reports with file:line and a…
Use when caller wants to observe how a stranger encounters a flow, artifact, or sandbox — triggers like "simulate a user journey", "test our onboarding / checkout / signup", "will my ICP convert", "how does a cold reader experience this README", "first-time user test", "cognitive walkthrough", or any request to…
Run and CDP-test a feature inside its own git worktree without colliding with other parallel coding sessions. Use whenever you are testing a feature locally in a worktree, running Playwright/CDP against your own app, or running two or more agent sessions in parallel that each need a dev server and a browser. Trigger…
Write solid unit tests using property-based testing and mutation testing. Use whenever unit tests are being written, fixed, audited, or reviewed in a TypeScript project; whether the user asks directly or test-writing occurs as a step inside another workflow (TDD, feature implementation, bug fixing, code review). Also…
Audit a repository's automated testing health and recommend a bounded, high-value next improvement slice. Use when assessing an existing test suite, introducing tests into an untested or legacy project, deciding what to test next, evaluating testing strategy or coverage, choosing between unit, integration, and…
Design evaluation contracts and test plans for agentic systems. Create deterministic tests, trajectory evals, quality dimensions, gold-set criteria, and CI gates before or after implementation. Use when asked for tests first, an eval plan, success criteria, non-deterministic testing, LLM-as-judge setup, or…
Use when writing an implementation plan in a project — wraps superpowers:writing-plans with a fresh-subagent test-rigor review loop (≤3 rounds) after the plan is written. Each round asks "what realistic failure mode would survive these tests?" and either extends the plan or marks gaps out-of-scope in a Deferred Risks…
End-to-end test a Claude Code plugin by launching an interactive Claude session in a tmux pane with the plugin loaded, sending prompts, and verifying behavior.
★not rated 3 1mo agoA34 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: