twilio-compliance-traffic

Rules you must follow for Twilio messaging and voice traffic. Covers TCPA (consent tiers, quiet hours, DNC), GDPR (EU consent, right to deletion), PCI DSS (payment recording, Pay verb), HIPAA (BAA, PHI), FDCPA (debt collection limits), CAN-SPAM, WhatsApp policies, SHAKEN/STIR, and consent management patterns. Use this skill proactively when developers have working traffic to ensure they follow the rules.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./plugins/twilio-developer-kit/skills/twilio-compliance-traffic/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A thorough, highly actionable compliance reference with executable code, concrete numeric thresholds, and a useful CANNOT section. Its weaknesses are length/verbosity, the absence of validation checkpoints in send workflows, and a monolithic single-file structure with no progressive disclosure to bundle references.

Suggestions

Move the deeper per-regime code and tables (e.g., FDCPA tracking, PCI Pay-verb integration, HIPAA notification matrices) into reference files and keep SKILL.md as an overview with one-level-deep links, improving progressive disclosure and conciseness.

Add an explicit validation/verification checkpoint for batch sends — e.g., a pre-send compliance checklist (consent verified, quiet-hours checked, DNC scrubbed, template approved) with a 'only send when all pass' gate.

Trim motivational framing ('Compliance failures block sends, get numbers suspended...') and consolidate repeated cross-skill references into the Next Steps section.

Dimension	Reasoning	Score
Conciseness	Most content is genuinely non-obvious regulatory specificity (8am-9pm quiet hours, 7-in-7 FDCPA limit, 400-day log retention, public-shortlink carrier filtering) that earns its tokens, but the ~245-line body includes motivational fluff ('Compliance failures block sends...') and some repetitive cross-references that could be trimmed.	2 / 3
Actionability	Executable Python examples (pausing recordings, the <Pay> verb, an FDCPA can_attempt_call guard, Mini-Miranda IVR), a concrete consent-record schema with typed fields, and do/don't tables give copy-paste-ready, specific guidance.	3 / 3
Workflow Clarity	Content is organized by regulation and a lifecycle sequence is named, but there are no explicit validation/verification checkpoints for batch or send operations, and the 'apply rule → send' path has no feedback loop, capping clarity at 2.	2 / 3
Progressive Disclosure	The body is well-sectioned with clear headers and tables, but at ~245 lines all nine regimes live inline in a single monolithic SKILL.md with no bundle files (references/scripts/assets absent), so content that could be split out is kept inline.	2 / 3
	Total	9 / 12 Passed

Description

90%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-scoped description that names specific regulatory regimes and includes an explicit 'Use when' trigger, distinguished clearly from related skills. The only weakness is second-person voice ('you must follow'), which lowers its specificity score under the rubric's voice penalty.

Suggestions

Rewrite in third person to avoid the specificity penalty — e.g., 'Rules to follow for Twilio messaging and voice traffic' instead of 'Rules you must follow'.

Lead with the skill's action verb so capabilities read as concrete actions rather than topics covered (e.g., 'Applies TCPA/GDPR/PCI/HIPAA compliance rules to live Twilio messaging and voice traffic').

Dimension	Reasoning	Score
Specificity	It lists many concrete regulatory areas and subtopics ('consent tiers, quiet hours, DNC', 'payment recording, Pay verb', 'BAA, PHI', 'debt collection limits'), which would normally score 3, but the second-person phrasing 'Rules you must follow' triggers the -1 specificity penalty per the rubric guidelines.	2 / 3
Completeness	It answers 'what' ('Rules you must follow for Twilio messaging and voice traffic. Covers...') and 'when' with an explicit trigger clause ('Use this skill proactively when developers have working traffic to ensure they follow the rules'), satisfying the highest anchor.	3 / 3
Trigger Term Quality	Strong coverage of terms a compliance-focused developer would naturally say: TCPA, GDPR, PCI DSS, HIPAA, FDCPA, CAN-SPAM, SHAKEN/STIR, consent, and compliance, with natural phrasing variations rather than only internal jargon.	3 / 3
Distinctiveness Conflict Risk	It carves a clear niche — ongoing compliance rules for live Twilio traffic — distinct from sibling skills like onboarding, numbers/senders, and security-hardening, making mis-triggering unlikely.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: openai/plugins
Path: plugins/twilio-developer-kit/skills/twilio-compliance-traffic/SKILL.md
Commit: 11c74d6

Reviewed: 17 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.