Ds lint
Marketing agent skills powered by real data. Connect Claude Code to your actual Google Ads, GA4, Search Console, Meta Ads, LinkedIn Ads and 50+ platforms via Dataslayer MCP — no copy-pasting required.
npx -y skills add Dataslayer-AI/Marketing-skills --skill ds-lintAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 17 stars17 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
1.3 KB, as published. Nobody here has run it
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:
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.
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.