Summary
Per the skill-development best practices, SKILL.md body content should use imperative/infinitive form, not passive voice or second person. Several skills contain passive constructions that should be converted.
Writing Style Requirements
From skill-development skill:
Writing Style: Write the entire skill using imperative/infinitive form (verb-first instructions), not second person. Use objective, instructional language (e.g., "To accomplish X, do Y" rather than "You should do X" or "If you need to do X").
Examples of Required Conversions
Passive → Imperative
| Current (Passive) |
Correct (Imperative) |
| "Understanding agent structure enables creating..." |
"To create agents effectively, understand the structure..." |
| "This allows you to..." |
"Use this to..." |
| "Hooks are loaded when..." |
"Claude Code loads hooks when..." |
| "This provides..." |
"Use this pattern to..." |
| "You can configure..." |
"Configure..." |
Second Person → Imperative
| Current (Second Person) |
Correct (Imperative) |
| "You should validate inputs" |
"Validate inputs" |
| "You need to check..." |
"Check..." |
| "If you want to..." |
"To [goal]..." |
Skills to Review
All skills should be audited, but these have notable instances:
Acceptance Criteria
Priority
Low - Polish task that improves consistency but doesn't affect functionality.
Summary
Per the skill-development best practices, SKILL.md body content should use imperative/infinitive form, not passive voice or second person. Several skills contain passive constructions that should be converted.
Writing Style Requirements
From
skill-developmentskill:Examples of Required Conversions
Passive → Imperative
Second Person → Imperative
Skills to Review
All skills should be audited, but these have notable instances:
agent-development- "Understanding agent structure enables creating..."command-development- Mixed styles in explanatory sectionshook-development- Some passive in lifecycle sectionmcp-integration- "This allows..." patternsplugin-structure- Generally good, minor polishplugin-settings- Some "you can" patternsskill-development- Should be exemplary as meta-skillAcceptance Criteria
Priority
Low - Polish task that improves consistency but doesn't affect functionality.