Generate JTBD (Jobs-to-be-Done) markdown files from step descriptions. Use when creating API workflows, building JTBD files, documenting multi-step processes, or when user says "create a JTBD", "generate workflow", "document these API steps", or "build a job with these operations".
80
72%
Does it follow best practices?
Impact
92%
3.17xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/jtbd-generator/SKILL.mdJTBD file structure and naming conventions
Correct save path
0%
100%
Kebab-case name
0%
100%
Name length
0%
100%
Description field present
0%
100%
Description length
0%
100%
Step headers exist
0%
100%
Sequential step numbering
0%
100%
URN format for api field
0%
100%
operationId field present
0%
100%
Inputs section present
0%
100%
Action-oriented overview
0%
100%
Folder name matches frontmatter name
0%
100%
Prerequisites section
0%
100%
Completion or summary section
0%
100%
Multi-step data flow between JTBD steps
Two step headers
0%
100%
Step 1 outputs section
100%
100%
projectId captured in outputs
100%
100%
Step 2 links projectId to Step 1
75%
60%
organizationId reused from Step 1
0%
33%
URN format in both steps
0%
100%
Inputs in both steps
100%
100%
Correct save path
0%
100%
Kebab-case name
100%
100%
Sequential step numbering
0%
100%
What happens next in Step 1
30%
100%
Conversational prose and action-oriented documentation
Overview section present
0%
100%
Overview starts with action verb
0%
100%
Conversational step language
53%
100%
Purpose explanations
53%
66%
What happens next sections
0%
100%
Prerequisites section
0%
100%
No placeholder text
100%
100%
Correct save path
0%
100%
URN format in YAML blocks
0%
100%
Specific terminology in descriptions
100%
100%
32e2b58
Table of Contents
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.