CtrlK
BlogDocsLog inGet started
Tessl Logo

devrel-story-craft

Design authentic launch stories, TAB, and dev packaging. Use when planning a launch narrative, TAB outreach, or pricing for developers. It does not design first-success DX (that's `devrel-dx-craft`).

67

Quality

80%

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 ./plugins/dev-gtm/skills/devrel-story-craft/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 body is well-structured with clear phase-gated workflow, validation checkpoints, and excellent progressive disclosure to real reference files. Its main weakness is verbosity from authoring-meta sections and repeated pressure-counters that could be trimmed.

Suggestions

Remove or relocate the Quality Checklist: items like 'frontmatter matches exact devex-kit shape' and 'writing-skills TDD baselines passed' describe how the skill was authored, not how to execute it, and consume context without aiding the task.

Tighten REFACTOR Hardening: the 'No exceptions' / delete-and-restart counter appears in multiple sections; consolidate into one stated rule in story-framework.md and reference it rather than restating throughout the body.

Trim the Attribution section's method note ('This skill was authored via writing-skills TDD ...') which is authoring provenance rather than execution guidance.

DimensionReasoningScore

Conciseness

The core sections are efficient and externalize heavy content, but the Quality Checklist and REFACTOR Hardening sections contain skill-authoring meta-content ('frontmatter matches exact devex-kit shape', 'writing-skills TDD baselines passed') and repeated 'No exceptions' counters that pad the body without aiding execution.

3 / 5

Actionability

It gives concrete, specific instruction ('produce the 3-part story canvas (Pain, Villain, Victory)', 'Use exactly the 3 diagnostic questions', 'magic moment that must be $0 and <5 minutes') with explicit rules, deferring only the bulk specifics to references, which is appropriate for an instruction skill.

4 / 5

Workflow Clarity

It sequences Story Building -> TAB -> Presence -> Packaging with explicit phase gates, validation checkpoints ('At least 5 TAB calls with diverse personas', 'story canvas updated with direct quotes'), feedback loops ('return to Story Building'), and a checklist.

5 / 5

Progressive Disclosure

The body is a clear overview with well-signaled one-level-deep load blockquotes to story-framework.md, tab-playbook.md, presence-advocacy.md, and packaging-pricing.md, all of which exist as real files; content is appropriately split and easy to navigate.

5 / 5

Total

17

/

20

Passed

Description

82%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 strong: third-person, with an explicit 'Use when' clause, concrete trigger phrases, and a clear boundary against a sibling skill. Its only weakness is that the action verb is singular, keeping specificity just below comprehensive.

DimensionReasoningScore

Specificity

It names the domain ('launch stories, TAB, and dev packaging') with the concrete action 'Design', but relies on a single verb across three areas rather than enumerating several specific actions, so it is not comprehensive.

3 / 5

Completeness

It explicitly answers both what ('Design authentic launch stories, TAB, and dev packaging') and when ('Use when planning a launch narrative, TAB outreach, or pricing for developers') with concrete trigger phrases.

5 / 5

Trigger Term Quality

'Use when planning a launch narrative, TAB outreach, or pricing for developers' gives good natural keyword coverage with concrete trigger phrases, though a few common synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (DevRel launch story/TAB/packaging) with distinct triggers and an explicit boundary statement ('It does not design first-success DX (that's devrel-dx-craft)'), minimizing 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
saif-shines/devex-kit
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.