Iteratively refine an existing writer skill generated by Voiceprint. Asks what you want to change first, then applies targeted edits to the single SKILL.md. Fast and focused — no upfront summary dump.
From voiceprintnpx claudepluginhub jamesckemp/claude-plugins --plugin voiceprintThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
Surgically improve an existing writer skill without re-running the full questionnaire. Users discover gaps when using their writer skill in practice - this workflow lets them fix those gaps immediately.
If plan mode is active, exit it now using ExitPlanMode before starting this workflow. All voiceprint commands run in execute mode.
SKILL.md.All reference file paths are resolved in the /refine command output above. Use those exact paths — do not search or glob.
Phase 1: Load & Check (~30s) → Read file, VERSION GATE, ask what to refine
Phase 2: Apply (~1 min) → Surgical edits to SKILL.md
Phase 3: Validate (~1 min) → Generate test content targeting the change
Phase 4: Cross-Check (opt) → Flag inconsistencies within the profile
Phase 5: Summary (~30s) → List changes made
Do NOT search, glob, or look up the writer skill by name — use the provided path directly.
Read from the provided directory path silently — do NOT display a summary:
{TARGET_DIR}/SKILL.md - The writer skillIf SKILL.md is missing, tell the user:
I couldn't find a writer skill at that path. I need
SKILL.mdin the directory. Check the path and try again.
Then stop.
Safety net: The /refine command already verified the version before loading this skill. If you notice voice-profile.md exists in the directory and SKILL.md has no voiceprint-version frontmatter field, stop and tell the user to run /voiceprint update {TARGET_DIR} first.
Do NOT display a profile summary. The user already knows their profile — they're here because something specific needs fixing. Go straight to the question:
Use AskUserQuestion:
Based on their selection, ask a follow-up for details.
For "Add forbidden patterns":
Ask (free text, not AskUserQuestion):
What patterns have you noticed that don't sound like you? Give me examples — specific phrases, sentence structures, or general categories. If you've seen them in content generated with your skill, paste an example.
After they respond, read the AI tells catalog listed in Reference Files above to check if the pattern falls into an existing category. If it does, offer to add the full category:
Use AskUserQuestion:
For "Remove forbidden patterns":
List the current items from the Forbidden Patterns section in SKILL.md and ask which ones to remove.
For "Adjust tone/formality":
Ask (free text):
How would you describe the adjustment? For example: "more casual", "less hedging", "more direct", "allow more humor". You can also paste an example of writing that has the tone you want.
For "Add active patterns":
Ask (free text):
What patterns or phrases do you want used more? Paste examples from your own writing if you have them.
For "Provide a writing example":
Ask (free text):
Paste a writing sample that represents your voice well. Tell me what context it's from (tweet, email, blog post, message, etc.) and I'll add it as an exemplar to your profile.
For "Update content templates":
Ask which content template (Social Media, Blog, Email, Documentation) and what to change.
For "Something else":
Ask them to describe what they need in free text.
Summarize what you're going to change before making edits:
Here's what I'll do:
{numbered list of specific changes}
Sound right?
Use AskUserQuestion:
If they want to adjust, loop back to gather more detail.
Make surgical edits to SKILL.md. The merged file contains all voice data in one place — no cross-file syncing needed.
The SKILL.md contains these sections that may need editing:
| Section | Contains |
|---|---|
| Quick Reference | 10-dimension summary table |
| Voice Exemplars | 6 categorized writing samples |
| Voice Profile | Core Characteristics, Sentence Metrics, Punctuation, Vocabulary, Voice Detail |
| Voice Markers | Signature Moves, Natural Expressions, Structural Preferences, Rhythm |
| Platform Formats | Social, Blog, Email, Docs with synthesized exemplars |
| Sample Transformations | 3 before/after pairs |
| Forbidden Patterns | Rejected Phrases, Rejected Structures, Additional Rejections |
| Internal Checks | Silent verification rules |
| Calibration Notes | Edge cases and context notes |
When adding a forbidden pattern category from the AI tells catalog:
Write a short paragraph (3-5 sentences) that specifically targets the change made. The goal is to test whether the skill correctly applies the refinement.
Examples:
Here's a test paragraph written with the updated skill. I specifically targeted the area we changed:
{test paragraph}
Does this look right?
Use AskUserQuestion:
If more adjustment is needed, loop back to Phase 1 Step 3 with the additional feedback.
After applying changes, offer to cross-check the updated skill for internal consistency.
Use AskUserQuestion:
If yes:
Present a clear summary:
Changes applied to {PROFILE_NAME}-writer:
{numbered list of changes with before/after where relevant}
Your writer skill has been updated. The changes will apply next time you (or any AI tool) uses the
{PROFILE_NAME}-writerskill.
/voiceprint generate first./refine command's pre-flight check before this skill loads. If somehow reached here with an old format, stop and direct user to /voiceprint update first.