View All guides Conversation skill · updated 2026-09-21
Maryland SBDC Toolkit

Skill guide

Transcript to SOP

Turn a process walkthrough into a repeatable Standard Operating Procedure a new consultant could follow.

For: Maryland SBDC consultants and staff
Maintainer: Brandon Mason
Source: the skill’s own instructions
What you getWhat you useSetupHow to useFAQ

Start here

What you get

Record someone explaining how they do a thing — intake, a Neoserra workflow, a reporting cycle — and this turns it into an operational playbook. It works in four passes: first an inventory of every distinct process in the transcript (trigger, owner, inputs, systems, outputs, handoffs, risks, open questions), then clarifying questions, then the SOPs themselves, then consultant-friendly artifacts like checklists.

The inventory-first rule is what stops a blended walkthrough from collapsing into one vague procedure.

Conversation skill. You start it by saying what you want; it asks for what it needs and hands back a deliverable in the same chat. Nothing to install beyond the plugin, nothing to configure.

What it never does

  • Never assumes policy — anything the transcript leaves unstated goes under Open Questions, not into an invented step.
  • In strict mode it will not invent a step or a field name at all; missing details become explicit gaps.

Step 1

What to have ready

Step 2

Setting it up

Getting it on your side

The skill is plain instructions, so it runs wherever you already work. Pick your row:

  1. Get the files: everything is in the public GitHub repository — the skills themselves, and the ready-to-install plugin file on the latest release. MIT licensed; no GitHub account needed to download.
  2. Claude desktop app: download sbdc-toolkit.plugin from the latest release, drag it into a chat, click Accept.
  3. ChatGPT: this skill is a plain Markdown file, not Claude-specific. Open skills/transcript-to-sop/SKILL.md, copy the whole file, and paste it into a ChatGPT Project’s instructions or a custom GPT. Same instructions, same outputs.
  4. Claude Code: /plugin marketplace add bwfnx/sbdc-toolkit then /plugin install sbdc-toolkit@maryland-sbdc

Your first conversation

Open a new chat and say:

Turn this walkthrough into an SOP.

It will ask for:

  • Clarifications on ambiguous steps, only after it has shown you the process inventory.

Step 3

How to use it

Say

Write an SOP from this transcript.Document this workflow so a new consultant could follow it.Strict mode — don't invent anything that isn't in the transcript.Give me the condensed version.

What comes back

  • Process inventory table — one row per distinct process, with Open Questions.
  • Clarifying questions, if any.
  • The SOPs — purpose, scope, roles, step-by-step, exceptions, handoffs, optional metrics to track.
  • Artifacts — checklists and quick-reference versions for daily use.

Then

  • Answer the open questions and ask it to revise; the SOP gets more exact each pass.
  • Ask for the condensed version to post somewhere visible.

Tips from the field

  • Record walkthroughs with the screen narrated ("now I click Counseling, then Add Session") — system names and field names are what make an SOP usable.

Questions people ask

FAQ

Meeting notes or a client email instead?
Meeting Notes for your file; Action Plan for the client.
It did something odd. Who do I ask?
Brandon Mason. Say which skill and what you said to start it; a screenshot of the reply helps.