CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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冷启动外联序列/回复分流/域名预热

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

73%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, highly actionable instruction-only skill: the 7-step workflow has real validation checkpoints, decision gates, and a done-when checklist, and the reference list is clearly annotated. Its weaknesses are systematic repetition of the same boundary disclaimers across five sections and a warmup/throttle instruction that mandates numbers it never provides.

Suggestions

State the scope/boundary exclusions once (e.g., in the Scope guard) and drop the near-verbatim repeats in the intro, Skill Contract, instruction 6, Reference Materials, and Next Best Skill — this would cut substantial tokens without losing information.

Either supply concrete category-standard warmup ramp numbers (e.g., starting daily volume and step-up percentage per week) in instruction 4, or point to the reference file where they live, since the instruction currently requires numbers labeled Estimated that appear nowhere.

Add a minimal example of the sequence-map and reply-triage branch-table output shape so the 'Expected output' contract is verifiable, and confirm the ../../../ reference paths resolve in the published bundle.

DimensionReasoningScore

Conciseness

Mostly efficient — the instructions are dense with specifics — but the same scope/boundary disclaimer ("does not design consented B2C lifecycle flows… does not hold the consent record… does not compute the EQS") is repeated in the intro, Skill Contract, instruction 6, the Scope guard, Reference Materials, and Next Best Skill. This matches the 3 anchor (could be tightened) rather than 4, since the repetition is a systematic pattern rather than a minor instance of over-explanation.

3 / 5

Actionability

Concrete, executable guidance throughout: the typed profile weights ("S 0.35 · E 0.25 · N 0.15 · D 0.25"), the five reply routes with their next actions, the four enumerated CAN-SPAM elements, the Pass/Partial/Fail/Unknown/N/A scale, NEEDS_INPUT/UNDECIDED/NOT_SCORED states, and explicit memory paths. It stops short of 5 because instruction 4 mandates "category-standard ramp numbers labeled Estimated" without ever supplying or referencing actual numbers, and no example of the sequence map or branch-table output shape is given.

4 / 5

Workflow Clarity

Seven clearly sequenced numbered steps with explicit validation checkpoints (mark Unknown, return NEEDS_INPUT, emit no score on partial coverage), a "Done when" completion checklist, and a Decision Gates section distinguishing stop-and-ask from continue-silently conditions. This matches the 5 anchor's explicit validation steps, feedback loops, and checklist; it is not a destructive/batch operation, so no cap applies.

5 / 5

Progressive Disclosure

Good structure: the body is organized into scannable sections and closes with a Reference Materials list where each of the eight references gets a one-line annotation, all one level deep and clearly signaled. It falls short of 5 because no bundle files exist in the skill directory — every reference resolves to an external path (../../../references/, ../../../protocol/, or a sibling skill folder) with heterogeneous depths, so the navigation cannot be verified from the bundle itself.

4 / 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.

A strong description: explicit when-triggers in natural user phrasing, a precise enumeration of outputs, and unusually disciplined negative boundaries naming the sibling skills to route to instead. Its only flaws are the missing "cold email" synonym and a redundant duplicated Chinese summary tacked onto the end.

DimensionReasoningScore

Specificity

The description lists four concrete outputs — "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" — which is comprehensive coverage of the skill's scope. It clearly matches the 5 anchor rather than 4 because there are no meaningful gaps within that scope.

5 / 5

Completeness

It explicitly answers both questions: "Use when the user asks to…" gives concrete trigger phrases and "produces a multi-step outbound sequence with…" states the what. This matches the 5 anchor's pattern of explicit what-and-when with concrete triggers, not the 4 anchor where the when is only loosely specified.

5 / 5

Trigger Term Quality

Quoted natural trigger phrases like "build a B2B cold-outbound sequence", "design reply-triage branching", "plan a domain warmup / sending throttle", and "make my outbound CAN-SPAM / opt-in compliant" give good keyword coverage. It falls short of 5 because the most common user phrasing "cold email" is absent (only "cold-outbound" appears), and the duplicated trailing Chinese summary adds no new trigger terms.

4 / 5

Distinctiveness Conflict Risk

Three explicit negative boundary clauses — "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" — give it a clear niche with minimal conflict risk, matching the 5 anchor exactly.

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.

Validation — 13 / 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

Path

email/deliver/cold-outbound-sequencer/SKILL.md

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.