Skip to content

refactor: convert passive voice to imperative form in skill content #4

@sjnims

Description

@sjnims

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:

  • agent-development - "Understanding agent structure enables creating..."
  • command-development - Mixed styles in explanatory sections
  • hook-development - Some passive in lifecycle section
  • mcp-integration - "This allows..." patterns
  • plugin-structure - Generally good, minor polish
  • plugin-settings - Some "you can" patterns
  • skill-development - Should be exemplary as meta-skill

Acceptance Criteria

  • All "Understanding X enables Y" → "To Y, understand X"
  • All "This allows you to..." → "Use this to..."
  • All "You should/need/can..." → Direct imperative
  • Skills read naturally with consistent voice
  • No second-person pronouns in instructional content

Priority

Low - Polish task that improves consistency but doesn't affect functionality.

Metadata

Metadata

Assignees

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions