CtrlK
BlogDocsLog inGet started
Tessl Logo

define-offer

Use when turning supplied product, service, or company evidence into an SDR offer brief before targeting or drafting outreach.

64

Quality

76%

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 ./skills/define-offer/SKILL.md
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 tightly written, well-structured instruction skill that avoids concept padding and gives a concrete workflow plus a copy-ready output template. The only real gap is a worked example of the filled-in brief to maximize actionability.

Suggestions

Add one short filled-in example of the Offer brief template (e.g. using the Northstar Relay fixture) so the output format is unambiguous.

Tighten the Quality check into an explicit pass/fail checklist to push workflow_clarity toward 5.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: no concept tutorials, no padding, each section (Purpose, Required inputs, Workflow, Output format, Guardrails, Quality check) earns its place.

5 / 5

Actionability

It provides a concrete, numbered workflow and a copy-ready markdown output template with explicit field labels (Fact/Inference/Missing, Excluded claims); minor gap is the absence of a worked example showing the template filled in.

4 / 5

Workflow Clarity

The five-step Workflow is clearly sequenced with a labeling/checkpoint step (step 2) and a closing Quality check section that acts as a validation gate; not a level-5 explicit validate->fix->retry feedback loop, and the brief is non-destructive so no cap applies.

4 / 5

Progressive Disclosure

Under 50 lines, single-purpose, no bundle files present; the content is well-organized into clear sections with no nested references, which per the simple-skill scoring note earns a 5.

5 / 5

Total

18

/

20

Passed

Description

68%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 clearly scopes a distinct SDR-offer-brief niche with a usable trigger clause, but it lists only one concrete action and could be sharpened with more specific verbs and synonyms. Strong but not exemplary.

Suggestions

List 2-3 concrete actions (e.g. 'extract offer facts, label proof status, produce a brief') to lift specificity toward 5.

Add a few more natural trigger synonyms (e.g. 'sales outreach', 'cold email', 'sales development') to broaden keyword coverage.

DimensionReasoningScore

Specificity

Names the domain ('turning supplied product, service, or company evidence into an SDR offer brief') and one concrete action ('brief before targeting or drafting outreach'), but does not enumerate multiple distinct concrete actions the way a 4-5 anchor would.

3 / 5

Completeness

The 'Use when...' clause gives a clear trigger and the what ('turning evidence into an SDR offer brief') is present; both are present but the 'when' could be more explicitly tied to concrete trigger phrases, matching the 4 anchor rather than 5.

4 / 5

Trigger Term Quality

'product, service, or company evidence', 'SDR offer brief', 'targeting or drafting outreach' are natural terms an SDR-oriented user would say; missing a few common synonyms (e.g. 'sales outreach', 'cold email') keeps it just below 5.

4 / 5

Distinctiveness Conflict Risk

The narrow SDR-offer-brief niche is mostly distinct with minimal overlap risk against general outreach skills; minor overlap with general 'sales research' skills keeps it at 4 rather than 5.

4 / 5

Total

15

/

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.