Claude-skill-registry email

Read and manage internal email messages between project roles

install

source · Clone the upstream repo

git clone https://github.com/majiayu000/claude-skill-registry

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/email" ~/.claude/skills/majiayu000-claude-skill-registry-email && rm -rf "$T"

manifest: skills/data/email/SKILL.md

source content

Internal Email System

This project uses an internal email system for communication between roles (Manager, Developer, Release Manager, Tester, etc.).

Directory Structure

Each role has its own email folder under

claude/{role}/email/

Inbox:
```
claude/{role}/email/inbox/
```
Inbox Archive:
```
claude/{role}/email/inbox-archive/
```
Sent:
```
claude/{role}/email/sent/
```
Outbox (pending delivery):
```
claude/{role}/email/outbox/
```

Current roles:

```
manager/email/
```
```
developer/email/
```
```
release-manager/email/
```
```
security-analyst/email/
```
```
tester/email/
```
(future)

Reading Email

First, determine your role by checking CLAUDE.local.md

List all files in your inbox directory:

ls -lt claude/{role}/email/inbox/

You always have permission to read claude/{role}/email/inbox/ and all files within. Do not request permission to read this directory.
Read each message file to display contents
Summarize messages in a table format showing:
- Date
- Type (Task Assignment, Completion Report, Reminder, Question, etc.)
- Subject/Summary
- Action needed (if any)

Processing Email

For completion reports:

Review the report
If work is verified complete, archive to
```
email/inbox-archive/
```
Update INDEX.md if needed

For reminders:

Keep in inbox until the remind-on date
Take action when due

For questions:

Respond by creating a file in
```
email/sent/
```
and copying to the sender's
```
email/inbox/
```

Sending Email

Create message file in your
```
email/sent/
```
folder with naming convention:
```
YYYY-MM-DD-HHMM-{type}-{brief-description}.md
```

Copy the file to the recipient's inbox:

cp claude/{your-role}/email/sent/{filename}.md claude/{recipient-role}/email/inbox/

Email Templates

Task Assignment:

# Task Assignment: <Title>

**Date:** YYYY-MM-DD HH:MM
**Project:** <project-name>
**Priority:** High | Medium | Low
**Estimated Effort:** X-Y hours

## Task
<Description>

## What to Do
1. Step 1
2. Step 2

## Success Criteria
- [ ] Criterion 1
- [ ] Criterion 2

---
**{Role}**

Completion Report:

# Task Completed: <Title>

**Date:** YYYY-MM-DD
**From:** {Role}
**Type:** Completion Report

## Status: COMPLETED

## Summary
<What was done>

## Branch
**Branch:** `branch-name`
**Commit:** `hash`

## Changes
<Files modified>

---
**{Role}**

Checking for Undelivered Mail

Also check outbox folders for messages waiting to be delivered:

ls claude/*/email/outbox/

If messages exist, they need to be moved to the recipient's

email/inbox/

Related Skills

communication - Communication guidelines and message templates
projects - Query project status (tasks often arrive via email)