{"slug":"feature-radar-validate","title":"feature-radar-validate","summary":"Validate SKILL.md frontmatter and .feature-radar/ files against format rules. Runs validate.sh, reports errors/warnings, and auto-fixes issues. MUST use this skill after editing any SKILL.md or .feature-radar/ file, even if the user doesn't ask — catches format bugs like the Agen","platform":"Claude","tags":[],"authorName":"LLM Mart","authorSlug":"llm-mart","score":0,"source":"github","price":null,"verified":false,"createdAt":"2026-09-30T19:53:11.724287Z","repo":{"url":"https://github.com/runkids/my-skills","stars":14,"forks":1,"license":null,"updatedAt":"2026-09-30T18:53:08Z"},"bodyHtml":"
\n

name: feature-radar-validate\ndescription: |\nValidate SKILL.md frontmatter and .feature-radar/ files against format rules. Runs\nvalidate.sh, reports errors/warnings, and auto-fixes issues. MUST use this skill after\nediting any SKILL.md or .feature-radar/ file, even if the user doesn't ask — catches format\nbugs like the Agent Skills spec's 1024-char description limit before they break the skill.\nUse when the user asks to validate, lint, or verify skills or .feature-radar/ files, after\nediting either, or before committing changes that touch skills/ or .feature-radar/.

\n

Validate Feature Radar

\n

Run skills/feature-radar-validate/scripts/validate.sh from the project root to check SKILL.md frontmatter and .feature-radar/ SPEC compliance, then fix any issues found.

\n

Why This Matters

\n

The description field in SKILL.md has a 1024-character limit in the Agent Skills spec (agentskills.io/specification, checked 2026-09-29). Agents that enforce the spec may reject a longer description; Claude Code instead truncates the skill listing at 1,536 characters, cutting off trigger text. Similarly, .feature-radar/ files must follow SPEC.md naming and metadata conventions or downstream tools can't parse them. This skill catches these issues before they cause problems.

\n

Workflow

\n

Step 1: Run Validation

\n
bash skills/feature-radar-validate/scripts/validate.sh\n
\n

Read the full output. Note the exit code:

\n\n

Step 2: Report Results

\n

Present the results clearly:

\n
── Feature Radar: Validate ──\n\nErrors:   {n}\nWarnings: {n}\n\n{List each error/warning with file path and issue}\n
\n

If everything passes, say so and stop. No further action needed.

\n

Step 3: Auto-Fix (if errors or warnings found)

\n

For each issue, apply the appropriate fix:

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
IssueFix Strategy
description > 1024 charsTrim to fit — cut the least essential trigger phrases or examples first, keep the core \"what it does\" and \"Use when\" intact. Show before/after char count.
description missing \"Use when\"Add a \"Use when:\" section based on the skill's purpose
name not kebab-caseRename to kebab-case
name missingDerive from directory name
name > 64 charsPropose a shorter name and ask user to confirm — the name is how the skill is invoked
name does not match directorySet name to the directory name; if the name is the intended one, ask user before renaming the directory (other skills reference it by path)
Body > 500 linesFlag for user — this requires judgment about what to extract into reference files
Filename not {nn}-{slug}.mdRename file to correct format
Missing **Status**: / **Impact**: / **Effort**:Add field with a placeholder value, ask user to confirm
base.md count mismatchUpdate the Tracking Summary table counts
\n

After fixing, re-run bash skills/feature-radar-validate/scripts/validate.sh to confirm all errors are resolved.

\n

Step 4: Completion Summary

\n
── Feature Radar: Validate Complete ──\n\nFiles fixed:   ~ {path} ({what changed})\nErrors fixed:  {n}\nWarnings fixed: {n}\nRemaining:     {n} (need user input)\n
\n

Proactive Triggering

\n

When you notice yourself editing skills/*/SKILL.md or .feature-radar/**/*.md, run validation afterward without being asked. A quick bash skills/feature-radar-validate/scripts/validate.sh check takes seconds and prevents silent breakage.

\n","files":[{"path":"scripts/validate.sh","sizeBytes":5481,"isText":true},{"path":"SKILL.md","sizeBytes":3578,"isText":true}],"reviewScore":null,"reviewSummary":null,"trust":{"provenance":"trusted-source-unreviewed","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow.","bodySource":null},"bodyLocked":false,"purchaseUrl":null,"sourceUrl":null,"report":{"provenance":"trusted-source-unreviewed","screen":{"ran":true,"outcome":"clean","suspicious":0,"notes":0,"hiddenCharacters":false},"virusScan":{"engine":"clamav","status":"clean","scannedAt":"2026-09-30T19:53:59.225155Z","sha256":"DE5BFA7D40FC254C75C6A208F9C420B55799F9757A86D8992115EDC0E40C125D","sizeBytes":3777},"review":null,"source":{"repositoryUrl":"https://github.com/runkids/my-skills","path":"feature-radar/feature-radar-validate","license":null,"commit":"7f33dbc5934c5e27920b3e88e8a6ccb06f304b98","subtreeSha":"6BD743E64094FF411F0145DE2C54291ECD8DABFDC251CD86AE2B84AAD09DE027","lastSyncedAt":"2026-09-30T19:53:09.4483Z"},"reviewedAt":"2026-09-30T20:00:57.82203Z","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow."},"install":[{"target":"skills-cli","command":"npx skills add https://github.com/runkids/my-skills/tree/main/feature-radar/feature-radar-validate"},{"target":"claude-code","command":"claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install runkids-my-skills@llmmart"},{"target":"git","command":"git clone https://github.com/runkids/my-skills.git"}]}