From fieldguides
Validates skill quality — preprocessing safety, frontmatter, line counts, references. Use when checking skills, validating SKILL.md, or when skillcheck, lint skill, or validate skill are mentioned.
npx claudepluginhub outfitter-dev/outfitter --plugin fieldguidesThis skill is limited to using the following tools:
Validate skill quality across one or more skill directories.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Guides MCP server integration in Claude Code plugins via .mcp.json or plugin.json configs for stdio, SSE, HTTP types, enabling external services as tools.
Validate skill quality across one or more skill directories.
Scan SKILL.md files for <bang>`command` patterns that trigger Claude Code's preprocessor unintentionally:
!bun ${CLAUDE_PLUGIN_ROOT}/skills/skillcheck/scripts/lint-preprocessing.ts ${ARGUMENTS:-${CLAUDE_PLUGIN_ROOT}}
The linter reports:
| Finding | Fix |
|---|---|
Unintentional <bang>`command` in SKILL.md | Replace ! with <bang> |
| Intentional preprocessing | Add metadata.preprocess: true to frontmatter |
<bang> ConventionSKILL.md files are preprocessed by Claude Code — any <bang>`command` syntax executes when the skill loads. To safely document or reference the syntax:
<bang> as a stand-in for !! is fine and encouraged! is required (that's the feature)Skills that intentionally preprocess (running scripts at load time) should declare it:
metadata:
preprocess: true
Beyond preprocessing, verify skill quality with existing tools:
# Frontmatter validation
bun ${CLAUDE_PLUGIN_ROOT}/scripts/validate-skill-frontmatter.ts <path-to-SKILL.md>
# Full plugin validation
bun ${CLAUDE_PLUGIN_ROOT}/scripts/validate-plugin.ts <plugin-directory>
After reviewing linter results, spawn the quartermaster agent to run deeper validation — frontmatter schema, naming conventions, description quality, line counts, and reference integrity. Pass it the same path argument.
<bang>`command` in SKILL.md (this linter)