Skip to content
Back to skills

Messenger Client Document Request

ASecurity

Prepare short, controlled document requests for client-facing messaging channels.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • 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 messenger-client-document-request --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Messenger Client Document Request?

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

Security grade badge for Messenger Client Document Request
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tomcustos-messenger-client-document-request/badge)](https://www.skillsdirectory.com/skills/tomcustos-messenger-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: "messenger-client-document-request"
title: "Messenger 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
---
# Messenger Client Document Request Channel Skill

## Purpose

Prepare short, controlled document requests for client-facing messaging channels.

## When to Use

Use only where the implementation profile permits client communication through a messenger or chat tool.

## Required Inputs

- approved channel;
- recipient identity;
- requested item list;
- case reference for internal logging;
- approved language and tone.

## Workflow

1. Confirm the channel is approved.
2. Use short administrative wording.
3. Request documents or clarifications without AML-sensitive reasoning.
4. Avoid attachments unless permitted.
5. Log the sent message or draft.
6. Update follow-up status.

## Agent Must Not

- discuss internal screening results with the external party;
- mention suspicious activity considerations;
- send sensitive case notes;
- use informal wording that changes the meaning of the request.

Files in this skill

  • SKILL.md1.4 KB
  • WORKFLOW.md388 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…