Use when testing Windows CRLF line endings.

Body deliberately exceeds the Level 2 line/token budget to exercise the progressive-disclosure warning.

Valid description, but the name field does not match the parent directory name.

Ask which docs path a contribution should take. A user-started orchestrator.

Extracts examples for testing the agentskills.io spec validator. Use when validating a well-formed skill against the open spec.

MANDATORY procedure for any pr_review task whose rubric is `pr-security-v1` or whose prompt asks for a security review. Read this skill FIRST before reading the PR diff. Defines the sequential recon → hunt → self-validate → trace → dedup → report pipeline a single agent must run against a PR. Without it, the review will be incomplete and the structured output will be rejected.

Test

Persistent memory and cryptographic identity via MoltNet. Connects to a remote MCP server over SSE, authenticates via OAuth2 client_credentials, and stores diary entries and cryptographic signatures. Requires the moltnet CLI for local Ed25519 signing operations. Credentials are stored locally at ~/.config/moltnet/moltnet.json.

Diagnose cookbook quality: skimmability, clarity, and reader load. Use when recipes are hard to follow or a new cookbook is starting. It does not set house voice (that's `docs-writing-style`).

Use doraval to validate, measure drift, and judge skills and plugins. Use when authoring or reviewing context engineering artifacts for AI coding agents (works for Codex too).

A test skill for fixture purposes

Second skill in the multi-skill fixture repo, used to test fan-out validation.

Design authentic launch stories, TAB, and dev packaging. Use when planning a launch narrative, TAB outreach, or pricing for developers. It does not design first-success DX (that's `devrel-dx-craft`).

First skill in the multi-skill fixture repo, used to test fan-out validation.

Nested skill under packages/x/skills, used to test recursive discovery.

Migrate applications from AI SDK 6.x to AI SDK 7.0. Use when upgrading Vercel AI SDK packages, fixing v7 migration errors, or when the user mentions AI SDK v6, v7, upgrade, migration, breaking changes, system to instructions, fullStream, telemetry, tool context, or finalStep.

Design first-success DX and pick sample app vs recipe vs pattern. Use when auditing onboarding or choosing content types for developers. It does not write launch stories (that's `devrel-story-craft`).

Review agent context (SKILL.md, plugin, rule, AGENTS.md) with dora before reporting done. Also when the user asks to review, diagnose, or clean up Claude, Cursor, Codex, Copilot, or Grok context.

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.

Use when writing or reviewing MoltNet e2e tests (apps/*/e2e, libs/mcp-test-harness): use @moltnet/api-client (createClient + typed fns like createDiaryEntry) not raw fetch for in-spec endpoints. Raw fetch only for /health, /oauth2/token, /auth/register.