Use when creating, editing, evaluating, testing, or verifying ANY skill or skill-related file (SKILL.md, skill resources, skill scripts, or skill assets). If you're asked to evaluate or test a skill's effectiveness, use this skill.
From lsnpx claudepluginhub landonschropp/agent-toolkit --plugin lsThis skill uses the workspace's default tool permissions.
assets/bash-script-template.shassets/ruby-script-template.rbassets/typescript-script-template.tsreferences/format-guide.mdreferences/getting-agents-to-follow-instructions.mdreferences/scripts.mdGuides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Orchestrates subagents to execute phased plans: deploys for implementation, verification, anti-pattern checks, code quality review, and commits only after passing checks.
When asked to create or edit a skill:
If helpful, ask clarifying questions about the skill's purpose:
Summarize your understanding and get user confirmation:
You cannot create a good skill without understanding what you're building.
After writing a skill, ask the user: "Would you like me to test the skill?" (Skills are often manually tested by the user, or can't be tested in an automated way, so you should ask before proceeding.)
If the user opts for the agent to test the skill:
If a script you're writing would benefit from the user interactively editing and saving a file, add to the SKILL.md: REQUIRED: Invoke the neovim skill. Have the script call edit-and-wait.sh.
STOP. Read these documents NOW. Not later. Not "as you go." Right now.