cipher

Convert informal business communications into structured SOPs and process diagrams.

1|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/motorthings/clode --skill cipher-motorthings
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cipher
Source: https://github.com/motorthings/clode/tree/main/skills/cipher
Command: npx skills add https://github.com/motorthings/clode --skill cipher-motorthings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts unstructured business communications like meetings, transcripts, emails, and chat logs into clear, structured process documentation so teams can align and execute consistently.

Core Features & Use Cases

  • Process extraction: Identifies core steps, decisions, roles, dependencies, and gaps from informal inputs.
  • Why-first analysis: Surfaces internal and external objectives (what the process achieves and why it matters).
  • Actionable deliverables: Produces SOPs, process summaries, analysis reports, and process diagrams (e.g., Mermaid/flowcharts/BPMN-oriented maps).
  • Operational readiness: Adds exception handling guidance and clarifying questions when information is ambiguous or contradictory.

Quick Start

Provide the meeting transcript and ask: Generate an SOP and a Mermaid process map for this process, including decision points, roles, dependencies, and exception handling.

Frequently Asked Questions about cipher

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an SOP from a meeting transcript?

Process mapping from chat logs identifies core steps, decisions, and gaps from informal inputs. It surfaces internal and external objectives to produce structured process summaries, analysis reports, and Mermaid diagrams for operational clarity.

Can I create Mermaid diagrams directly from email threads?

Converting unstructured business communications into process documentation is needed when teams require alignment and consistent execution. It transforms informal inputs like chat logs and transcripts into structured SOPs, resolving operational ambiguities and contradictions.

How do I extract decision points and roles for process documentation?

Workflow optimization from informal inputs works by applying why-first analysis to surface process objectives. It transforms unstructured communications into structured documentation by extracting sequence steps, decisions, roles, and dependencies while adding exception handling guidance.

What is the best way to standardize business communications into process maps?

Handling ambiguities in process descriptions involves asking targeted clarifying questions when information is contradictory. This ensures the generated SOPs and process maps maintain operational readiness and accurately reflect exception handling guidance.

Does process mapping from chat logs work for workflow optimization?

Generating SOPs from business communications requires no specific prerequisite environment or dependencies. You simply provide informal inputs like meeting transcripts or email threads to extract process steps, roles, and decisions for standardization.

Why does workflow optimization from informal inputs require exception handling?

Handling ambiguities in process descriptions involves asking targeted clarifying questions when information is contradictory. This ensures the generated SOPs and process maps maintain operational readiness and accurately reflect exception handling guidance.