professional-greeting

Included with Lifetime

$97 forever

# Professional Greeting

General

What this skill does

# 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**: Any specific cultural considerations mentioned?

## Greeting Selection Rules

### For First Contact or Formal Situations
- Unknown recipient or very formal: "Dear [Name/Title],"
- Professional but less formal: "Hello [Name],"
- Multiple recipients: "Dear Team," or "Hello everyone,"

### For Established Professional Relationships
- Colleague (casual): "Hi [Name],"
- Colleague (formal): "Hello [Name],"
- Regular client: "Hi [Name]," or "Hello [Name],"

### For Follow-ups Within Same Thread
- Quick follow-up: "Thanks for the quick response," or "[Name],"
- Continuing discussion: "Thanks," or just continue the conversation

## Time-Based Greetings

Only use time-based greetings ("Good morning/afternoon") when:
- You know the recipient's timezone
- The message is truly time-sensitive
- It's a live conversation, not async email

## What to Avoid

- Never use "To whom it may concern" (too impersonal)
- Avoid "Hey" in formal contexts
- Don't use "Dear Sir/Madam" (outdated and assumes gender)
- Skip exclamation marks in initial professional contact
- Avoid overly casual openers like "What's up" or "Yo" in professional settings

## Output Format

Provide:
1. **Recommended greeting**: The specific greeting text
2. **Rationale**: Brief explanation of why this greeting fits
3. **Alternative**: One backup option if they want to adjust formality
4. **Opening sentence suggestion**: A natural first sentence that flows from the greeting

## Example

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]."
```

## Special Cases

- **Bad news**: Use formal greeting, avoid cheerfulness
- **Apology**: More formal than usual previous communication
- **Celebration**: Match the enthusiasm level to your relationship
- **Request from someone senior**: Lean formal
- **Thank you note**: Can be slightly warmer than typical communication

## Process

1. Ask clarifying questions if context is unclear
2. Provide your recommendation with rationale
3. Offer to adjust if they want more/less formality
4. Draft the full opening (greeting + first 1-2 sentences) for their approval

Files: 1

Size: 3.0 KB

Complexity: 4/100

Category: General

Source: https://github.com/obra/superpowers-developing-for-claude-code/tree/main/examples/simple-greeter-plugin/skills/professional-greeting

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts