agentleFS
manastalukdarmanastalukdar/ai-devstudio/.claude/skills/skill-validator/SKILL.md

skill-validator

Skill1 starsChanged 7 months agoMITView on GitHub

Internal skill that validates a new or modified AI DevStudio skill against project standards. Checks YAML frontmatter, token optimization section, line limit, and naming conventions. Used by the code-reviewer agent during PR review.

17 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use fetch-library-docs, browsing-with-playwright and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Rehan-Ul-HaqSkill

    fetch-library-docs

    Fetches official documentation for external libraries and frameworks (React, Next.js, Prisma, FastAPI, Express, Tailwind, MongoDB, etc.) with 60-90% token savings via content-type filtering. Use this skill when implementing features using library APIs, debugging library-specific errors, troubleshooting configuration issues, installing or setting up frameworks, integrating third-party packages, upgrading between library versions, or looking up correct API patterns and best practices. Triggers automatically during coding work - fetch docs before writing library code to get correct patterns, not after guessing wrong.

    Also in 6 projects that use this

  • mjunaidcaSkill

    browsing-with-playwright

    Browser automation using Playwright MCP. Navigate websites, fill forms, click elements, take screenshots, and extract data. Use when tasks require web browsing, form submission, web scraping, UI testing, or any browser interaction. NOT when only fetching static content (use curl/wget instead).

    Also in 5 projects that use this

  • muhammad-anas35Skill

    skill-creator-pro

    Creates production-grade, reusable skills that extend Claude's capabilities. This skill should be used when users want to create a new skill, improve an existing skill, or build domain-specific intelligence. Gathers context from codebase, conversation, and authentic sources before creating adaptable skills.

    Also in 7 projects that use this

  • dazuckSkill

    interview

    Interview me about a plan to flesh out requirements before implementation. Asks non-obvious questions one at a time until all ambiguities are resolved.

    Also in 4 projects that use this

  • GoogleSkill

    internal-comms

    A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

    Also in 4 projects that use this

  • AnthropicSkill

    xlsx

    Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Claude needs to work with spreadsheets (.xlsx, .xlsm, .csv, .tsv, etc) for: (1) Creating new spreadsheets with formulas and formatting, (2) Reading or analyzing data, (3) Modify existing spreadsheets while preserving formulas, (4) Data analysis and visualization in spreadsheets, or (5) Recalculating formulas

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify the skill is in the correct location:

    line 20
  2. Distinctive:

    Read the skill file and check:

    line 30
  3. Distinctive:

    No unknown frontmatter fields (warn on unrecognized keys)

    line 35
  4. Very specific:

    Check that the file contains a ## Token Optimization section:

    line 52
  5. Distinctive:

    No underscores, no camelCase

    line 63

“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill Validator Skill

Internal skill used by the code-reviewer agent when reviewing skill contributions. Validates a skill file against AI DevStudio standards.

Usage

Called with the path to a skill file to validate. Context will contain the file path.

Validation Checks

1. File Location

Verify the skill is in the correct location:

skills/<skill-name>/SKILL.md

Reject if in wrong directory or wrong filename.

2. YAML Frontmatter

Read the skill file and check:

  • name field present and matches directory name (kebab-case)
  • description field present and non-empty (>10 characters)
  • disable-model-invocation field present and is a boolean
  • No unknown frontmatter fields (warn on unrecognized keys)

3. Line Count

Bash: wc -l < skills/<name>/SKILL.md

Warn if over 100 lines of instruction content (excluding frontmatter, code blocks, Token Optimization section).

Estimate instruction lines:

  • Total lines minus frontmatter (lines between ---)
  • Minus code block lines (between ``` markers)
  • Minus Token Optimization section

4. Token Optimization Section

Check that the file contains a ## Token Optimization section:

Bash: grep -n "## Token Optimization" skills/<name>/SKILL.md

Fail if missing. The section must include expected token range.

5. Naming Conventions

  • Directory name: kebab-case only
  • No underscores, no camelCase
  • Name matches name field in frontmatter

6. No Hardcoded Paths

Bash: grep -n "/Users/\|/home/[a-z]\|C:\\Users" skills/<name>/SKILL.md

Fail if any absolute user-specific paths found.

Output Format

Skill Validation: skills/<name>/SKILL.md

PASS / FAIL / WARNINGS

Checks:
  [PASS] File location
  [PASS] YAML frontmatter
  [WARN] Line count: 112 lines (limit: 100 instruction lines)
  [PASS] Token Optimization section present
  [PASS] Naming conventions
  [PASS] No hardcoded paths

Summary: Ready to merge / Needs fixes

Token Optimization

Expected range: 150-400 tokens

Patterns used: Bash grep for specific checks, early exit on critical failures

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.