Service Blueprinting
Prorise-cool/Claude-Code-Multi-Agent
Create service blueprints - frontstage/backstage visualization, touchpoints, support processes, evidence, and service design methodology.
Map service delivery across frontstage actions, backstage processes, and supporting systems.
Install Service Blueprint
$ npx skills add Owl-Listener/designer-skills --skill service-blueprint -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designer-skills service-blueprint --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ux-strategy/skills/service-blueprint .claude/skills/service-blueprint && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "service-blueprint" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/ux-strategy/skills/service-blueprint into .claude/skills/service-blueprint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-blueprint", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Owl-Listener/designer-skills/tree/main/ux-strategy/skills/service-blueprintType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Owl-Listener/designer-skills --skill service-blueprint -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designer-skills service-blueprint --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/ux-strategy/skills/service-blueprint .agents/skills/service-blueprint && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "service-blueprint" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/ux-strategy/skills/service-blueprint into .agents/skills/service-blueprint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-blueprint", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designer-skills --skill service-blueprint -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designer-skills service-blueprint --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/ux-strategy/skills/service-blueprint .cursor/skills/service-blueprint && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "service-blueprint" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/ux-strategy/skills/service-blueprint into .cursor/skills/service-blueprint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-blueprint", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Owl-Listener/designer-skills.git --path ux-strategy/skills/service-blueprint--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Owl-Listener/designer-skills --skill service-blueprint -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designer-skills service-blueprint --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/ux-strategy/skills/service-blueprint .gemini/skills/service-blueprint && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "service-blueprint" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/ux-strategy/skills/service-blueprint into .gemini/skills/service-blueprint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-blueprint", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Owl-Listener/designer-skills service-blueprintInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Owl-Listener/designer-skills --skill service-blueprint -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/ux-strategy/skills/service-blueprint .github/skills/service-blueprint && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "service-blueprint" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/ux-strategy/skills/service-blueprint into .github/skills/service-blueprint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-blueprint", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designer-skills --skill service-blueprint -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Owl-Listener/designer-skills service-blueprint --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/ux-strategy/skills/service-blueprint .opencode/skills/service-blueprint && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "service-blueprint" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/ux-strategy/skills/service-blueprint into .opencode/skills/service-blueprint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-blueprint", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
service-blueprint- GitHub stars
- 2.9k
- Used in
- 1 other repo
- Token cost
- ~1k tokens
- SKILL.md length
- 527 words
- Files
- 1
- Skills in repo
- 107
- Repo updated
- First seen
- Licence
- MIT
At a glance
Map service delivery across frontstage actions, backstage processes, and supporting systems.
- Works in 5 steps: Physical evidence: what the user sees,… → User actions: what the user does — drawn… → Frontstage actions: what employees or… → …
- Staff and operations are part of the experience
- SKILL.md covers What You Do, What a Service Blueprint Shows, When to Use a Service Blueprint and Blueprint vs Journey Map, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Service Blueprint is an agent skill from Owl-Listener/designer-skills. Map service delivery across frontstage actions, backstage processes, and supporting systems. Use when staff and operations are part of the experience. For the customer-visible layer only, use experience-map.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering Customer journey mapping and Platform engineering. The repository describes itself as: Designer Skills Collection: agentic skills, commands, and plugins for design — from research to systems, UI, interaction, and delivery. The licence is MIT.
When your agent uses it
- Staff and operations are part of the experience
- Tasks that involve Customer journey mapping
- Tasks that involve Platform engineering
Example prompts
- “/service-blueprint”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Physical evidence: what the user sees, touches, or receives at each step (screens, emails, receipts, packaging, spaces)
- User actions: what the user does — drawn from journey map research
- Frontstage actions: what employees or systems do that the user can see or experience directly (customer support replies, onboarding calls…
- Backstage actions: what employees or systems do that the user cannot see (order processing, fraud checks, fulfillment)
- Support processes: the infrastructure that enables frontstage and backstage (databases, third-party services, internal tools, policies)
What it can do on your machine
Read from SKILL.md and the folder at commit 9a6930c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Service Blueprint loads about 1k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 527 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Owl-Listener/designer-skills at commit 9a6930c, republished under its MIT licence (© Owl-Listener). 527 words, ~1,020 tokens.
Download SKILL.mdSave it as
.claude/skills/service-blueprint/SKILL.md (or your agent's skills folder).- name
- service-blueprint
- description
- Map service delivery across frontstage actions, backstage processes, and supporting systems. Use when staff and operations are part of the experience. For the customer-visible layer only, use `experience-map`.
Service Blueprint
You are an expert in service design and systems-level experience mapping.
What You Do
You create service blueprints that reveal how a service is delivered across all channels and actors — giving teams a shared view of the full system, not just the user-facing touchpoints.
What a Service Blueprint Shows
A blueprint maps five horizontal swim lanes:
- Physical evidence: what the user sees, touches, or receives at each step (screens, emails, receipts, packaging, spaces)
- User actions: what the user does — drawn from journey map research
- Frontstage actions: what employees or systems do that the user can see or experience directly (customer support replies, onboarding calls, chat responses)
- Backstage actions: what employees or systems do that the user cannot see (order processing, fraud checks, fulfillment)
- Support processes: the infrastructure that enables frontstage and backstage (databases, third-party services, internal tools, policies) Line of interaction: separates user actions from frontstage Line of visibility: separates frontstage (visible to user) from backstage (invisible) Line of internal interaction: separates backstage from support processes
When to Use a Service Blueprint
- Designing a new end-to-end service
- Diagnosing where a service is failing (look for gaps between swim lanes)
- Coordinating a multi-team product that spans multiple channels (web, app, email, phone, physical)
- Planning a major service redesign or migration
- Onboarding new team members to the full scope of a product
Blueprint vs Journey Map
| Journey Map | Service Blueprint | |
|---|---|---|
| Focus | User experience | Entire delivery system |
| Actors | User | User + employees + systems |
| Purpose | Understand emotional journey | Reveal operational gaps and dependencies |
| When | Research and ideation | System design and coordination |
| Use journey maps to understand the experience; use blueprints to design and fix the system delivering it. |
Show full SKILL.md (247 more words)Show less
Process
- Define scope: choose a specific scenario (e.g. "first-time user completes onboarding") — don't try to blueprint the entire product at once
- Gather inputs: user journey research, stakeholder interviews, process documentation, analytics
- Draft user actions: adapt from journey map
- Map frontstage: for each user action, what does the system or team do visibly?
- Map backstage: what happens behind the scenes to enable each frontstage action?
- Map support: what infrastructure, tools, or third-party services support backstage actions?
- Add physical evidence: what artifacts does the user receive or interact with?
- Identify failure points: where do swim lanes disconnect? Where do delays, errors, or handoffs break down?
- Validate: review with operations, engineering, and support teams — they often spot missing backstage steps
Reading the Blueprint
- Gaps between lanes: where frontstage promises something backstage can't deliver
- High-density backstage clusters: complexity that may be ripe for automation or simplification
- Multiple support dependencies for a single frontstage action: fragility — single points of failure
- Long horizontal stretches without user touchpoints: the user is waiting; is this communicated?
Best Practices
- Blueprint existing state first, future state second — don't skip the as-is
- Co-create with operational teams, not just design — they know the backstage
- Keep scope narrow; a focused blueprint of one scenario is more useful than a sprawling map of everything
- Use the blueprint as a coordination artifact in cross-functional planning, not just as a research output
- Revisit blueprints when services change — they become misleading faster than journey maps
© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in ux-strategy/skills/service-blueprint of Owl-Listener/designer-skills.
Open the folder on GitHubat commit 9a6930c
Used in 1 other repository
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Owl-Listener/designer-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Service Blueprint next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Service Blueprint this skillOwl-Listener/designer-skills | 2.9k | 1 repos | ~1k | Automated safety check: Pass | MIT | |
| Service BlueprintingProrise-cool/Claude-Code-Multi-Agent | 306 | — | ~3.9k | Automated safety check: Pass | None | |
| User Story Mappingdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~2.8k | Automated safety check: Pass | Custom licence | |
| QA Critical UXfastrepl/anarlog | 9.5k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Prdjuanandresgs/claude-ctrl | 193 | — | ~2.9k | Automated safety check: Pass | None | |
| Customer Journey Map Builderdeanpeters/Product-Manager-Skills | 7.2k | 1 repos | ~3.7k | Automated safety check: Pass | Custom licence |
Similar skills
User Story Mapping
deanpeters/Product-Manager-Skills
Lays out a user journey as activities, steps, and tasks on a two-dimensional map that then informs backlog slicing.
QA Critical UX
fastrepl/anarlog
QA Anarlog's critical Pro user journey on a signed staging candidate — onboarding, responsive launch, microphone and system-audio capture, automated summaries, and cloud sync.
Prd
juanandresgs/claude-ctrl
Write structured feature specifications with problem statements, user journeys, use cases, functional requirements, and success metrics.
Customer Journey Map Builder
deanpeters/Product-Manager-Skills
Builds a stage-by-stage customer journey map covering actions, touchpoints, emotions, KPIs, goals, and owning teams for one persona and scenario.
Super Product Owner
syahiidkamil/Software-Engineer-AI-Agent-Atlas
Complete Product Owner / Product Manager capability — a wiki-style knowledge map of product practice in active software development: the role and its boundaries, strategy cascade (vision → OKRs →…
More from Owl-Listener/designer-skills
All 107 skills in this repoA B Test Design
Owl-Listener/designer-skills
Design an A/B experiment — hypothesis, variants, primary metric, and sample size.
Accessibility Test Plan
Owl-Listener/designer-skills
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol.
Aesthetic Usability
Owl-Listener/designer-skills
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction.
Affinity Diagram
Owl-Listener/designer-skills
Cluster many qualitative data points into themes and insight statements.
Animation Principles
Owl-Listener/designer-skills
Apply animation principles — easing, staging, follow-through — to one specific UI motion.
Business Design
Owl-Listener/designer-skills
Read financials, map competitive landscapes, and argue design decisions in the language of value.
Related
Categories
Questions about Service Blueprint
What does Service Blueprint do?
Map service delivery across frontstage actions, backstage processes, and supporting systems. Service Blueprint is an agent skill from Owl-Listener/designer-skills. Map service delivery across frontstage actions, backstage processes, and supporting systems.
When should I use Service Blueprint?
Service Blueprint fits situations like: staff and operations are part of the experience; tasks that involve Customer journey mapping; tasks that involve Platform engineering.
How do I install Service Blueprint in Claude Code?
Run `npx skills add Owl-Listener/designer-skills --skill service-blueprint -a claude-code`. Or copy the skill folder (ux-strategy/skills/service-blueprint in Owl-Listener/designer-skills) into .claude/skills/service-blueprint in your project. Claude Code loads it when a task matches its description.
How do I install Service Blueprint in Codex?
Run `npx skills add Owl-Listener/designer-skills --skill service-blueprint -a codex`. Or copy the skill folder (ux-strategy/skills/service-blueprint in Owl-Listener/designer-skills) into .agents/skills/service-blueprint in your project. Codex loads it when a task matches its description.
Can I use Service Blueprint in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Owl-Listener/designer-skills --skill service-blueprint -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/service-blueprint, .gemini/skills/service-blueprint, .github/skills/service-blueprint and .opencode/skills/service-blueprint in your project.
What does Service Blueprint need to run?
SKILL.md names no scripts, command-line tools or credentials: Service Blueprint is instructions for the agent only.
Does Service Blueprint access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Service Blueprint safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Service Blueprint use?
Service Blueprint is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Service Blueprint use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Service Blueprint?
Skills that share tags, products or a category with Service Blueprint: Service Blueprinting (Prorise-cool/Claude-Code-Multi-Agent, 306 stars), User Story Mapping (deanpeters/Product-Manager-Skills, 7.2k stars), QA Critical UX (fastrepl/anarlog, 9.5k stars) and Prd (juanandresgs/claude-ctrl, 193 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Service Blueprint?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/designer-skills, which has 2,871 GitHub stars. The repository holds 107 skills in this directory. The repository was last updated on September 5, 2026.
Source: Owl-Listener/designer-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.