CtrlK
BlogDocsLog inGet started
Tessl Logo

twilio-marketing-promotions-advisor

Planning skill for marketing and promotional messaging. Qualifies the developer's campaign needs across channel selection, compliance, audience segmentation, and delivery tracking to recommend the right Twilio messaging architecture. Handles both "set up a promotional SMS campaign" and "build a multi-channel engagement pipeline with Segment integration."

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/twilio-developer-kit/skills/twilio-marketing-promotions-advisor/SKILL.md
SKILL.md
Quality
Evals
Security

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.

The body is highly actionable with specific Twilio domain guidance and a clear qualification workflow, but it is a monolithic file with some redundancy and only implicit validation checkpoints rather than explicit feedback loops.

Suggestions

Add explicit validation checkpoints in the workflow (e.g., "Before recommending a Level, confirm compliance readiness: approved templates? A2P registration complete?") to convert implicit gating into verify-then-proceed steps.

Deduplicate the skill-install lists by defining them once and referencing them, or move the channel-mix matrix and per-channel compliance detail into a bundled reference file to reduce inline length.

Tighten the channel descriptions in Step 2, which currently repeat rationale that could be condensed without losing the actionable thresholds.

DimensionReasoningScore

Conciseness

The body is mostly lean domain-specific fact (A2P timelines, MPS limits, 429 backoff) but repeats the skill-install list across Step 3 and the Output Format block and includes verbose channel descriptions that could be tightened, fitting the anchor for mostly efficient with some unnecessary content.

2 / 3

Actionability

It gives concrete, copy-paste-ready guidance — exact skill IDs (twilio-messaging-services, twilio-compliance-traffic), precise volume thresholds (<1,000 / 100,000+), specific MPS rates, and exact compliance steps (Register Brand → Create Campaign → Link to Messaging Service) — and per scoring notes code absence is not penalized for an instruction-only skill.

3 / 3

Workflow Clarity

Steps 1-4 are clearly sequenced with a checklist-style Output Format, but validation is implicit gating ("This is non-negotiable", mode-based branching) rather than explicit verify-then-fix feedback loops, fitting the anchor for steps listed with checkpoint gaps.

2 / 3

Progressive Disclosure

It is a single well-organized 172-line file with no bundle references and all detail inline; the under-50-line section-only exemption does not apply, and content such as the channel matrix and compliance tables could be split out, fitting the anchor for content that should be separate being inline.

2 / 3

Total

9

/

12

Passed

Description

67%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.

The description is specific and well-scoped to a distinct Twilio marketing-advisory niche, but it lacks an explicit "Use when..." trigger clause and its keywords skew architectural, limiting trigger-term coverage and completeness.

Suggestions

Add an explicit "Use when..." clause enumerating natural user phrases (e.g., "Use when a developer asks to set up a promotional SMS campaign, send bulk marketing messages, or build a multi-channel engagement pipeline").

Broaden trigger terms with common natural variants such as "bulk SMS", "mass email", "drip campaign", and "marketing campaign" rather than architectural phrasing.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Qualifies the developer's campaign needs across channel selection, compliance, audience segmentation, and delivery tracking to recommend the right Twilio messaging architecture" — matching the anchor for several specific concrete actions rather than a single named domain.

3 / 3

Completeness

It clearly answers "what" (qualify needs, recommend architecture) but provides no explicit "Use when..." trigger clause — only implied trigger sense via the two example phrases — so per the guideline a missing explicit trigger guidance caps completeness at 2.

2 / 3

Trigger Term Quality

It includes relevant terms ("marketing and promotional messaging", "promotional SMS campaign") but leans architectural ("multi-channel engagement pipeline", "messaging architecture") and omits common natural variants like "bulk SMS" or "campaign", fitting the anchor for some relevant keywords missing common variations.

2 / 3

Distinctiveness Conflict Risk

The Twilio marketing/promotions niche is clearly scoped with distinct example triggers ("set up a promotional SMS campaign", "build a multi-channel engagement pipeline with Segment integration"), making it unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

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.