adapt-channel

Use when rewriting supplied factual outbound copy into channel-specific offline drafts without changing its evidenced meaning.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%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 content is concise, well-structured, and assumes Claude's intelligence while providing a clearly sequenced workflow with validation gates and feedback handling. Its only weakness is the absence of a concrete worked example showing the actual per-channel draft output, which keeps actionability just below full marks.

Suggestions

Add one short worked example showing the input message and the resulting per-channel DRAFT FOR HUMAN REVIEW sections to make the output format copy-paste-ready.

Optionally show the exact return shape for the drafting-gate status line (e.g. 'ELIGIBLE | no opt-out') so Claude reproduces it verbatim.

Consider a tiny inline template skeleton for one channel (e.g. email) to lift actionability from 4 to 5.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: it states rules and gate behaviors without explaining what a channel, opt-out, or evidence ledger is, and every section earns its place.	5 / 5
Actionability	It gives concrete, executable guidance — explicit gate returns ('STOP', 'NEEDS VERIFICATION'), per-channel rewrite shapes, and a prohibited-claims list — but is instruction-only with no worked example output, leaving minor gaps versus copy-paste-ready material.	4 / 5
Workflow Clarity	The numbered workflow is clearly sequenced with explicit validation checkpoints (gate checks in step 1, 'NEEDS VERIFICATION — NOT READY TO SEND' marking in step 3, evidence tracing in step 6) and a feedback path where missing data does not suppress offline drafts.	5 / 5
Progressive Disclosure	The skill is a compact, well-sectioned overview (Purpose, Required inputs, Workflow, Output format, Guardrails, Quality check, Example invocation) with no bundle files and no nested references, so structure alone satisfies the simple-skill exception.	5 / 5
	Total	19 / 20 Passed

Description

76%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 cleanly states both what the skill does and when to use it with an explicit 'Use when' trigger, scoring well on completeness. It loses points on trigger-term quality (missing natural channel synonyms like 'email' or 'LinkedIn') and minor specificity gaps around which channels are covered.

Suggestions

Add concrete trigger keywords users would naturally say, such as 'email', 'LinkedIn', 'phone', or 'voicemail' drafts, to improve trigger term quality.

Mention the specific channels supported (email, LinkedIn, phone, voicemail) in the description to lift specificity from 4 to 5.

Consider a phrasing tweak like 'Use when adapting verified outbound copy into email, LinkedIn, phone, or voicemail drafts' to sharpen distinctiveness.

Dimension	Reasoning	Score
Specificity	Describes the concrete action ('rewriting supplied factual outbound copy into channel-specific offline drafts') and the key constraint ('without changing its evidenced meaning'), but does not enumerate the specific channels or the multiple rewrite variants it supports, leaving minor coverage gaps.	4 / 5
Completeness	It explicitly answers both 'what' (rewrite supplied copy into channel-specific offline drafts preserving evidenced meaning) and 'when' ('Use when rewriting supplied factual outbound copy...'), with a concrete trigger clause.	5 / 5
Trigger Term Quality	It opens with 'Use when' and references 'channel-specific offline drafts' and 'outbound copy', but lacks the natural synonyms a user would say (e.g. 'email', 'LinkedIn', 'voicemail', 'rewrite', 'adapt'), so common variations are missing.	3 / 5
Distinctiveness Conflict Risk	The niche (channel-specific offline drafting under eligibility/opt-out gates preserving evidenced meaning) is fairly distinct, though 'rewriting copy' could overlap with general copywriting or editing skills, leaving minor conflict risk.	4 / 5
	Total	16 / 20 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: llaskin/AI-SDR-Skill-Pack
Path: skills/adapt-channel/SKILL.md
Commit: 56ebfd3

Reviewed: ~22 hours 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.