This skill should be used only when the user explicitly asks to use `$ralph-specum-refactor`, or explicitly asks Ralph Specum in Codex to revise spec artifacts after implementation learnings.

This skill should be used only when the user explicitly asks to use `$ralph-specum-requirements`, or explicitly asks Ralph Specum in Codex to run the requirements phase.

This skill should be used only when the user explicitly asks to use `$ralph-specum-research`, or explicitly asks Ralph Specum in Codex to run the research phase.

This skill should be used only when the user explicitly asks to use `$ralph-specum-tasks`, or explicitly asks Ralph Specum in Codex to run the tasks phase.

This skill should be used only when the user explicitly asks to use `$ralph-specum-triage`, or explicitly asks Ralph Specum in Codex to triage a large effort into multiple specs.

React 19 patterns with React Compiler. Trigger: When writing React 19 components/hooks in .tsx (React Compiler rules, hook patterns, refs as props). If using Next.js App Router/Server Actions, also use nextjs-16.

Write modern React components with TypeScript, hooks, and best practices. Creates functional components, custom hooks, and follows composition patterns.

Architectural guidance for building node-based UIs with React Flow. Use when designing flow-based applications, making decisions about state management, integration patterns, or evaluating whether React Flow fits a use case.

React Native mobile patterns, platform-specific code

React best practices: hooks, composition, state management, performance optimization, Server Components, and testing patterns.

How to use the Readwise MCP tools — access highlights, documents, and your entire reading library via MCP

Clean up stale Readwise Reader documents. Use when the user wants to declutter their reading library, remove old unread articles, or manage Reader inbox. Triggers on "clean up readwise", "prune reader", "delete old articles", "declutter reading list".

Search Readwise highlights. Use when the user wants to find highlights, quotes, notes, or annotations from their reading library. Triggers on "search highlights", "find in readwise", "what did I highlight about", "my notes on".

Receive context from parent, child, or sibling session

Create frontend work plan from design document and obtain plan approval

Template for commands that implement a structured recipe: validate preconditions, then execute numbered steps. Fork this and replace the placeholder content. The 'Context Validation Checkpoints' section is the key pattern, forcing Claude to verify preconditions before starting.

Analyze code or requirements and recommend the best es-toolkit functions. Use when the user asks which es-toolkit function to use, needs help finding a utility, or wants alternatives to manual implementations.

A pattern for generating higher-quality output by iterating against explicit scoring criteria. Use for headlines, CTAs, landing page copy, social content, ad copy — anything where quality matters. Generate → Evaluate → Diagnose → Improve → Repeat.

When the user wants to set up, optimize, or manage Reddit Ads. Also use when the user mentions "Reddit Ads," "Promoted Posts," "subreddit targeting," "Reddit advertising," or "Reddit communities." For organic Reddit, use reddit-posts.

Analyze code for SOLID violations and suggest targeted improvements

Refactor existing AGENTS.md to follow progressive disclosure principles

Use when analyzing and refactoring multiple skills across a project. Use when user says "refactor skills", "cleanup skills", "consolidate skills", "skill review". Use when skills overlap, are redundant, or need cross-skill consolidation. NOT for improving a single skill (use improving-skills instead).

Reference documentation for docker-local architecture, commands, and configuration

Analyze command history to identify which skills work, which fail, and where to improve.

Check PR merge readiness, sync local repo, cleanup stale worktrees; optional cross-repo sweep and stale-branch prune modes

# Release Claude Code Plugin

Security fix patterns for configuration and deployment vulnerabilities (path traversal, debug mode, security headers). Provides language-specific secure implementations.

Security fix patterns for cryptographic vulnerabilities (weak algorithms, insecure randomness, TLS issues). Provides language-specific secure implementations.

Security fix patterns for injection vulnerabilities (SQL, Command, XSS). Provides language-specific code examples showing vulnerable and secure implementations.

Memory operations for Muninn (recall, remember, supersede, config). The canonical implementation has moved to oaustegard/muninn-utilities/remembering/. This file is a pointer; do not load skills from this path.

Use when removing an obsolete documentation file (ad-hoc doc or module AGENTS.md/CLAUDE.md pair) — finds all references, presents a removal plan, deletes the file(s), and cleans up references from root and module AGENTS.md. Requires confirmation; --auto skips it.

Generate professional data reports with charts, tables, and visualizations

Use this skill when creating bug reproductions. Activate when the user needs to create a minimal reproduction case, report a bug with steps to reproduce, isolate a bug to specific conditions, or help others understand how to trigger an issue.

Use when "requirements document", "acceptance criteria", "user stories", "EARS format", "specification", "feature spec", "product requirements"

Internal skill. Synthesis guidance loaded via SKILL_HINTS by planner and bug-investigator when research files are available.

Research best practices, guides, and libraries. Use when needing documentation, recommendations, implementation guidance, or library comparisons.

Use when brainstorming completes and user selects research-first option - manages parallel research subagents (up to 4) across codebase, library docs, web, and GitHub sources, synthesizing findings and auto-saving to memory before planning

Develops intuition for what makes research "good" versus "incremental." Use when asked about research taste, how to identify good research, what makes a paper impactful, how to develop research intuition, or how to pick important problems. Analyzes patterns in highly-cited work and what top researchers do differently.

Analyze and fix CI check failures on a PR. Use when CI checks fail, build errors occur, or tests fail in CI. Invoked automatically by the SDLC workflow (Step 7.4) when checks fail, or manually via 'resolve CI failures', 'fix CI', 'fix failing checks'.

Plans resource allocation and agent assignments to tasks. Use when you need to allocate agents to tasks, balance workload, or plan resource usage. Considers task dependencies, agent capabilities, and workload distribution.

Design RESTful API endpoints with proper resource modeling, HTTP methods, and URL structure. Use when creating REST APIs, designing endpoints, or structuring API resources.

Use when "tailoring resume", "job application", "CV customization", "ATS optimization", or asking about "resume writing", "career transition", "job description matching"

Create targeted resume sections optimized for different experience levels and roles

Retrieve code diff from a local git commit. Use this as the first step in a code review pipeline when reviewing local commits.

Document an existing decision from code as an ADR or DES

Creates minimal, effective AGENTS.md files using progressive disclosure. Triggers on "create agents.md", "refactor agents.md", "review my agents.md", "claude.md", or questions about agent configuration files. Also triggers proactively when a project is missing AGENTS.md.

Synthesizes accumulated QA learnings from .qa-learnings/ledger.md into prioritized, actionable plugin improvements. Use when the user says "review learnings", "what have we learned", "improve the plugin", "learnings report", or "synthesize QA feedback".

Review implementation plans for completeness and feasibility. Use when user says "review this plan before I start", "is this implementation plan complete", "check if this plan aligns with our patterns", "give me feedback on my implementation strategy", or "validate this plan before we execute it".

Review service documentation completeness on Notion. Use when auditing service documentation, validating Notion database entries, or checking compliance with documentation standards.

Code review checkpoint using codex review CLI. Returns structured result with pass/fail status and issues. Use when: 'code review', 'review changes', 'codex review', 'check my code'.

This skill should be used when the user asks to "review Dependabot alerts", "check for vulnerable dependencies", "audit third-party packages", "assess supply chain risk", "run Grype scan", or needs to evaluate dependency health, transitive risk, or supply chain security.

Revolut Business API CLI — accounts, balances, transactions, counterparties, payments, FX exchange, CSV export. Auto-refreshes OAuth tokens. Business accounts only (not personal).

Rewrite Rust documentation comments to ensure all documentation and comments are in English, following rustdoc guidelines. Use when the user wants to clean up Rust documentation, translate Chinese comments to English, fix missing documentation, or ensure rustdoc compliance in a Rust codebase.

Adding database-per-tenant isolation into a Go service end-to-end via an 11-gate cycle: detects the stack, audits compliance, then dispatches backend agents to implement tenantId-from-JWT routing through the lib-commons v5 dispatch layer (config, middleware, repositories, metrics, tests) and runs reviewers. Use when adding tenant isolation to a Go service. Skip for non-Go services or organization_id-style soft tenancy.

Detailing the first phase's epics into dispatch-ready tasks written inline into tasks.md — Context with file:line refs, implementation vision, exact Files, Verification, Done-when — prose over code, no vague tasks, no deferrals. Gate 8 of ring:using-pm-team Full Track; runs after ring:decomposing-phases-and-epics. Use when a phased plan passed Gate 7 and Phase 1 must become executable. Skip on Small Track or for later phases.

Fixing lint to a clean state: runs the linter, groups reported issues into independent streams, and dispatches one parallel fixer agent per stream (ring:backend-go for Go, ring:general-purpose otherwise), iterating until clean. Use when a codebase has lint errors across multiple files. Skip for a single error (fix directly), already-passing lint, or view-only requests; security lints are reported, not auto-fixed.

Managing an in-progress development cycle without driving it: status reports phase, epic/gate progress, assertiveness, and elapsed time from current-cycle.json; cancel confirms, marks the cycle cancelled, and writes a partial feedback report. Use when checking the status of, or cancelling, a running dev cycle. Skip when no cycle is active or the question is general project status, not cycle-specific.

Pinning an explicit versioned dependency manifest (dependencies.md plus PROJECT_RULES.md): exact package versions, CVE and license checks, compatibility matrices, and per-component cost analysis against Ring Standards. Gate 6 of ring:planning-large-features, runs after ring:designing-data-model. Use when the data model is validated and you are about to lock products and versions. Skip for Small Track or when versions are already locked.

Planning a frontend refactor: audits an existing React/Next.js frontend against Ring standards (architecture, Sindarian UI, accessibility, testing) and produces a prioritized task list (findings.md + tasks.md) for ring:running-dev-cycle-frontend. Plans only — no edits. Use when an existing frontend needs to meet standards or an audit is requested. Skip for greenfield, single-file fixes, or backend (use ring:planning-backend-refactor).

Planning the 10-gate Full Track pre-dev workflow (research, PRD, feature map, design validation, TRD, API design, data model, dependency map, phases and epics, task creation, delivery planning) with per-gate human approval. Use for features 2+ days that add dependencies, data models, multi-service integration, or new architecture. Skip for small features (use ring:planning-small-features). Plans only — no edits.

Running the frontend (React/Next.js/TS) dev cycle from a tasks.md or backend handoff: drives frontend agents through Gate 0 TDD plus accessibility/visual/E2E/perf checks, Gate 7 parallel review, and Gate 8 user validation, with rolling-wave phase boundaries. Use when starting or resuming a gated frontend dev cycle. Skip for backend (use ring:running-dev-cycle) or docs-only work.

Tracking actual delivery progress against plan by scanning repo branches, commits, and PRs, matching work to roadmap epics and tasks.md, and producing an evidence-linked status report with per-task completion, variance, critical-path impact, and velocity/risk insights. Consumes the roadmap from ring:planning-delivery. Use for status updates or sprint checkpoints. Skip when no roadmap exists or the repo has no activity yet.

Capture decisions and requirements from conversation history. Use when user says "harvest", "capture decisions", or "save what we discussed" to persist architectural decisions into .rivet/systems.yaml.

RivetKit React client guidance. Use for React apps that connect to Rivet Actors with @rivetkit/react, create hooks with createRivetKit, or manage realtime state with useActor.

Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior

Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior

Analyzes the current project to surface high-value Routines use cases across the three trigger types (schedule, API, GitHub events). Usage: /routines-discover

Rstest best practices for config, CLI workflow, test writing, mocking, snapshot testing, DOM testing, coverage, multi-project setup, CI integration, performance and debugging. Use when writing, reviewing, or troubleshooting Rstest test projects.

Use when fixing Rubocop violations. Runs Rubocop to identify issues, applies fixes following project conventions, and explains non-obvious corrections.

Run citation-bearing deep research with deep-research-client across OpenAI, Perplexity, Edison/Falcon, Cyberian, and site-specific providers such as OpenScientist. Use when a user asks for research reports, literature reviews, source-backed synthesis, or provider/model trade-off guidance.

Execute an epic plan phase-by-phase, inline by default with opt-in worker spawns per task annotation

Analyze a user's codebase to verify it can use Runway's public API (server-side requirement)

Generate images directly using the Runway API via runnable scripts. Supports text-to-image with optional reference images.

Help users integrate Runway audio APIs (TTS, sound effects, voice isolation, dubbing)

Use when writing tests for next-safe-action actions or hooks -- Vitest patterns for testing server actions directly, middleware behavior, hooks with React Testing Library, validation errors, and server errors

Integrate with Salesforce for CRM operations. Use when you need to: (1) create and query Salesforce records, (2) manage accounts and opportunities, or (3) automate sales workflows.

Use for Salesforce Agentforce work — Agents (Topics, Actions), prompt templates, Atlas reasoning engine, Trust Layer integration, agent testing.

Use for Salesforce Einstein work — Discovery, Predictions, Next Best Action, Einstein Bots (legacy → migrating to Agentforce), prompt builder, model management.

Visual HTML canvas sandbox for agent-driven UI and live previews

Generate Docker sandbox configurations for safely running untrusted OpenClaw skills. Isolates filesystem, network, and process access.

Display native sandbox status, configuration, and recent violations

Disk-pressure defense for AI coding workloads. Use when: disk full, low space, ballast, cleanup, scan artifacts, emergency, sbh daemon, sbh status.

Initialize a new Python repository with correct structure following RAE guidelines. Use when the user says "new repo", "new project", "initialize", "scaffold", "create a project", "set up a repo", or "start a new package". Creates src/ layout, pyproject.toml, tests, .gitignore, and optionally a devcontainer.

Analyzes current conversation context to recommend the best skills and subagents for the task at hand. Use proactively when unsure which tool, skill, or agent to use.

Guide to creating CLI tools and scripts that augment Claude Code. Use when building bin/ executables, automation scripts, hook handlers, or tooling that abstracts repeated agent workflows.

This skill provides guidance for ultrawork agents on using SCRIPTS_PATH and accessing session data via scripts. Required knowledge for all ultrawork agents (explorer, planner, worker, verifier, reviewer, scope-analyzer).

Finish work and reset local environment for next task. Use this when the user is done with a feature branch, wants to clean up after a merged PR, or needs to reset their workspace.

Address PR review feedback and request re-review. Use this when the user needs to handle PR comments, respond to code review, or iterate on feedback from reviewers.

Ruthlessly analyze architectural seams—the interfaces, boundaries, and contracts between system components—to expose coupling problems, abstraction leaks, and design failures. Use when asked to review architecture, analyze coupling, find interface problems, improve module boundaries, audit dependencies, or redesign system structure. Produces uncompromising redesign proposals that prioritize correctness over backwards compatibility.

Search development memory using semantic understanding

Expert web researcher using advanced search techniques and synthesis. Masters search operators, result filtering, and multi-source verification. Handles competitive analysis and fact-checking. Use PROACTIVELY for deep research, information gathering, or trend analysis.

SEC EDGAR extraction pipeline: setup, filing discovery by CIK, recipe-driven extraction, and report generation.

Answer questions against the knowledge base wiki. Use when the user asks a question about their collected knowledge, wants to explore connections between topics, says "what do I know about X", or wants to search their wiki.

Manage encrypted local credentials for agent tooling with the `secrets` CLI: add, rotate, list, enable, disable, and inspect service integrations without exposing secret values in agent output.

Use when implementing secrets management, using Vault, AWS Secrets Manager, handling credentials in CI/CD, or asking about "secrets", "Vault", "credentials", "secret rotation", "API keys", "external secrets operator"

Security assessment using STRIDE threat modeling, OWASP Top 10, and CVSS scoring. Use for security reviews, threat modeling, and secure coding guidance.