CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pitch-position

Produce a complete positioning document using the Dunford framework — competitive alternatives, unique attributes, value, best-fit customer, market category, positioning statement, and tagline. Use when asked to "write our positioning", "define our value prop", "positioning statement", "what market are we in", "how do we position against X", "what's our tagline", or "write our messaging foundation".

Quality

88%

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

78%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-sequenced 8-step positioning framework that is unusually actionable for an instruction-only skill — fill-in templates, concrete rules, and named quality tests at every step. The main weaknesses are the dangling docs/output-kit.md reference and unshipped /atlas-report dependency that break the delivery path, and the absence of validation checkpoints before Step 6.

Suggestions

Ship or inline the output format: Step 8's 'Follow the output format defined in docs/output-kit.md' references a file absent from the bundle — either include docs/output-kit.md or inline the essential formatting rules so the delivery step is self-contained.

Add explicit checkpoints between Steps 1–5 (e.g., a minimum count of competitive alternatives, a prune gate for attributes) so weaknesses surface before the positioning statement is drafted, mirroring the validate-and-fix pattern already present in Step 6.

Trim the repeated decorative separator lines across the eight template blocks and a few rationale sentences ('This is the most important step. Do not skip it or rush it.') to reduce token cost without losing clarity.

DimensionReasoningScore

Conciseness

The body is lean with no explanations of concepts Claude already knows — every step is a fill-in template plus a pruning rule. Minor trimmable padding remains: decorative '─────' separator lines repeated across eight templates and editorial lines like 'This is the most important step. Do not skip it or rush it.' — anchor 4 ('efficient; minor instances of over-explanation that could be trimmed') rather than 5.

4 / 5

Actionability

Every step ships a copy-ready fill-in template with placeholder fields, plus concrete rules and examples: '7 words or fewer', 'No gerunds… no adjectives that mean nothing ("powerful", "seamless", "next-gen")', and "'Easier to use' is not an attribute. 'Processes in real time without a manual sync step' is an attribute." For an instruction-only skill this is fully executable guidance covering the common cases, matching the top anchor.

5 / 5

Workflow Clarity

The sequence is explicit (Inputs → Steps 1–8 → Delivery) with real checkpoints late in the flow: 'Apply these tests before moving on' (three named tests in Step 6) and the fix directive 'If you can shrug, rewrite it', plus assumption flagging at input and delivery. However, no validation checkpoints exist between Steps 1–5 (e.g., minimum alternative count, attribute-prune gate), so errors surface only after the statement is drafted — a minor gap consistent with anchor 4.

4 / 5

Progressive Disclosure

The body is well-sectioned, but scored against the actual bundle structure it has a broken reference chain: 'Follow the output format defined in docs/output-kit.md' points to a file that does not exist anywhere in the bundle (no references/, scripts/, assets/, or docs/ directories), and the delivery step depends on an unshipped '/atlas-report' skill. The only external reference is dangling, which strands the reader at Step 8 — matching anchor 3 ('references present but not clearly signaled; could be better organized') rather than 4.

3 / 5

Total

16

/

20

Passed

Description

96%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 exemplary: it names the framework, enumerates every deliverable component, and supplies seven quoted natural trigger phrases that explicitly answer both what the skill does and when to invoke it. The only weakness is minor overlap risk with adjacent messaging/copywriting skills via the broader trigger phrases.

DimensionReasoningScore

Specificity

'Produce a complete positioning document using the Dunford framework — competitive alternatives, unique attributes, value, best-fit customer, market category, positioning statement, and tagline' enumerates all seven deliverable components concretely and comprehensively. Not anchor 4, which is reserved for coverage with 'minor gaps' — the enumeration matches the full framework.

5 / 5

Completeness

Both halves are explicit: the 'what' ('Produce a complete positioning document using the Dunford framework…') and the 'when' ('Use when asked to…' followed by concrete trigger phrases). This matches the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

Seven quoted natural user phrases are provided: 'write our positioning', 'define our value prop', 'positioning statement', 'what market are we in', 'how do we position against X', 'what's our tagline', and 'write our messaging foundation' — comprehensive coverage including synonyms, matching the top anchor.

5 / 5

Distinctiveness Conflict Risk

The Dunford positioning niche is clear and the triggers are distinct, but phrases like 'define our value prop' and 'write our messaging foundation' could plausibly belong to adjacent messaging/copywriting skills in the same family — minor overlap risk with closely related skills, i.e., anchor 4 rather than anchor 5's 'minimal conflict risk'.

4 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

jeremylongshore/tons-of-skills-marketplace

Path

plugins/ai-agency/tonone/bundle/marketing-team/skills/pitch-position/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.