CtrlK
BlogDocsLog inGet started
Tessl Logo

job-stories

Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria. Use when writing job stories, creating JTBD-style backlog items, or expressing user situations and motivations.

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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./pm-execution/skills/job-stories/SKILL.md
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, self-contained skill with a concrete template, a fully worked example, and a clear multi-step process. The main improvements are removing the redundant restatement of the description and adding an explicit validation/quality-check checkpoint before output.

Suggestions

Remove the redundant opening sentence and 'Use when' block since they restate the frontmatter description, or replace them with body-specific guidance not already in the description.

Add an explicit quality-check checkpoint to the process (e.g., 'Verify each story follows the When/I want/so I can format and has 6-8 measurable acceptance criteria before output') to strengthen workflow clarity.

Show one variant story shape (e.g., an edge-case or B2B example) in addition to the snack-spending example to broaden actionability coverage.

DimensionReasoningScore

Conciseness

The body is mostly efficient with a concrete template, worked example, and a numbered process, but the opening line and 'Use when' block repeat the frontmatter description, leaving minor instances that could be trimmed.

4 / 5

Actionability

Provides a concrete story template, a six-item acceptance-criteria template, and a fully worked example (Track Weekly Snack Spending) that serves as a copy-paste-ready model; minor gaps remain in showing variant story shapes.

4 / 5

Workflow Clarity

The eight-step process is a clear, ordered sequence and the task is non-destructive so the validation cap does not apply, but explicit checkpoints (e.g., verifying each story follows the format before output) are implicit rather than stated.

4 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections, is self-contained with no bundle files, and the single external link is one level deep and clearly signaled; it sits just above the 'good structure, minor gaps' anchor.

4 / 5

Total

16

/

20

Passed

Description

78%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, well-structured description that clearly states both the capability and the trigger conditions with good natural-language keywords. It is held back only by describing a single primary action rather than enumerating several distinct capabilities.

Suggestions

Optionally name a second concrete action (e.g., 'break a feature into multiple job stories' or 'refine acceptance criteria') to lift specificity from one detailed action to several distinct ones.

Consider adding 'user stories' as a synonym in the trigger clause to broaden natural-term coverage and reduce overlap ambiguity with user-story skills.

DimensionReasoningScore

Specificity

Names the domain and the explicit 'When...I want...so I can' format plus acceptance criteria, but it is essentially one action (create job stories) described in detail rather than a list of multiple distinct actions, matching the anchor for 1-2 concrete actions.

3 / 5

Completeness

Explicitly answers both 'what' (create job stories in the When/I want/so I can format with acceptance criteria) and 'when' (writing job stories, JTBD-style backlog items, expressing user situations and motivations) with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say — 'job stories', 'JTBD-style backlog items', 'user situations and motivations' — with the JTBD synonym, giving good coverage though a few variants like 'user stories' are absent.

4 / 5

Distinctiveness Conflict Risk

JTBD/job stories is a distinct niche with clear triggers, but 'JTBD-style backlog items' creates minor overlap risk with general backlog or user-story skills, landing just below the minimal-conflict anchor.

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
phuryn/pm-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.