CtrlK
BlogDocsLog inGet started
Tessl Logo

review-send-readiness

Use when deciding whether supplied outbound copy passes relevance, recipient-fit, evidence, eligibility, consent, policy, and operational gates.

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

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 tight, well-structured instruction-only skill with a clear sequenced workflow, explicit fail-closed validation, and a concrete output format. Its main gaps are minor gate-list repetition across sections and a thin example that lacks a worked PASS/BLOCK table.

Suggestions

Add one short worked example showing a filled Gate|PASS/BLOCK|Evidence|Reason|Remediation table so the output format is unambiguous.

Consider consolidating the gate enumeration so each gate appears authoritatively once (e.g., in Required inputs) with the Workflow and Output format referencing them, reducing repetition.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, with no padding explaining what copy or consent means, but the same gate list is enumerated across Required inputs, Workflow, and Output format rows, producing minor redundancy that keeps it just below a 5.

4 / 5

Actionability

Concrete, executable guidance is given throughout (specific block categories, an exact output table with named columns and rows, a fail-closed verdict rule), but the example invocation is only a one-line prompt with no worked PASS/BLOCK table, so it falls short of fully copy-paste-ready examples.

4 / 5

Workflow Clarity

The nine-step sequence is clearly ordered with explicit fail-closed validation (any failed/missing gate forces BLOCK, never override gates), a remediation feedback path, and a dedicated Quality check checklist, matching the top anchor for validation and feedback loops.

5 / 5

Progressive Disclosure

This single-purpose skill is under ~60 lines with no external references and is organized into well-signaled sections (Purpose, Required inputs, Workflow, Output format, Guardrails, Quality check, Example), satisfying the simple-skill exception for well-organized single-file content.

5 / 5

Total

18

/

20

Passed

Description

78%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 a clear niche and explicit trigger conditions with comprehensive gate enumeration. It falls just short of top marks because it describes one decision action rather than several distinct ones and omits the PASS/BLOCK verdict output from the description itself.

Suggestions

State the concrete output in the description, e.g. "Returns a fail-closed PASS or BLOCK verdict per gate" so the "what" is explicit.

Add a more natural trigger phrase such as "review an email or message before sending" alongside the gate-list phrasing.

DimensionReasoningScore

Specificity

The description enumerates several concrete gate categories ("relevance, recipient-fit, evidence, eligibility, consent, policy, and operational gates") rather than vague language, but it frames a single decision action rather than multiple distinct concrete actions, so it sits at 4 rather than 5.

4 / 5

Completeness

It answers both "what" (deciding whether copy passes the listed gates) and "when" ("Use when deciding whether supplied outbound copy passes...") with a concrete trigger, but the verdict output (fail-closed PASS/BLOCK) is not stated in the description itself, so it does not fully reach the explicit what+when of a 5.

4 / 5

Trigger Term Quality

The "Use when deciding whether supplied outbound copy passes..." phrasing plus gate names (eligibility, consent, policy) gives good keyword coverage a compliance user would recognize, but it misses the most natural colloquial phrasings (e.g., "review this email before sending"), keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

The outbound-copy send-readiness compliance niche with these specific gate triggers is highly specialized and clearly distinct from other skills, with minimal conflict risk.

5 / 5

Total

17

/

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
llaskin/AI-SDR-Skill-Pack
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.