examples/simple-greeter-plugin/skills/professional-greeting/SKILL.md
# Professional Greeting When the user asks you to help write a greeting (email, message, letter opening), use this skill to ensure professional and appropriate tone. ## Context Detection First, determine: 1. **Relationship**: Is this for a colleague, client, superior, or someone you don't know? 2. **Formality level**: Professional formal, professional casual, or friendly professional? 3. **Purpose**: Introduction, follow-up, request, thank you, or general correspondence? 4. **Cultural context
npx skillsauth add obra/superpowers-developing-for-claude-code examples/simple-greeter-plugin/skills/professional-greetingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
When the user asks you to help write a greeting (email, message, letter opening), use this skill to ensure professional and appropriate tone.
First, determine:
Only use time-based greetings ("Good morning/afternoon") when:
Provide:
User: "Help me write an email to a new client I'm meeting next week"
Output:
Recommended greeting: "Hello [Client Name],"
Rationale: This strikes a balance between professional and approachable for a first-time client interaction. It's formal enough to show respect but not overly stiff.
Alternative: "Dear [Client Name]," if you want to err on the more formal side
Opening sentence suggestion: "Thank you for taking the time to meet with me next week. I'm looking forward to discussing [topic]."
tools
Use when working with Claude Code CLI, plugins, hooks, MCP servers, skills, configuration, or any Claude Code feature - provides comprehensive official documentation for all aspects of Claude Code
tools
Use when working on Claude Code plugins (creating, modifying, testing, releasing, or maintaining) - provides streamlined workflows, patterns, and examples for the complete plugin lifecycle
tools
Use when demonstrating plugin workflow features - shows how skills can guide multi-step processes
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.