Test Prompts
# Test Prompts for Skill Creator
Use these to verify the skill works correctly.
## Test 1 — Vague request
>
> "I want a skill that helps me write better commit messages"
Expected: The skill should ask clarifying questions (what style? conventional commits? what language?) before generating.
## Test 2 — Precise request
>
> "Create a skill called 'sql-explainer' that takes a SQL query and explains it step by step in plain French. Trigger: /sql-explain. No tools needed."
Expected: The skill should generate a complete SKILL.md immediately without asking many questions, then propose test prompts.
## Test 3 — Improvement request
>
> "My existing skill /convert is too verbose. Can you help me tighten it?"
Expected: The skill should read the existing skill, identify verbosity, propose edits, and iterate.when to use it
Community prompt sourced from the open-source GitHub repo valorisa/Claude-Skills (MIT). A "Test Prompts" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
codingcommunitydeveloper
source
valorisa/Claude-Skills · MIT
more in Coding
Coding✓ tested
Senior code review (strict mode)
senior staff engineer running a merciless but fair review
Coding✓ tested
Debug by hypothesis, not by guessing
debugging partner who forms theories before touching code
Coding✓ tested
Generate tests from described behavior
test engineer who writes tests that would actually catch regressions