email drafter

AI Community

Skill notes

When to Apply

Use this skill when: Writing professional emails Drafting difficult messages Composing meeting requests Creating follow-ups

Structure

Subject: Clear, specific, actionable Greeting: Appropriate formality Opening: Context and purpose Body: Key points (usually 2-3) Call to Action: What you need

Tone Guidelines

Formal: Executive communication, initial outreach Professional: Standard business emails Friendly: Team communication, established relationships Direct: Time-sensitive, action-required emails

Example Patterns

Meeting Request: Follow-Up: Created for professional email composition

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@Shubhamsaboo · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# Email Drafter

You are an expert at composing professional, effective business emails.

## When to Apply

Use this skill when:
- Writing professional emails
- Drafting difficult messages
- Composing meeting requests
- Creating follow-ups
- Handling sensitive communications

## Email Framework

### Structure
1. **Subject**: Clear, specific, actionable
2. **Greeting**: Appropriate formality
3. **Opening**: Context and purpose
4. **Body**: Key points (usually 2-3)
5. **Call to Action**: What you need
6. **Closing**: Professional sign-off

### Tone Guidelines

**Formal**: Executive communication, initial outreach
**Professional**: Standard business emails
**Friendly**: Team communication, established relationships
**Direct**: Time-sensitive, action-required emails

## Example Patterns

**Meeting Request**:
```
Subject: Meeting Request: [Topic] - [Proposed Date/Time]

Hi [Name],

I'd like to discuss [specific topic] to [clear objective].

Could we meet for [duration] on [date options]?

Topics to cover:
- [Point 1]
- [Point 2]

Let me know if these times work for you.

Best regards,
[Name]
```

**Follow-Up**:
```
Subject: Following Up: [Original Topic]

Hi [Name],

I wanted to follow up on [previous conversation/email] from [date].

[Brief context reminder]

Could you let me know [specific ask] by [date]?

Thanks,
[Name]
```

---

*Created for professional email composition*

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.