CtrlK
BlogDocsLog inGet started
Tessl Logo

roadmap-communicator

Use when preparing roadmap narratives, release notes, changelogs, or stakeholder updates tailored for executives, engineering teams, and customers.

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

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./product-team/skills/roadmap-communicator/SKILL.md
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-structured, token-efficient communication skill that keeps the overview in SKILL.md and pushes templates and tooling into real one-level-deep bundle files. It is actionable and clearly navigable, with only minor opportunities to tighten redundancy and add explicit validation gating.

DimensionReasoningScore

Conciseness

The body is lean and bullet-driven with no padding or explanation of concepts Claude already knows; the only minor trim opportunity is the 'When To Use' list, which overlaps the frontmatter description.

4 / 5

Actionability

Provides a concrete executable command (changelog_generator.py invocation) plus concrete referenced templates and a numbered framework, but the roadmap-format and stakeholder-pattern sections stay somewhat high-level rather than step-by-step.

4 / 5

Workflow Clarity

The Feature Announcement Framework is a clear numbered sequence and the Communication Quality Checklist acts as a checkpoint; as a non-destructive communication skill it needs no validate-fix-retry loop, though explicit gating language would push it higher.

4 / 5

Progressive Disclosure

A clear overview that points to two real, well-signaled, one-level-deep references (references/roadmap-templates.md, references/communication-templates.md) and a script, with detail appropriately split out of the main file.

5 / 5

Total

17

/

20

Passed

Description

75%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 solid, audience-aware trigger description that names concrete deliverables and explicit use-conditions. It stops short of the top anchor because the 'what' and 'when' are folded together and a few natural synonyms are missing.

Suggestions

Lead with a distinct capability verb statement before the trigger, e.g. 'Drafts roadmap narratives, release notes, changelogs, and stakeholder updates. Use when...' to cleanly separate 'what' from 'when'.

Add natural synonyms users may say, such as 'product updates', 'feature announcements', or 'launch communications', to broaden trigger coverage.

Consider naming output formats (e.g. markdown, slides, email) to sharpen the distinctiveness versus generic writing skills.

DimensionReasoningScore

Specificity

Lists several concrete deliverables — 'roadmap narratives, release notes, changelogs, or stakeholder updates' — with audience tailoring, but these are artifact types rather than granular actions, leaving minor coverage gaps.

4 / 5

Completeness

Has an explicit 'Use when...' trigger clause and an embedded 'what' (preparing those artifacts), so both are present, but the what and when are merged rather than cleanly separated into a distinct capability statement plus concrete trigger phrases.

4 / 5

Trigger Term Quality

Includes natural terms users would say (roadmap, release notes, changelogs, stakeholder updates, executives/engineering/customers), but misses common synonyms like 'announcements' or 'product updates' needed for comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (roadmap/stakeholder communication) with distinct triggers, with only minor overlap risk against generic release-notes or git-commit skills.

4 / 5

Total

16

/

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
alirezarezvani/claude-skills
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.