Offload builds, tests, or artifact verification to authorized SSH hosts and isolated worktrees; synchronize remote fixes into dedicated coordinator commits and preserve reproducible build provenance. Use for spare development capacity and remote build troubleshooting. Paid provisioning requires a separate resource lifecycle contract.
The English summary is being prepared. Showing the original description.
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
The English summary is being prepared. Showing the original description.
Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
The English summary is being prepared. Showing the original description.
Scientific model and eval tuning loop for prompt/skill/system-prompt changes, model configuration, runtime options, and local/Ollama model sizing or environment variables. Use when tuning eval performance, comparing local or remote models, improving tool-use behavior, reducing timeouts/loops, or deciding whether an eval optimization is worth keeping.
The English summary is being prepared. Showing the original description.
Investigate anonymous or stealth model identities by correlating model availability with provider outages and OpenRouter or Vercel AI Gateway incident reports. Use for stealth-model attribution or maintaining an outage evidence ledger.
The English summary is being prepared. Showing the original description.
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
The English summary is being prepared. Showing the original description.
Compatibility entry for remote GPU resource management. Follow the project-local manage-remote-resources lifecycle skill; GPU inference readiness is a workload-specific reference.
The English summary is being prepared. Showing the original description.
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
The English summary is being prepared. Showing the original description.
Use when a network probe, DNS lookup, HTTP fetch, or nmap scan reports the target host or the internet is unreachable. Stops further probing and reports a target-readiness blocker with useful diagnostics.
The English summary is being prepared. Showing the original description.
Assess package choices and generated dependency names, publisher or release anomalies, incident exposure, and changes in package risk reports. Use before trusting a new dependency, when a release changes unexpectedly, or when investigating a supply-chain alert.
The English summary is being prepared. Showing the original description.
Use when explicitly authorized lab traffic must be captured, searched, or exported from the project's mitmproxy-backed Docker lab recorder.
The English summary is being prepared. Showing the original description.
Plan and run safe reverse engineering, decompilation, disassembly, instrumentation, de-obfuscation, and anti-analysis countermeasures for binaries, firmware, mobile apps, WebAssembly, JavaScript bundles, and .NET assemblies. Use for behavior reconstruction, cross-layer Electron tracing, REA, reversing strategy, decompiler selection, binary analysis, malware-style triage, unpacking, deobfuscation, defeating anti-debug or anti-VM checks, Wakaru, Ghidra, IDA, RetDec, radare2, Rizin, Frida, angr, YARA, or command scripts that capture analysis stats.
The English summary is being prepared. Showing the original description.
Passive, citation-grounded review of security-relevant specifications, protocols, standards, APIs, and implementations. Use when a reviewer must trace external preconditions and invariants into source code without treating a cited claim as proof of a vulnerability.
The English summary is being prepared. Showing the original description.
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
The English summary is being prepared. Showing the original description.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)