developer-journey-map skill (samber): find where developers drop off
Maps one developer segment's journey stage by stage and names the single leak worth fixing next.
- Installs
- 12.4K
- on skills.sh
- Stars
- 7
- on GitHub
- Files
- 5
- besides SKILL.md
- Updated
- Nov 2026
- last repo commit
developer-journey-map produces a decision artefact: one table with a row per stage, each row carrying an exit event, a named owner, cited friction evidence and one signal, plus a short diagnosis of the one stage to work on next. It picks a published stage model first, collects evidence before filling any row, adds a buyer lane for B2B, names three critical moments and writes a seven-heading map validated section by section.
It triggers on "what does our developer journey look like", "where does adoption drop off" or "who owns each step". It bundles no scripts. SKILL.md says it maps and diagnoses and does not fix the stages, and it sends the metrics framework to devrel-metrics.
Good for
- DevRel leads who think they lose developers somewhere between trial and production
- Teams asking who owns each step of developer experience
- Maintainers mapping how users become contributors
Install developer-journey-map
Claude Code
- 1
Copy this prompt.
Install the developer-journey-map skill in Claude Code. Run this command: /plugin marketplace add samber/developer-relations-skills /plugin install developer-relations-skills@developer-relations-skills Then check that it loaded and tell me how to use it.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
The README recommends installing the whole collection because its skills reference each other, and developer-journey-map names other skills in the collection to hand work to. The whole-collection routes add all 93 skills in the repo (counted from the git tree); the repo holds no hooks, agents, commands or MCP server files, and 14 of its skills bundle a script. Pick one route per agent.
From the project README. Source.
What's in the skill
When it loads
Maps the developer journey for one audience segment - discovery, trial, adoption, contribution, advocacy - as a stage-by-stage table where each stage carries an exit event, a named owner, cited friction evidence and one signal, and names the single leak worth fixing next. Use whenever someone asks what their developer journey looks like, wants a developer adoption funnel or journey map, asks why developers try the product but never reach production, where adoption drops off, who owns each step of developer experience, or how developers become contributors - even if they only say "we lose people somewhere". Not the metrics framework - use samber/developer-relations-skills@devrel-metrics.
Sections in SKILL.md
- What you can cite, and what you cannot
- Invocation examples
- Interview
- Step 1 - Choose the stage model, do not invent one
- Step 2 - Collect evidence before filling any row
- Step 3 - Fill one row per stage
- Step 4 - Add the buyer lane, or say there isn't one
- Step 5 - Name the three critical moments
- Step 6 - Diagnose the leak
- Step 7 - Write the map and validate it section by section
- Scope segment, end state, stage model used and why
- Journey the stage table (one row per stage, eight fields)
- Buyer lane the buyer's stages, or an explicit "none - self-serve"
- Moments first success, moment of truth, abandonment point
- Leak the chosen stage, its evidence, why it beat the others
- Handoff who owns the fix, the signal to watch, the re-read date
Key facts
- Skill version
- 1.0.2 (SKILL.md metadata)
- Installs on skills.sh
- 12,429 (Nov 2, 2026)
- Last repo commit
- Nov 1, 2026
- Audits on skills.sh
- Gen Agent Trust Hub: pass, Socket: pass, Snyk: pass
What it includes
Asks 13 questions; segment, end state and available evidence come first.
InterviewDeletes models whose last stage is not your end state, then ranks the rest.
Deletes models whose last stage is not your end state, then ranks the rest; five models are on the menu.
Step 1: Choose the stage modelUses a friction log, tickets, interviews with finishers and drop-outs, and funnel data.
Friction log, mining tickets and threads, interviews with 5-8 finishers and 3 who abandoned, and existing funnel data.
Step 2: Collect evidenceFills eight fields per stage, with exit event, owner and signal required.
Eight fields per stage, with exit event, owner and signal required.
Step 3: Fill one row per stageAdds a lane for the economic buyer in B2B, with three signal families.
Adds a lane for the economic buyer in B2B, with depth, spread and boundary-contact signals.
Step 4: Buyer laneNames the first success, the moment of truth and the abandonment point.
First success, moment of truth and abandonment point.
Step 5: Three critical momentsPicks the earliest poorly converting stage that has an owner, then explains why.
Picks one stage, the earliest that converts poorly and has an owner who can change it, then explains why using BJ Fogg's B=MAP.
Step 6: Diagnose the leakWrites seven headings, validated with you section by section.
Seven headings, validated section by section.
Step 7: Write the mapRequires seven checks, such as one exit event per stage and 60% of stages with a signal.
Seven checks, such as one exit event per stage and at least 60% of stages with a real signal.
Quality gate
From the official docs
Permissions
Low risk
developer-journey-map is interview and analysis instructions with no scripts, and it may save notes to devrel-context.md.
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
It may save notes to devrel-context.md
SKILL.md tells Claude to keep task and project context in devrel-context.md when memory lives in a file, or in the memory system your tool already uses. Check the file before you commit it. github.com
The whole-set install adds 93 skills, 14 with scripts
The README says to install every skill. The git tree has 93 skill folders, and 14 of them hold .py or .sh files. This skill bundles no scripts, and the tree holds no hooks, agents or MCP config files. github.com
Technical details
| Turning on read-only | SKILL.md describes no read-only mode. |
|---|---|
| Sign-in and keys | SKILL.md names no account, key or token. |
| Scopes |
|
Questions
What does developer-journey-map do?
It maps a developer's path from discovery to advocacy for one audience segment. You get a table with an exit event, owner, friction evidence and signal per stage, and a named leak with an owner and a re-read date.
How do I install it?
Use the install box at the top. The README says to install every skill in the repo, because the skills point to each other. The box shows the whole-set route for each app.
Where do the conversion numbers come from?
From your own data. SKILL.md says other companies' published rates use incompatible stage definitions, so it compares only against this map's previous version and labels unmeasured stages as inferred.
Does it fix the leak?
No. SKILL.md says to produce the map and the leak diagnosis and not to fix the stages. It names one stage, who owns the fix and the signal to watch.
Is it safe to install?
The skill bundles no scripts. Analytics numbers, tickets and interview notes you share go into your conversation. The whole-set install adds 93 skills, 14 of which bundle scripts.
How is it different from devrel-metrics?
This skill maps stages and finds the leak. SKILL.md routes the full measurement framework to samber/developer-relations-skills@devrel-metrics and the tracking plan to devrel-analytics.
Information
updated Nov 2, 2026
- Repository
- samber/developer-relations-skills
- Folder
skills/developer-journey-map
Sources
Docs, issue trackers and discussions this page is built from.
Show all 3Hide
- README · github.com
- developer-journey-map SKILL.md · github.com
- LICENSE · github.com