Loading...
Loading...
Found 3,049 Skills
Update Codex's pinned `v8` / `rusty_v8` versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update `rusty_v8` artifacts, prepare or validate a V8 release candidate, check `v8-canary`, or diagnose why a V8 version update no longer builds.
Opinionated guide for building production TypeScript applications with Effect v4. Use when implementing Effect workflows, services, layers, schemas, configuration, schedules, caches, streams, HTTP clients, or tests.
Check the evidence, biases, alternative explanations, and reporting boundaries required for research conclusions before implementation or submission. Use when the user asks for “review my research design”, “act as a strict reviewer”, “challenge this conclusion”, or requests the rw-research-referee workflow. Runs without a private local workspace or preset research-lab; use user-provided material and bundled public-source methods.
Use when configuring any n8n node: HTTP, webhooks, database, comms (Slack/Gmail/Discord), AI, triggers, Merge, anything. Triggers on any node-builder call (`node(...)`, `trigger(...)`, `tool(...)`, `memory(...)`, `languageModel(...)`, `ifElse(...)`, `merge(...)`, etc.), configuring a parameter, `useDataOfInput`, `numberOfInputs`, fan-in convergence, or any node-specific debugging.
Apply fixes from an /age report, finding list, or CI failure, then run the project's test/lint/build gates and hand a clean cure to /plate for commit/publication. Use when the user wants selected findings resolved. Do NOT use for review (route to /age), test authoring (route to /press), or direct publication (route to /plate).
Use when generating agent-native onboarding docs, coverage maps, health baselines, and agent adapters for a repo.
Facilitates the first step of a proven customer-interview method: deciding exactly what you're trying to learn, written as numbered goal questions (G1, G2, …) that your hypotheses and interview questions will later be designed to answer. Interviews the user about their business — new idea or established company, B2B or B2C — then drafts a tailored goal-question list, critiques and revises it with them, and preserves the result in a GOALS.md file. Load when the user wants to interview customers, plan customer discovery or customer development, validate a startup idea, or answer unaskable questions like what to charge, how to position, who the ideal customer is, or what to build. Do NOT load for job or hiring interviews, for writing survey questionnaires, for analyzing customer interviews that have already been conducted, or when a goal-question list already exists and the user wants the next step (hypotheses).
Bring existing tracker issues up to standard without implementing anything — applies missing SDLC labels, clarifies laconic issues (analyzing attached screenshots), posts a read-only implementation-prep analysis, and flags feature issues lacking a covering spec (optionally authoring one with --write-missing-specs). Single issue by id, or a batch (default — last ~25 open, worst-described first). Idempotent and claim-aware. Use for "triage the backlog", "clean up issue 123".
Rigorously evaluate an Agent Skill end-to-end across ANY coding-agent CLI — verify its scripts emit the documented numbers (deterministic checks), test whether its description triggers on the right prompts, and measure whether an agent following the SKILL.md beats a no-skill baseline (with/without pass-rate delta, mean ± stddev, benchmarked). Use whenever you need to test, benchmark, validate, grade, or quantify a skill's quality, check if a skill "actually works," compare two skill versions, optimize a skill's triggering, or set up an eval suite — even if the user just says "is this skill any good," "does my skill work," or "benchmark this skill." Drives Claude Code, OpenAI Codex, Antigravity (agy), Cursor, GitHub Copilot, Amp, opencode, or Grok in headless mode.
Use when the user wants to validate a product idea, find pain points, mine demand signals, discover objections, or gather voice-of-customer language from Reddit, social posts, video transcripts, and comments. Produces evidence-backed product research.
Use when symfony bootstrap check
Generate lightweight section/subsection transitions (NO NEW FACTS) to prevent “island” subsections; outputs a transition map that merging/writing can weave in. **Trigger**: transition weaver, weave transitions, coherence, 过渡句, 承接句, 章节连贯性. **Use when**: `outline/subsection_briefs.jsonl` exists and you want coherent flow before/after drafting (typically Stage C5). **Skip if**: `outline/transitions.md` exists and is refined (no placeholders). **Network**: none. **Guardrail**: do not add new factual claims or citations; transitions may only refer to titles/RQs/bridge terms already present in briefs.