agents-standards
Standards for authoring SDD plugin agents — frontmatter, self-containment, skill references, and no-user-interaction rules.
Validate plugin and marketplace manifest files against the official Claude Code specification
$ npx -y skills add LiorCohen/sdd --skill manifest-validation --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/manifest-validationContext preview
The summary Claude sees to decide when to auto-load this skill.
Validate plugin and marketplace manifest files against the official Claude Code specification
name: manifest-validation description: Validate plugin and marketplace manifest files against the official Claude Code specification
Validates `.claude-plugin/marketplace.json` and `plugin/.claude-plugin/plugin.json` against the official Claude Code plugin specification.
**Documentation Reference**: [Claude Code Plugins Reference](https://code.claude.com/docs/en/plugins-reference) **Claude Code Version**: 2.1.27 **Schema Fetched**: 2026-01-31
---
---
Run through all checks in order. Stop at the first failure.
# Both must parse without errors jq . plugin/.claude-plugin/plugin.json > /dev/null jq . .claude-plugin/marketplace.json > /dev/null
**plugin.json** - Must have: | Field | Type | Description | |-------|------|-------------| | `name` | string | Unique identifier (kebab-case, no spaces) |
**marketplace.json** - Must have: | Field | Type | Description | |-------|------|-------------| | `name` | string | Marketplace identifier (kebab-case) | | `owner.name` | string | Maintainer name | | `plugins` | array | List of plugins (non-empty) |
**Each plugin entry** - Must have: | Field | Type | Description | |-------|------|-------------| | `name` | string | Plugin identifier | | `source` | string\|object | Where to fetch plugin |
# Check required fields jq -e '.name' plugin/.claude-plugin/plugin.json jq -e '.name, .owner.name, .plugins[0].name, .plugins[0].source' .claude-plugin/marketplace.json
If both files specify version, they must be identical:
PLUGIN_VER=$(jq -r '.version // empty' plugin/.claude-plugin/plugin.json) MARKET_VER=$(jq -r '.plugins[0].version // empty' .claude-plugin/marketplace.json) [ "$PLUGIN_VER" = "$MARKET_VER" ] && echo "OK: $PLUGIN_VER" || echo "MISMATCH: plugin=$PLUGIN_VER marketplace=$MARKET_VER"
All component paths must be relative to plugin root and start with `./`:
| Field | Example | |-------|---------| | `commands` | `["./core/commands/sdd.md"]` | | `skills` | `["./core/skills/"]` | | `mcpServers` | `"./.mcp.json"` | | `lspServers` | `"./.lsp.json"` | | `outputStyles` | `"./styles/"` |
# Check all command paths start with ./ jq -r '.commands[]? // empty' plugin/.claude-plugin/plugin.json | while read -r p; do echo "$p" | grep -qE '^\./' || echo "ERROR: command path must start with ./: $p"; done
Verify files referenced by paths actually exist:
# Check command files exist
jq -r '.commands[]? // empty' plugin/.claude-plugin/plugin.json | while read -r p; do
[ -f "plugin/${p#./}" ] || [ -d "plugin/${p#./}" ] && echo "OK: $p" || echo "ERROR: not found: plugin/${p#./}"
done
# Check skill directories exist
jq -r '.skills[]? // empty' plugin/.claude-plugin/plugin.json | while read -r p; do
[ -d "plugin/${p#./}" ] && echo "OK: $p" || echo "ERROR: not found: plugin/${p#./}"
doneMarketplace plugin source paths must point to valid directories:
SOURCE=$(jq -r '.plugins[0].source' .claude-plugin/marketplace.json) [ -d "$SOURCE" ] && echo "OK: $SOURCE" || echo "ERROR: source directory not found: $SOURCE"
Names must be kebab-case (lowercase letters, numbers, hyphens):
jq -r '.name' plugin/.claude-plugin/plugin.json | grep -E '^[a-z0-9]+(-[a-z0-9]+)*$' || echo "ERROR: invalid name format"
Paths must not contain `../` (security restriction):
jq -r '.. | strings | select(contains("../"))' plugin/.claude-plugin/plugin.json && echo "ERROR: path traversal detected" || echo "OK: no path traversal"---
Run all checks at once:
echo "=== Manifest Validation ==="
# 1. JSON syntax
echo -n "1. JSON syntax: "
jq . plugin/.claude-plugin/plugin.json > /dev/null 2>&1 && \
jq . .claude-plugin/marketplace.json > /dev/null 2>&1 && \
echo "OK" || echo "FAIL"
# 2. Required fields
echo -n "2. Required fields: "
jq -e '.name' plugin/.claude-plugin/plugin.json > /dev/null 2>&1 && \
jq -e '.name and .owner.name and (.plugins | length > 0)' .claude-plugin/marketplace.json > /dev/null 2>&1 && \
echo "OK" || echo "FAIL"
# 3. Version match
echo -n "3. Version match: "
P=$(jq -r '.version // "none"' plugin/.claude-plugin/plugin.json)
M=$(jq -r '.plugins[0].version // "none"' .claude-plugin/marketplace.json)
[ "$P" = "$M" ] && echo "OK ($P)" || echo "FAIL (plugin=$P, marketplace=$M)"
# 4. Paths start with ./
echo -n "4. Path format: "
FAIL=0
for p in $(jq -r '.commands[]?, .skills[]?' plugin/.claude-plugin/plugin.json 2>/dev/null); do
[[ "$p" == ./* ]] || { echo "FAIL ($p)"; FAIL=1; break; }
done
[ $FAIL -eq 0 ] && echo "OK"
# 5. Referenced files exist
echo -n "5. Files exist: "
FAIL=0
for p in $(jq -r '.commands[]?, .skills[]?' plugin/.claude-plugin/plugin.json 2>/dev/null); do
[ -f "plugin/${p#./}" ] || [ -d "plugin/${p#./}" ] || { echo "FAIL (missing: plugin/${p#./})"; FAIL=1; break; }
done
[ $FAIL -eq 0 ] && echo "OK"
# 6. Source directory exists
echo -n "6. Source exists: "
S=$(jq -r '.plugins[0].source' .claude-plugin/marketplace.json)
[ -d "$S" ] && echo "OK ($S)" || echo "FAIL ($S not found)"
# 7. Name format
echo -n "7. Name format: "
jq -r '.name' plugin/.claude-plugin/plugin.json | grep -qE '^[a-z0-9]+(-[a-z0-9]+)*$' && \
echo "OK" || echo "FAIL"
# 8. No path traversal
echo -n "8. No traversal: "
jq -r '.. | strings' plugin/.claude-plugin/plugin.json 2>/dev/null | grep -q '\.\.' && \
echo "FAIL" || echo "OK"
echo "=== Done ==="---
{
"name": "plugin-name", // REQUIRED: kebab-case
"version": "1.0.0",Structure for AI-assisted development AI coding assistants are powerful but chaotic. You prompt, you get code, but then what?
Repo: LiorCohen/sdd
Standards for authoring SDD plugin agents — frontmatter, self-containment, skill references, and no-user-interaction rules.
Standards for authoring SDD plugin commands — frontmatter, user interaction, skill/agent invocation, CLI integration, and output formatting.
Create a commit following repository guidelines with proper versioning and changelog updates.
Two-step self-review at every task lifecycle phase. Step 1 (this skill) runs in-context to gather session signals — files read vs grepped, user pushback, build…
D2 diagramming language reference for architecture diagrams, sequence diagrams, grid layouts, SQL tables, and class diagrams. Produces .d2 files rendered via…
Writes and maintains user-facing documentation for the SDD plugin. Proactively detects when docs are out of sync with plugin capabilities.