CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

positioning-workshop

Run a positioning workshop that surfaces target customer, unmet need, category, benefits, and differentiation. Use when your product messaging feels fuzzy, generic, or misaligned.

Quality

83%

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

75%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 facilitation skill with a clear sequenced workflow and concrete templates. Its main weakness is verbosity from redundant sections (repeated intent, overlapping pitfall/anti-pattern content) that could be tightened or split into reference files.

Suggestions

Remove the verbatim repeat of the frontmatter intent in the Purpose section, or replace it with a one-line summary.

Consolidate the Anti-Patterns, Common Pitfalls, and the bad Example 2 sections, which cover overlapping ground (vague target, feature-as-need, feature-as-differentiation).

Move the worked examples and/or the full output template into a reference file (e.g. references/positioning-statement.md) and link to it, reducing the inline SKILL.md length and improving progressive disclosure.

DimensionReasoningScore

Conciseness

Mostly useful domain content, but padded: the Purpose section repeats the frontmatter intent verbatim, Common Pitfalls overlaps the Anti-Patterns and bad-example sections, and the enumerated option lists are long.

3 / 5

Actionability

Concrete adaptive questions, enumerated context-aware options, a copy-paste-ready positioning-statement output template, and worked good/bad examples make the guidance fully executable for an instruction-only skill.

5 / 5

Workflow Clarity

Clear Step 0 → Q1–Q5 → Output sequence with quality checks, adaptation tips, and a stress-test step; not a destructive/batch operation so no cap applies, but inter-step validation gates are implicit rather than explicit.

4 / 5

Progressive Disclosure

Clear section headers and one-level-deep references to sibling skills (positioning-statement.md, workshop-facilitation) are well signaled; no bundle files exist and the ~400-line body is monolithic, but content is well organized.

4 / 5

Total

16

/

20

Passed

Description

87%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 that clearly states what the skill does and when to use it, with specific enumerated outputs and natural trigger language. Third-person imperative voice is used correctly.

DimensionReasoningScore

Specificity

Names the domain and lists five concrete surfaced elements ("target customer, unmet need, category, benefits, and differentiation"), giving comprehensive coverage under a single action verb rather than multiple distinct actions.

4 / 5

Completeness

Explicitly answers both what ("Run a positioning workshop that surfaces...") and when ("Use when your product messaging feels fuzzy, generic, or misaligned") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases like "product messaging feels fuzzy, generic, or misaligned" plus "positioning workshop" give good coverage, though common synonyms like "value proposition" or "differentiate" are missing.

4 / 5

Distinctiveness Conflict Risk

"Positioning workshop" is a clear niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

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

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository

deanpeters/Product-Manager-Skills

Path

skills/positioning-workshop/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.