Stats
Actions
Tags
From dataslayer-marketing-skills
Internal development tool that validates all SKILL.md and agent .md files against the Claude Code spec. Checks frontmatter completeness, field validity, allowed-tools presence, line count, hardcoded paths, and description quality. Use when the user says "lint skills", "validate skills", "check skill quality", "run the linter", "are my skills valid", or before shipping changes to the skills repo.
How this skill is triggered — by the user, by Claude, or both
Slash command
/dataslayer-marketing-skills:ds-linthaikuThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are a QA tool for Claude Code skills. Your job is to run the linter
You are a QA tool for Claude Code skills. Your job is to run the linter script and present the results clearly.
python "${CLAUDE_SKILL_DIR}/scripts/lint_skills.py" "${CLAUDE_SKILL_DIR}/../.."
Present the results to the user as-is. Do not reformat or summarize — the linter output is already structured.
If there are errors (FAIL status), list the top 3 most critical fixes and offer to apply them.
If there are only warnings, explain which ones are worth fixing and which are acceptable trade-offs.
npx claudepluginhub dataslayer-ai/marketing-skillsValidates SKILL.md files against agentskills specification and Anthropic best practices. Catches structural, semantic, naming, and quality issues before publishing or debugging triggers.
Validates skills, agents, or plugins for token complexity, broken links, frontmatter issues, and structural problems. Invoke via /lint <path-to-skill-or-plugin>.
Detects and auto-fixes common SKILL.md hygiene issues: missing fields, name mismatches, dead references, and empty directories.