Skip to content

Comments

Fix terminology: third person → passive voice#133

Closed
FauxReal9999 wants to merge 1 commit intoEveryInc:mainfrom
FauxReal9999:fix/passive-voice-terminology
Closed

Fix terminology: third person → passive voice#133
FauxReal9999 wants to merge 1 commit intoEveryInc:mainfrom
FauxReal9999:fix/passive-voice-terminology

Conversation

@FauxReal9999
Copy link

Summary

  • Corrects terminology throughout the documentation: "third person" → "passive voice"
  • The example "This skill should be used when..." is passive voice, not third person
  • Third person would be "The developer uses this skill when..."

Files Changed

  • CLAUDE.md - Skill compliance checklist
  • CHANGELOG.md - Historical reference
  • skills/create-agent-skills/ - SKILL.md, references, and workflows (7 files)

🤖 Generated with Claude Code

The example "This skill should be used when..." is passive voice,
not third person. Third person would be "The developer uses this
skill when..." - this change corrects the terminology throughout
the documentation.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@kieranklaassen kieranklaassen added the documentation Improvements or additions to documentation label Feb 8, 2026
@kieranklaassen
Copy link
Collaborator

Thanks for the thoughtful PR! You're right that "third person" was imprecise terminology.

However, after checking the official Anthropic skill docs, neither "third person" nor "passive voice" is mandated. The official examples use direct/imperative style:

  • "Explains code with visual diagrams and analogies. Use when..."
  • "Deploy the application to production"
  • "Research a topic thoroughly"

The spec just says: describe what it does and when to use it.

We'll update our docs to match the official spec rather than prescribing a specific voice. Thanks for flagging this inconsistency!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants