CtrlK
BlogDocsLog inGet started
Tessl Logo

pm-skill-creator

Design a new PM skill through guided conversation. Use when you have raw content or an idea and want to shape it into a compliant skill.

65

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 ./skills/pm-skill-creator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and clearly sequenced with explicit validation gates, and its references are well-signaled and one level deep. The only meaningful weakness is moderate redundancy where the Purpose and Draft Generation sections restate content already present elsewhere.

Suggestions

Remove the verbatim duplication between the frontmatter intent and the Purpose section, or have Purpose add only the relationship to skill-authoring-workflow.

Consolidate the Skill Anatomy section list and the Draft Generation output list so the section inventory is stated once and cross-referenced.

DimensionReasoningScore

Conciseness

The body is mostly efficient with no off-topic concept explanations, but the Purpose section duplicates the intent frontmatter verbatim and the Skill Anatomy and Draft Generation lists restate the same section inventory, so it could be tightened per the level-2 anchor.

2 / 3

Actionability

It provides copy-ready scripted prompts, numbered response options, exact validation commands (e.g., 'python3 scripts/check-skill-metadata.py skills/<name>/SKILL.md'), and full example Q&A transcripts, matching the level-3 fully-executable anchor for an instruction-only skill.

3 / 3

Workflow Clarity

A clear Step 0 -> Q1-Q5 -> Draft Generation sequence is given with explicit validation checkpoints (check-skill-metadata, check-skill-triggers, test-a-skill) and an adjust-then-validate feedback loop, matching the level-3 anchor.

3 / 3

Progressive Disclosure

No bundle files exist, so content lives in well-organized top-level sections; all external references (workshop-facilitation, skill-authoring-workflow, repo scripts) are one level deep and clearly signaled in the References section, satisfying the level-3 anchor.

3 / 3

Total

11

/

12

Passed

Description

75%

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 cleanly answers both 'what' and 'when' with an explicit trigger and a distinctive meta-authoring niche. It is slightly held back by naming only one action method and by repo-facing jargon ('compliant skill') narrowing the natural trigger vocabulary.

Suggestions

Expand specificity by listing a second concrete action (e.g., 'shape raw notes into a structured skill draft') to reach the level-3 'multiple specific actions' anchor.

Replace repo jargon 'compliant skill' with user-natural phrasing like 'a ready-to-use skill' and add common variations such as 'turn notes into a skill' to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('PM skill') and a single action method ('Design... through guided conversation') but does not list multiple distinct concrete actions, so it falls short of the level-3 anchor and above the vague level-1 anchor.

2 / 3

Completeness

It explicitly states what it does ('Design a new PM skill through guided conversation') and includes an explicit 'Use when...' trigger clause, satisfying both halves of the level-3 anchor.

3 / 3

Trigger Term Quality

'raw content or an idea' are natural user phrases, but 'compliant skill' is repo-facing jargon and common variations (e.g., 'turn notes into a skill', 'create a skill') are missing, matching the level-2 anchor.

2 / 3

Distinctiveness Conflict Risk

The meta-authoring niche ('design a new PM skill' from 'raw content or an idea') is clearly distinct from domain skills and unlikely to trigger for the wrong skill, matching the level-3 anchor.

3 / 3

Total

10

/

12

Passed

Validation

81%

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

Validation13 / 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: 3 suspicious

Warning

referenced_paths_exist

Referenced path issues: 11 missing

Warning

Total

13

/

16

Passed

Repository
deanpeters/Product-Manager-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.