Skip to content
Back to skills

Email Client Document Request

ASecurity

Draft a controlled email requesting missing documents or clarifications from a client or counterparty.

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 30, 2026
devops

Works with

  • cli

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 30, 2026

npx -y skills add tomcustos/tcaml-framework --skill email-client-document-request --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Email Client Document Request?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Email Client Document Request
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tomcustos-email-client-document-request/badge)](https://www.skillsdirectory.com/skills/tomcustos-email-client-document-request)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
tcaml_version: "1.8.1"
document_type: "skill"
skill_type: "channel"
skill_id: "email-client-document-request"
title: "Email Client Document Request Channel Skill"
risk_area:
  - communication
human_review_required: true
final_decision_allowed: false
paid_source_boundary: false
source_access_required: "not_applicable"
private_configuration_required_for:
  - client-specific Implementation Profiles
  - private source configuration
  - evidence rules
  - MLRO escalation logic
---
# Email Client Document Request Channel Skill

## Purpose

Draft a controlled email requesting missing documents or clarifications from a client or counterparty.

## When to Use

Use when the AML workflow identifies missing information that can be requested externally without disclosing internal AML concerns.

## Required Inputs

- recipient name or role;
- requested document list;
- deadline or expected response time;
- approved tone/template;
- case identifier for internal logging only.

## Workflow

1. Confirm that the request is permitted for external communication.
2. Use neutral wording.
3. Request only necessary documents or clarifications.
4. Avoid explaining internal risk flags.
5. Do not mention suspicious activity, sanctions concern or regulatory reporting unless the implementation profile explicitly permits such wording.
6. Log the draft or sent message.

## Safe Message Content

- missing document list;
- document format requirements;
- deadline;
- contact channel;
- neutral administrative context.

## Agent Must Not

- disclose internal red flags;
- imply suspicion;
- discuss potential regulatory reporting;
- provide final onboarding outcome.

Files in this skill

  • SKILL.md1.6 KB
  • WORKFLOW.md384 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…