Add /send-email skill wrapping sop-email-send #232

Closed
opened 2026-04-03 19:04:43 +00:00 by forgejo_admin · 0 comments
Contributor

Type

Feature

Lineage

Standalone — part of email architecture overhaul (2026-04-03). The SOP (sop-email-send) and architecture doc (arch-email) already exist in pal-e-docs. This skill is the agent-facing trigger that loads and follows them.

Repo

forgejo_admin/claude-custom

User Story

As an agent (Ava, Penny),
I want a /send-email skill that loads the email SOP and walks through it,
So that I can compose and send branded emails without missing safety gates.

Context

The email send workflow has hard safety gates (test email, phone approval, double approval for contracts). These are documented in sop-email-send in pal-e-docs. The skill is a thin wrapper that ensures agents find and follow the SOP.

File Targets

Files to create:

  • skills/send-email/SKILL.md — skill frontmatter + instructions referencing sop-email-send and arch-email

Acceptance Criteria

  • /send-email skill loads and directs agent to read sop-email-send
  • Quick reference includes layouts, test email address, endpoint
  • Red flags section catches common violation patterns

Test Expectations

  • Skill file has valid YAML frontmatter with name and description
  • Description starts with "Use when"

Constraints

  • Under 200 words — heavy content lives in the SOP note, not the skill
  • Must reference sop-email-send and arch-email via MCP calls

Checklist

  • PR opened
  • No unrelated changes
  • sop-email-send — the SOP this skill wraps
  • arch-email — architecture reference
  • project-westside-basketball — parent project
### Type Feature ### Lineage Standalone — part of email architecture overhaul (2026-04-03). The SOP (`sop-email-send`) and architecture doc (`arch-email`) already exist in pal-e-docs. This skill is the agent-facing trigger that loads and follows them. ### Repo `forgejo_admin/claude-custom` ### User Story As an agent (Ava, Penny), I want a `/send-email` skill that loads the email SOP and walks through it, So that I can compose and send branded emails without missing safety gates. ### Context The email send workflow has hard safety gates (test email, phone approval, double approval for contracts). These are documented in `sop-email-send` in pal-e-docs. The skill is a thin wrapper that ensures agents find and follow the SOP. ### File Targets Files to create: - `skills/send-email/SKILL.md` — skill frontmatter + instructions referencing `sop-email-send` and `arch-email` ### Acceptance Criteria - [ ] `/send-email` skill loads and directs agent to read `sop-email-send` - [ ] Quick reference includes layouts, test email address, endpoint - [ ] Red flags section catches common violation patterns ### Test Expectations - [ ] Skill file has valid YAML frontmatter with name and description - [ ] Description starts with "Use when" ### Constraints - Under 200 words — heavy content lives in the SOP note, not the skill - Must reference `sop-email-send` and `arch-email` via MCP calls ### Checklist - [ ] PR opened - [ ] No unrelated changes ### Related - `sop-email-send` — the SOP this skill wraps - `arch-email` — architecture reference - `project-westside-basketball` — parent project
forgejo_admin 2026-04-03 19:07:09 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ldraney/claude-custom#232
No description provided.