agentleFS
Sign inStart free
podopodo/design-agent-skills/skills/service-blueprint/SKILL.md

service-blueprint

Skill32 starsChanged 6 months agoMITView on GitHub

Generate professional service blueprints (NN/g, GDS, Practical Service Design): the five swim lanes, lines of interaction/visibility/internal-interaction, plus a JSON schema and render pipeline.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read ~/.agents/service-blueprint-skill/SKILL.md and follow it.

    line 46

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

service-blueprint

Catalogue stub — full package: j-clegg/service-blueprint-skill

<!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block -->

Decision tree

  1. Is the full skill already installed?
    • f=~/.agents/service-blueprint-skill/SKILL.md; [ -e "$f" ] && ! grep -qs "^das:" "$f" && echo "installed" || echo "pointer"
    • installed → invoke it and proceed
    • pointer → go to step 2

  2. Install (the skills CLI cannot install this one):

    The upstream SKILL.md has no YAML frontmatter (name, description), so the skills CLI skips it and installs nothing ("No valid skills found"). Clone the repo to a fixed folder and have your agent read its SKILL.md directly; this pointer stays installed as the entry point.

    git clone --depth=1 https://github.com/j-clegg/service-blueprint-skill.git ~/.agents/service-blueprint-skill

Heads-up

  • License: MIT
  • Name collision: service-blueprint is also written by designer-skills (its install or its catalogue pointer); installing both overwrites the earlier one.
<!-- das:install:end -->

Invoke after install

  • Read ~/.agents/service-blueprint-skill/SKILL.md and follow it; it points to METHODOLOGY.md, SCHEMA.md and RENDERING.md in the same folder
  • Trigger phrases: "service blueprint", "service design blueprint", "frontstage backstage", "service delivery map"

What it does

A service-blueprint package: sourced methodology (METHODOLOGY.md), a machine-readable blueprint schema (SCHEMA.md), and an HTML/Mermaid output pipeline (RENDERING.md) with example blueprints and a stylesheet. Maps user actions, frontstage, backstage, and support processes across the lines of interaction, visibility and internal interaction, with timed facilitation and moments-of-truth analysis. Follows methodology from Nielsen Norman Group, the UK Government Digital Service and Practical Service Design.

When NOT to use

  • Single-user emotional journey only → use a journey-map skill
  • High-level UX strategy → use design-consultation
  • You want a skill the skills CLI can install and register by name → use designer-skills, whose service-blueprint skill is a lighter take on the same method

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free