CtrlK
BlogDocsLog inGet started
Tessl Logo

twilio-security-hardening

Secure Twilio applications against common attacks. Covers credential management (API keys vs auth tokens), request validation (webhook signature verification), PCI DSS compliance, HIPAA account requirements, SMS pumping prevention, geo-permissions, and account isolation patterns. Use this skill when developers are building or deploying Twilio apps.

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

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

A well-structured, actionable hardening guide with executable examples, clear irreversible-operation warnings, and good cross-skill navigation. It could tighten a few explanatory passages and add validation feedback loops for the more complex destructive operations.

Suggestions

Trim contextual framing sentences (e.g. 'Verify that webhook requests actually come from Twilio — not spoofed by attackers') where the heading already conveys intent.

Add an explicit validate-fix-retry feedback loop for webhook signature verification (e.g. what to check when validation fails in production).

Provide a second executable webhook-validation snippet (e.g. Python) or a concrete console/API step for the HIPAA and best-practices sections that currently read as checklists.

DimensionReasoningScore

Conciseness

The body is dense and mostly assumes Claude's competence, with explanations focused on Twilio-specific domain facts (PCI mode irreversibility, Auth Token rotation invalidating API keys) rather than generic concepts; a few framing sentences could be trimmed.

4 / 5

Actionability

Executable code is provided for webhook validation (Node.js), recording pause (Python), and the <Pay> verb, plus concrete console URLs and a numbered rotation workflow; some advisory sections (HIPAA checklist, best practices) lack executable specifics.

4 / 5

Workflow Clarity

The credential rotation workflow is clearly sequenced with a verification checkpoint ('verify all traffic uses the new credential' before deleting the old key), and irreversible operations (PCI mode, Auth Token rotation) are flagged; minor validation gaps remain in other sections.

4 / 5

Progressive Disclosure

Content is well-organized into themed sections and delegates detail to sibling skills via clearly signaled one-level references ('Docs: See X', 'Next Steps'); no bundle files exist, and the inline body is somewhat long but appropriately split across the Twilio skill family.

4 / 5

Total

16

/

20

Passed

Description

88%Weight 40%Scale 1-5

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, specific description that names concrete capabilities and includes an explicit use-when trigger. Minor improvements could expand natural trigger-term variations and sharpen the boundary against sibling Twilio skills.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions—'credential management (API keys vs auth tokens)', 'request validation (webhook signature verification)', 'SMS pumping prevention', 'geo-permissions', and 'account isolation patterns'—giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

It clearly states what the skill does (lists the security domains covered) and provides an explicit 'Use this skill when developers are building or deploying Twilio apps' trigger, satisfying both what and when with concrete phrasing.

5 / 5

Trigger Term Quality

Natural terms like 'Twilio applications', 'Twilio apps', 'building or deploying', and 'attacks' give good coverage, but a few common user phrases (e.g. 'Twilio webhook', 'Twilio credentials', 'Twilio fraud') are not surfaced as explicit triggers.

4 / 5

Distinctiveness Conflict Risk

The 'Twilio' niche is clear and distinct, but the broad security framing has minor overlap risk with closely related sibling skills (e.g. credential setup and webhook architecture) referenced in the body.

4 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
Reviewed

Table of Contents

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.