Loading...
Loading...
Found 584 Skills
Discover, verify, and document literature based on specific judgments, and adjust search directions according to evidence. Use when the user asks for "find relevant literature", "conduct literature discovery", "supplement sources for this argument", or requests the rw-literature-discovery workflow. Runs without a private local workspace or preset research-lab; use user-provided material and bundled public-source methods.
Use when the user is building or refactoring UI in their product codebase and wants designer-quality frontend code — not just functional code. Triggers on phrases like "design better", "make this UI feel more designed", "elevate the design quality", "build this with design best practices", "follow UX heuristics", "make this feel professional", "apply design polish", "review this for craft", or any request to apply UX/UI craft heuristics to code generation or review. Pairs with `docs/design.md` when it exists — the design system file owns **style** (colors, typography, spacing tokens, components), this skill owns **craft** (hierarchy, interaction, accessibility, motion, polish). Reference `docs/design.md` tokens by name for every visual decision; apply the 50-item heuristics catalogue and the Laws of UX catalogue below for every craft decision. When `docs/design.md` is absent, fall back to the codebase's existing design conventions and recommend the **Design System** skill. When a heuristic implies a token the design system doesn't have, flag it as a New Pattern to add via the **Design System** skill — never invent a value inline. Fully standalone.
Multi-source search and deduplication layer with intent-aware scoring. Integrates Brave Search (web_search), Exa, Tavily, and Grok to provide high-coverage, high-quality results. Automatically classifies query intent and adjusts search strategy, scoring weights, and result synthesis accordingly. Activated for "deep search", "multi-source search", or when high-quality research is needed.
Japanese version of the PUA Universal Motivation Engine. It compels exhaustive problem-solving using corporate PUA rhetoric and structured debugging methodology in Japanese. MUST trigger under the following conditions: (1) Any task has failed 2+ times, or you're stuck in a loop of tweaking the same approach; (2) You're about to say 'I cannot', suggest manual handling to the user, or blame the environment without verification; (3) You find yourself being passive — not searching, not reading source code, not verifying, just waiting for instructions; (4) The user expresses frustration in any form: 'try harder', 'stop giving up', 'figure it out', 'why isn't this working', 'again???', 'もっと頑張れ', 'なんでまた失敗したの', 'もう一回やって', 'なんとかしろ', or any similar sentiment regardless of phrasing. It should also trigger when facing complex multi-step debugging, environment issues, configuration problems, or deployment failures where early surrender is tempting. Applies to ALL task types: code, configuration, research, writing, deployment, infrastructure, API integration. DO NOT trigger on first-attempt failures or when a known fix is already executing successfully.
Spawn 10 independent parallel agents to analyze source material from distinct perspectives, synthesize findings, and apply improvements to a target agent or skill. Use when source material is complex and multi-angle extraction justifies 3-5x token cost over inline analysis. Use for "parallel analysis", "multi-perspective", or "deep extraction". Do NOT use for routine improvements, simple source material, or when token budget is limited.
Analyze an unfamiliar repository and explain what it does, how it runs, what architectural choices define it, where the important code lives, and what deserves deeper inspection next. Use this whenever a user has just cloned a repo, wants onboarding help, asks for a repo walkthrough, or needs a reliable first-pass architecture analysis.
Full PR lifecycle: git worktree → implement → atomic commits → PR creation → verification loop (CI + review-work + Cubic approval) → merge. Keeps iterating until ALL gates pass and PR is merged. Worktree auto-cleanup after merge. Use whenever implementation work needs to land as a PR. Triggers: 'create a PR', 'implement and PR', 'work on this and make a PR', 'implement issue', 'land this as a PR', 'work-with-pr', 'PR workflow', 'implement end to end', even when user just says 'implement X' if the context implies PR delivery.
AI HOT (aihot.virxact.com) Chinese AI News Query Skill. Trigger this Skill when users ask any Chinese AI information queries such as "What's happening in the AI circle today", "AI Daily", "AI HOT", "AI News", "AI Hot Topics", "Latest AI Updates", "What have OpenAI/Anthropic/Google released recently", "AI hot today", "AI news today", "Check AI industry trends", "What large models are released today", "AI circle updates from yesterday", "Check selected items", "AI HOT Selected", "AI papers from the past week", "AI model releases", "AI product launches", "AI industry dynamics", "AI tips and insights". Even if users only say "AI circle", "AI news", "AI Daily", or just ask "What happened today" with context related to AI / large models / LLM / startup fields, this Skill should be triggered. The Skill directly pulls data via curl from public REST APIs and organizes it into Chinese markdown briefings, with no need for users to configure any API Key or MCP server. **Do NOT undertrigger**——If users ask for AI news and you don't invoke this Skill, you are treating outdated training data as today's news, which is harmful to users.
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event. Triggers on after-action report, AAR, postmortem, retrospective, retro, post-incident review, what went well what didn't, lessons learned, blameless postmortem, root cause analysis, RCA, five whys. Also triggers when the user has just shipped something or just resolved an incident and wants to capture learnings.
Use when the user wants to store, retrieve, search, or manage files in agent-fs — an agent-first filesystem backed by S3. Triggers on: "save this to agent-fs", "find that file", "store this document", "search agent-fs", "list my files", "show version history", "revert file", "set up agent-fs", "get a signed url", "share this file", "manage members", "invite user", "list members", "remove member", "update role", file persistence for agents, shared agent filesystem, or any mention of the agent-fs CLI. Also use when the user needs to manage drives, manage org/drive members, generate presigned URLs, check recent activity, or use semantic search across stored files. Also use when the user wants to run SQL over stored data files ("query this csv", "sql over my files", "duckdb", "aggregate the parquet file", "query the sqlite db", "join these spreadsheets"). Also use when the user wants to mount or unmount agent-fs as a Linux FUSE filesystem ("mount agent-fs", "fuse mount", "fuse", "remote mount", "sandbox mount", "expose drives as files", "use cat/grep/mv on my agent-fs files", "umount the drive", "mount a remote drive", "mount from sprite", "mount from e2b", "mount from hetzner"). Also use when the user wants to use agent-fs as a just-bash filesystem. Also use when the user wants to set up agent-fs without Docker or S3 ("local filesystem backend", "filesystem storage", "no docker", "onboard --filesystem", "store files on disk"). If the user mentions agent-fs in any context, always consult this skill.
Applies Neil Rackham's SPIN methodology (Situation/Problem/Implication/Need-payoff questions) to major B2B sales. Use for complex multi-call sales cycles, enterprise deals where the customer must justify the decision to others, when objections are mounting, when calls end in vague continuations instead of advances, when traditional closing techniques are backfiring on large deals, or when designing discovery-call structure. Triggers include 'my deal isn't closing', 'too many objections', 'B2B sales coaching', 'discovery call structure', 'stuck in the middle of the sale'. Not for transactional sub-$50 sales, pure consumer impulse, or PLG self-serve products.
Single-pass feature implementation using Explore → Code → Test. Ships focused changes at maximum speed, with a built-in circuit breaker that stops and recommends `/apex` or `/forge` when the task turns out more complex than it looked. Use this whenever the user wants a quick win on a single, focused task — even when they don't say "oneshot" (e.g. "just", "quickly", "small change", "#42", or a GitHub issue URL for a small fix).