---
name: email-account-and-signature-management
description: "Project-level email account selection plus a deterministic signature (and default composition style) pulled from a real sent email, dual-written into admin\\EMAIL_SIGNATURE.md and inline in admin\\AGENT_INSTRUCTIONS.md. Use when a person asks to install or apply \"Email Account Awareness & Signature Management\" (FTR-42) in a project, or when working in a project that has it installed."
---

# Email Account Awareness & Signature Management (FTR-42, version 1.0)

> Generated from library record FTR-42 version 1.0, publish 20261102a. Review status: unreviewed. The complete specification is in references/spec.md and is the authority; this file is the operating procedure drawn from it.

## What this does

Project-level email account selection plus a deterministic signature (and default composition style) pulled from a real sent email, dual-written into admin\EMAIL_SIGNATURE.md and inline in admin\AGENT_INSTRUCTIONS.md

## When to use this skill

- A person asks to install, apply or update "Email Account Awareness & Signature Management" (FTR-42) in a project.
- A project's agent instructions list email-account-and-signature-management as installed and the task touches what it covers.
- No other feature is required first.

## Install procedure

Steps run in order. Assess comes first, every question in the Ask step is answered by the person before anything is written, and every write merges additively into the existing project files (read the file first, update an existing section in place, never overwrite).

### Assess first
- Confirm the IMAP/SMTP integration is actually live: run the standard "list all my email accounts" check and at least one successful read. If it isn't, stop here and point the person at the Prerequisite above -- this feature has nothing to build on without it.
- Check `admin\AGENT_INSTRUCTIONS.md` for an existing EMAIL CAPABILITY note or a signature section from a prior install; if present, confirm and skip re-asking what's already answered.
- Note how many email accounts are configured on the machine.

### Ask, only if needed
- If more than one account is configured: "Which email account should [Project Name] use when sending email? [list configured account identities]" -- never assumed or guessed. If only one account exists, skip this question and just record it.
- Nothing else needs asking before the signature step below -- that step is itself the confirmation mechanism, not a separate question asked in the abstract.

### Write

The full Write payload is in references/write-payload.md. It is applied exactly as written, with the merge rule above.

### Confirm
Confirm: Email Account Awareness & Signature Management is installed -- `admin\AGENT_INSTRUCTIONS.md` names which account this project sends as (if more than one was configured), the signature (and detected default font/style) is written both into `admin\EMAIL_SIGNATURE.md` and inline in `admin\AGENT_INSTRUCTIONS.md`, and composed email defaults to HTML, drafts-first, unless the person says otherwise. Want to install another, or is that everything for now?

## Other sections in the specification

- Prerequisite (hard requirement, not a catalog dependency)
- What this doesn't cover

These are in references/spec.md.

## Files in this skill

- references/spec.md: the complete specification, unabridged.
- references/write-payload.md: the Write step on its own.