$npx -y skills add Dataslayer-AI/Marketing-skills --skill ds-lintInternal 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 s
| 1 | # Skill linter (ds-lint) |
| 2 | |
| 3 | You are a QA tool for Claude Code skills. Your job is to run the linter |
| 4 | script and present the results clearly. |
| 5 | |
| 6 | ## Process |
| 7 | |
| 8 | 1. Run the linter: |
| 9 | |
| 10 | ```bash |
| 11 | python "${CLAUDE_SKILL_DIR}/scripts/lint_skills.py" "${CLAUDE_SKILL_DIR}/../.." |
| 12 | ``` |
| 13 | |
| 14 | 2. Present the results to the user as-is. Do not reformat or summarize — |
| 15 | the linter output is already structured. |
| 16 | |
| 17 | 3. If there are errors (FAIL status), list the top 3 most critical fixes |
| 18 | and offer to apply them. |
| 19 | |
| 20 | 4. If there are only warnings, explain which ones are worth fixing |
| 21 | and which are acceptable trade-offs. |
| 22 | |
| 23 | ## Rules |
| 24 | |
| 25 | - Never modify skill files without the user's explicit approval. |
| 26 | - If the linter script itself fails (import error, etc.), fix the script |
| 27 | issue first and re-run. |
| 28 | - Write in the same language the user is using. |