CtrlK
BlogDocsLog inGet started
Tessl Logo

cold-outbound-sequencer

Use when the user asks to "build a B2B cold-outbound sequence", "design reply-triage branching", "plan a domain warmup / sending throttle", or "make my outbound CAN-SPAM / opt-in compliant"; produces a multi-step outbound sequence with reply-triage branches (positive / objection / referral / not-now / opt-out), a warmup + send-throttle ramp schedule, jurisdiction opt-in/CAN-SPAM guardrails (guidance, not legal advice), and a SEND S-dimension read. Not for B2C lifecycle flows — use email-sequence-designer; not for the consent record — use consent-registry; not for computing EQS — use email-quality-auditor. B2B冷启动外联序列/回复分流/域名预热

66

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is well-structured and highly actionable with explicit gates and a reference section, but it carries meaningful repetition of the compliance caveat and scope boundaries that a tighter pass would consolidate.

Suggestions

State the 'guidance, not legal advice; confirm with counsel' caveat once (e.g. in Instructions) and reference it rather than repeating it across the intro, Scope guard, and Decision Gates.

Consolidate the sibling-skill boundaries into a single Scope guard or Reference Materials entry; the consent-registry/auditor handoff is currently restated in five places.

Add one short rendered example of the expected output (a sample sequence-map row set or reply-triage branch table) to lift actionability from concrete-directive to copy-paste-ready.

DimensionReasoningScore

Conciseness

The body is information-dense and avoids explaining basics Claude already knows, but it repeats the same scope boundaries several times — 'guidance, not legal advice' appears ~4 times and the consent-registry/auditor handoff and 'Not for ...' sibling boundaries are restated across Skill Contract, Scope guard, Instructions, Reference Materials, and Next Best Skill, so it could be tightened.

3 / 5

Actionability

Each of the seven numbered steps gives concrete directives — e.g. 'build a branch table that routes every reply type ... positive (hand to sales / book), objection (rebuttal branch), referral (re-route to named contact, log the referral), not-now (defer + re-enroll date), and opt-out (suppress immediately)' — with specific profile numbers and a Pass/Partial/Fail/Unknown/N/A rubric; the main gap is the absence of a rendered example artifact.

4 / 5

Workflow Clarity

A clear seven-step sequence is backed by explicit validation checkpoints (NEEDS_INPUT gating on missing consent basis or partial S coverage), a Done-when checklist, and Stop/Continue decision gates; it falls short of 5 only because the error-recovery feedback loop is handed off to the auditor rather than contained as a numbered step here.

4 / 5

Progressive Disclosure

The SKILL.md is a lean overview with a dedicated, labeled 'Reference Materials' section pointing one level deep to send-benchmark.md, skill-contract.md, CONNECTORS.md, SECURITY.md, and sibling skills, each with a one-line description — content is appropriately externalized and navigation is easy.

5 / 5

Total

16

/

20

Passed

Description

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

The description is strong: it pairs a concrete 'Use when' trigger list with an explicit deliverable inventory and clear sibling-skill boundaries. The only minor gap is synonym coverage among the trigger terms.

DimensionReasoningScore

Specificity

It enumerates multiple concrete deliverables — 'a multi-step outbound sequence with reply-triage branches (positive / objection / referral / not-now / opt-out), a warmup + send-throttle ramp schedule, jurisdiction opt-in/CAN-SPAM guardrails ... and a SEND S-dimension read' — with comprehensive coverage and no real gaps.

5 / 5

Completeness

It explicitly answers both 'what' (the produced sequence map, triage branches, ramp schedule, guardrails, S-read) and 'when' via a 'Use when the user asks to ...' clause with four concrete trigger phrases, matching the anchor-5 example.

5 / 5

Trigger Term Quality

Four natural quoted trigger phrases ('build a B2B cold-outbound sequence', 'design reply-triage branching', 'plan a domain warmup / sending throttle', 'make my outbound CAN-SPAM / opt-in compliant') give good keyword coverage, but common synonyms like 'cold email', 'prospecting cadence', or 'email sequence' are not included.

4 / 5

Distinctiveness Conflict Risk

A clear B2B cold-outbound niche plus explicit 'Not for B2C lifecycle flows — use email-sequence-designer; not for the consent record — use consent-registry; not for computing EQS — use email-quality-auditor' disambiguation gives minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 25 suspicious

Warning

Total

13

/

16

Passed

Repository
aaron-he-zhu/aaron-marketing-skills
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.