Loading...
Loading...
Found 166 Skills
Run Claude Code CLI for complex tasks, code generation, analysis, and research. Uses Anthropic OAuth (included in Claude Pro). Use for extended thinking, code review, architecture decisions. Preferred for load balancing sub-agent work (35% weight).
Novel chapter content creation, suitable for user requests such as "Write a chapter of a novel for me", "Continue the following content", "Generate XX plot", "Batch write web novel chapters", "Expand/rewrite this content", "Write me an XX plot", "Continue the novel", "Expand this content", "Rewrite this chapter", "Batch generate novel chapters", "Write an opening chapter", "Write a climax plot", "Novel content generation", "Help me write novel content", etc. It supports multiple modes such as single-chapter/multi-chapter batch generation, continuation, rewriting, and expansion. It automatically adapts to the rhythm of web novels, maintains consistency of characters and plot, and **automatically uses sub-Agents for parallel processing during batch generation, with each Agent responsible for a maximum of 3 chapters**
Scaffolds new sub-agent definitions. Automates the entire process from category selection, file creation, model/tools least privilege configuration, to quality checks. Can be used with commands like "Make an Agent", "Add sub-agent", "create-agent".
Spawn a Team Leader agent that manages multiple sub-agents working toward a common goal. Team Leader reads requirements, decomposes work, assigns personalities and tasks, manages communication between team members, tracks progress, and reports results following ogt-docs task workflow. Integrates fully with docs-first system via task signals and status tracking.
Test, validate, and improve agent instructions (CLAUDE.md, system prompts) using sub-agents as experiment subjects. Measures instruction compliance, context decay, and constraint strength. Use for "test prompt", "validate instructions", "prompt effectiveness", "instruction decay", or when designing robust agent behaviors.
Parallel DAG-plan implementation skill. Reads a v-planning plan directory (root.md + step-<n>.md files), topologically schedules ready steps, and fans them out as parallel sub-agents. Use whenever the user invokes /v-implement, points at a plan directory produced by /v-plan, or asks to "run the parallel plan", "implement the DAG", or "fan out the steps" — even without those exact words. For linear plans (single .md file), use `implementing` instead.
Provides guidance on choosing between Agent Teams and Sub-agents and executing complex plans with parallel coordination. Use when implementing complex features requiring multiple specialized teammates working in parallel.
Generate a unit testing framework for Qt projects. Includes complete dependencies, sub-Agents, and fixed scripts to generate the autotests testing framework with one click.
PUA Shot — v2 Original Concentrated Version (449 lines full injection), the complete single-file version before splitting, with the strongest flavor. Zero dependencies and zero references, injects all content into the context at once. Suitable for sub-agent injection, scenarios requiring the strongest PUA effect, or those who don't want progressive loading. Triggers on: '/pua:shot', '/pua shot', 'PUA Concentrate', 'Shot Mode', 'Max PUA', 'Full Injection'. Also great for injecting into sub-agents via Read tool since it's self-contained.
Adaptive PLAN.md executor that preserves cook-quality implementation while choosing between direct main-agent work and sub-agent delegation. Runs a phase directly through cook when delegation has no material parallelism, context, or capability benefit; otherwise dispatches disjoint assignments through encode-agent prompts, discloses agent type, model, effort, scope, and rationale before each dispatch, and acceptance-reviews every returned diff. Expects prep to have created PLAN.md + HANDOFF.md and composes with cook, encode-agent, encode-docs, and handoff. Triggers: "/cater".
Comprehensive code review with parallel specialist sub-agents. Analyzes requirements traceability, code quality, security, performance, accessibility, test coverage, and technical debt. Produces detailed findings and calls /qa-gate for final gate decision.
Provides information about how to create, structure, install, and audit Agent Skills, Plugins, Antigravity Workflows, and Sub-agents. Trigger this when specifications, rules, or best practices for the ecosystem are required.