Use when checking skill quality, validating frontmatter before commit, or diagnosing validator warnings. Runs the plugin validator on a skill, agent, or plugin directory — reports token complexity, broken links, frontmatter issues, and structural problems. Pass the path as an argument.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
If the user's intent does not match this skill, route through /plugin-creator:plugin-lifecycle.
<provided_path> $ARGUMENTS </provided_path>
Run uvx skilllint@latest check <path> via Bash, using the exact literal path in <provided_path/>. Never splice <provided_path/> directly into a !`...` injection line or any other shell-interpreted string — it is caller-supplied text and may contain characters (;, `, $(), |) that corrupt shell parsing on contact.
Read the findings straight from the command output. Each one carries its error code, severity, the
field or path it applies to, and the suggested fix. Report those to the user and act on them; do
not look up a code anywhere else. Re-run with --fix to apply the auto-fixable ones.
When <provided_path/> is a plugin directory, also run:
uv run "${CLAUDE_PLUGIN_ROOT}/skills/lint/scripts/audit_runtime_escapes.py" --plugin-dir <path>
It reports every path, markdown link, and cross-plugin reference in the plugin's runtime files
that resolves only in the authoring repo, with file:line for each. Exit 0 means clean; exit 1
means findings. Pass --all instead of --plugin-dir to sweep every plugin and get one count
each.
A finding is real when the text tells the runtime agent to act on something an installed
consumer does not have. Fenced blocks are exempt, because an anti-pattern shown in a fence is an
illustration rather than an instruction; angle-bracket placeholders are exempt for the same
reason. Move an illustrative real path into a fence, and write a generic one as
<plugin>/skills/<name>/SKILL.md.
The test behind each finding: a path, command, fact, or cross-plugin reference is present in
every environment, bundled and reached by a relative path inside the plugin, or inlined;
otherwise inline, bundle, guard, or delete it. A harness variable counts only where that harness
substitutes it. The scanner never reports a path built on ${CLAUDE_PLUGIN_ROOT} or
${CLAUDE_SKILL_DIR}, so check those by hand against the same test.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Add automated documentation updater to any Claude skill. Creates a Python sync script that downloads upstream docs, processes markdown for AI consumption, and maintains local cache with configurable refresh. Collects template variables, then delegates implementation through 5-phase workflow. Use when adding auto-updating reference documentation to plugins or skills.
日本語の概要は準備中です。原文の説明を表示しています。
SAM-style feature initiation workflow — discovery through codebase analysis, architecture spec, task decomposition, validation, and context manifest. Use when a user asks to add a feature, plan a feature, or convert an idea into an executable SAM plan.
日本語の概要は準備中です。原文の説明を表示しています。
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
日本語の概要は準備中です。原文の説明を表示しています。
Browser automation for AI agents using the agent-browser CLI and Playwright. Use when navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, logging into sites, or automating any browser task. Triggers on "open a website", "fill out a form", "click a button", "scrape data", "test this web app", "automate browser actions", or any programmatic web interaction request.
日本語の概要は準備中です。原文の説明を表示しています。
Runs the description-drift experiment — spawns all Claude Code agents simultaneously to collect self-reported capabilities, then compares them against static frontmatter descriptions to reveal how reliable orchestrator routing based on descriptions actually is. Use when measuring description drift across the agent fleet, re-running the capability collection experiment, analyzing a specific agent's self-reported capabilities, or auditing whether frontmatter descriptions accurately reflect agent behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Create or adapt Claude Code agent definitions. Use when creating an agent, changing subagent configuration, selecting agent scope, or designing a specialized delegation role.
日本語の概要は準備中です。原文の説明を表示しています。