How to Test a SKILL.md Skill Before Publishing

Publishing a broken or poorly-tested skill damages your reputation as a creator. Bad reviews are permanent. Here's how to test properly before listing.

Quick Answer: To test an AI skill before publishing, follow these steps: test trigger reliability with diverse prompts, evaluate output quality on real projects, check edge cases, verify cross-agent compatibility, and review the description/metadata to ensure accuracy and clarity.

Step 1: Test trigger reliability

The most common failure mode: the skill doesn't activate when it should, or activates when it shouldn't.

Start a Claude Code session and try 5 different prompts that should trigger your skill. Then try 5 prompts that are similar but shouldn't trigger it.

For a code review skill:

Should trigger:

• "Review my latest changes"
• "Check this code for bugs"
• "Do a code review on the auth module"
• "Look for security issues in this PR"
• "Review the code I just wrote"

Should NOT trigger:

• "Write a new function to parse JSON"
• "Help me with my Docker configuration"
• "Explain what this regex does"
• "Create a README for this project"
• "Fix the bug on line 45"

If it triggers on fewer than 4 of the first 5, your description is too narrow. If it triggers on more than 1 of the second 5, your description is too broad.

For help writing better descriptions, see How to Write a SKILL.md Description That Triggers.

Skills built by the community

code-reviewer

Free

Run a structured code review on your recent changes without waiting for a teammate. This skill checks for security vulnerabilities (SQL injection, XSS, authentication bypasses), logic errors, edge cases, performance issues, and style violations.Findings are organized by severity: Critical, Warning, and Suggestion. Each finding includes the file, line number, a description of the issue, and a concrete fix. Use it as a first pass before peer review, or as your only reviewer on solo projects.

Get this skill

git-commit-writer

Free

Stop writing vague commit messages. This skill reads your actual staged diff and generates precise, informative commit messages following the Conventional Commits specification. It detects the commit type (feat, fix, refactor, docs, chore, etc.), identifies the scope from the changed files, flags breaking changes, and suggests splitting commits when multiple logical changes are staged. Works with any git repository.`

Get this skill

readme-generator

Free

Point this skill at any project and it generates a real README from your actual codebase. It scans package.json, pyproject.toml, Cargo.toml, or equivalent to detect your language, framework, and dependencies. It reads your .env.example for setup instructions, checks for Dockerfiles and CI config, and produces a README with only the sections that apply to your project. No placeholder text, no generic filler. Every line is derived from what it actually finds in your repo.

Get this skill

Browse all skills

Step 2: Test output quality

Once the skill triggers, does it produce useful output? Test on a real project — not a toy example. Use a codebase with real complexity, real patterns, and real edge cases.

Check:

• Does the output follow the instructions in the skill?
• Is it actually better than Claude Code without the skill?
• Does it match the conventions of the target project?
• Are there factual errors or hallucinated patterns?

Step 3: Test edge cases

• Empty files or projects with no code
• Very large files (1000+ lines)
• Multiple languages in the same project
• Unusual project structures
• Projects using uncommon frameworks or tools

Your skill doesn't need to handle every edge case perfectly, but it shouldn't crash or produce obviously wrong output.

Step 4: Test cross-agent compatibility

If you're listing the skill as compatible with multiple agents, test it in each one:

# Test in Claude Code
cp -r ~/.claude/skills/my-skill/ /tmp/skill-test/
ls ~/.claude/skills/my-skill/SKILL.md

# Test in Codex CLI
cp -r /tmp/skill-test/ ~/.codex/skills/my-skill/

# Test in Gemini CLI
cp -r /tmp/skill-test/ ~/.gemini/skills/my-skill/

Run the same test prompts in each agent. The skill should produce comparable output across all of them.

Step 5: Test the description and metadata

Your marketplace listing is the first thing buyers see. Check:

• Does the title clearly communicate what the skill does?
• Does the description match the actual behavior?
• Are the tags accurate?
• Is the reading time/complexity appropriate for the skill's content?

Pre-publish checklist

• Skill triggers on relevant prompts (5/5)
• Skill does NOT trigger on unrelated prompts (0/5)
• Output quality is better than Claude without the skill
• Tested on a real project, not a toy example
• Edge cases don't cause crashes or garbage output
• Tested in all listed compatible agents
• SKILL.md frontmatter is valid (name, description)
• No hardcoded paths, secrets, or personal info
• Description and metadata are accurate

---

Publish your tested skill on Agensi — 80/20 revenue split, security review included.