Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    SOP Writer

    1

    Standardize messy process notes into rigorous, numbered SOPs with verifiable completion criteria.

    $10

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    SOP Writer

    SOP Writer

    Example session with this skill installed

    Turn this dump into an SOP named 'Server Patching' for the SysAdmin role. Trigger is 'Critical Security Bulletin'. As of 2023-10-27. Source: 'Login to portal, run update, check logs for 200 OK.'

    • Read your context and instructions
    • Compiled the sop writer

    I have processed the source dump and drafted the Server Patching SOP. I identified a gap regarding the specific portal URL which was not provided in the source.

    Server Patching SOP

    • SOP Name: Server Patching
    • Audience: SysAdmin
    • Trigger: Critical Security Bulletin
    • As Of: 2023-10-27
    • Owner Role: unresolved
    • Status: ready
    • Write Mode: draft

    Purpose

    Update servers in response to security bulletins.

    When this SOP applies

    Triggered by a Critical Security Bulletin for the SysAdmin role.

    When it does not apply

    (none)

    Roles

    RoleDutySource
    SysAdminExecute updates and verify logsbuyer paste

    Procedure

    1. SysAdmin: Login to portal.
      • Completion Criterion: Dashboard is visible. (Source: buyer paste)
    2. SysAdmin: Run update.
      • Completion Criterion: Progress bar reaches 100% or terminal returns to prompt. (Source: buyer paste)
    3. SysAdmin: Check logs for "200 OK".
      • Completion Criterion: Log entry with timestamp and "200 OK" status is present. (Source: buyer paste)

    Verification

    • Check: Server logs
    • Pass: Presence of "200 OK" status following the update command.
    • Actor: SysAdmin
    • When: immediately
    • Verification Source: source

    Exceptions

    (none)

    Gaps

    • unresolved actor: Owner role not specified in dump.
    • missing info: Specific portal URL was not named in the dump.

    Residual

    • mutated: no
    • invented: no

    Next steps

    1. Provide the specific portal URL to resolve the gap in the documentation.
    2. Review the completion criteria to ensure they match your local environment.
    3. Set write_mode=apply if you want this committed to your docs/sop.md.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The problem

    Process knowledge often lives in messy chat logs, meeting transcripts, or scattered notes. When these are turned into SOPs manually, editors often invent missing steps or include vague instructions like "ensure it looks good" that provide no real accountability.

    What it does

    • Transforms a single raw data dump into a strictly numbered procedure with checkable completion criteria.
    • Enforces a mandatory verification step with an observable pass/fail condition to ensure the process actually worked.
    • Identifies and logs "gaps" such as contradictions in the source, unresolved roles, or missing exceptions.
    • Strips out sensitive environment data like local file paths, vault IDs, and internal chat routing tokens.
    • Prevents "hallucinated" safety steps by refusing to add rollbacks or notifications not present in the source.

    Why this beats prompting it yourself

    Generic prompts often hallucinate "best practices" or legalistic language that wasn't in your notes. This tool uses a rigid 8-step execution logic that prioritizes source fidelity over helpfulness, ensuring you only document what is actually known while highlighting exactly where your process is broken.

    Use cases

    • Converting a recorded screenshare transcript into a technical runbook.
    • Formalizing "tribal knowledge" from a Slack thread into a version-controlled Markdown file.
    • Auditing existing procedures by diffing them against fresh execution notes.
    • Standardizing handoffs between roles by strictly mapping actors to imperative actions.

    Known limitations

    This skill handles exactly one procedure per run. It will not extract meeting minutes, write policy manuals, or generate weekly review templates.

    Processes one procedure at a time. Requires ISO dates. Does not handle HR/legal policy or multi-procedure files. Requires explicit approval before writing to a wiki.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 2 months ago

    Permissions

    Read Files
    Write Files
    Listed2 months ago

    What's inside

    Frequently Asked Questions

    The skill accepts raw data dumps including meeting transcripts, screen-share notes, and Slack threads, transforming them into structured Markdown SOPs with numbered steps and verifiable pass/fail criteria.

    Unlike generic prompts, this skill uses rigid logic to prevent "hallucinating" extra steps, instead flagging contradictions or missing information as specific 'gaps' for you to address manually.

    Yes, the skill is designed with a data-stripping layer that automatically identifies and removes sensitive information like local file paths, internal vault IDs, and specific routing tokens from the final output.

    The SOP Writer is compatible with most major LLM-based agents that support Markdown output and complex reasoning, and it integrates directly into your existing AI workflow via a standard API or skill-call.

    You receive the core logic for the 8-step execution engine, lifetime access to updates, and a template for the standardized Markdown output format.

    This skill is optimized for one procedure per run to maintain high fidelity; it is not intended for generating general policy manuals or summarizing meeting minutes.

    New in Business & Operations