service-blueprint
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`.
npx skills add Owl-Listener/designer-skills --skill service-blueprint --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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: 1. **Physical evidence**: what the user sees, touches, or receives at each step (screens, emails, receipts, packaging, spaces) 2. **User actions**: what the user does — drawn from journey map research 3. **Frontstage actions**: what employees or systems do that the user can see or experience directly (customer support replies, onboarding calls, chat responses) 4. **Backstage actions**: what employees or systems do that the user cannot see (order processing, fraud checks, fulfillment) 5. **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**: separ
- What You Do
- What a Service Blueprint Shows
- When to Use a Service Blueprint
- Blueprint vs Journey Map
- Process
- Reading the Blueprint
- Best Practices
What does the service-blueprint skill do?
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`.
How do I install it?
Run `npx skills add Owl-Listener/designer-skills --skill service-blueprint --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Owl-Listener/designer-skills, a repository with 1,964 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.