ds-lint
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.
Install
With your agent
Install OMGSkills skill "dataslayer-ai/marketing-skills:skills/ds-lint" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/Dataslayer-AI/Marketing-skills /tmp/Marketing-skills && ln -s /tmp/Marketing-skills/skills/ds-lint ~/.claude/skills/ds-lintFrom README
Skill linter (ds-lint) You are a QA tool for Claude Code skills. Your job is to run the linter script and present the results clearly. Process Run the linter: 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. Rules Never modify skill files without the user's explicit approval. If the linter script itself fails (import error, etc.), fix the script issue first and re-run. Write in the same language the user is using.