Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    SOP & Process Documentation

    1

    When that person is out sick, goes on vacation, or leaves, the work stalls.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    SOP & Process Documentation

    SOP & Process Documentation

    Example session with this skill installed

    Write an SOP for [how we onboard a new client]. Here are my rough notes: [send welcome email, send contract, collect deposit, add them to our project tool, book the kickoff call]. Our [account manager] does this every time we sign a client.

    • Read your context and instructions
    • Compiled the sop & process

    Here's your SOP as a step-by-step procedure, since onboarding follows the same path every time.

    STANDARD OPERATING PROCEDURE

    PROCESS NAME: New Client Onboarding
    VERSION: 1.0
    EFFECTIVE DATE: [Date]
    NEXT REVIEW DATE: [Date, 6 months from now]
    DOCUMENT OWNER: Account Manager

    PURPOSE
    Makes sure every new client is set up the same way, so nothing is missed between signing and the first project meeting.

    SCOPE
    Applies to every new client, from the moment they say yes until the kickoff call is booked.

    TRIGGER / WHEN TO START THIS PROCESS
    A client confirms they want to work with us.

    REQUIRED BEFORE YOU BEGIN

    • Access to the shared inbox
    • The current contract template
    • Access to the invoicing tool and the project tool

    ROLES

    • Account Manager: owns every step below
    StepActionWhoDeadline
    1Send the welcome emailAccount ManagerWithin 24 hours of the yes
    2Send the contractAccount ManagerSame day as step 1
    3Collect the depositAccount ManagerWithin 2 business days of the signed contract
    4Add the client to the project toolAccount ManagerSame day the deposit clears
    5Book the kickoff callAccount ManagerWithin 5 business days of the deposit

    STEP 1: Send the welcome email
    Who: Account Manager
    What to do: Send the welcome email template from the shared inbox.
    Expected output: Welcome email in the client's inbox.
    ⚠️ Common error: Sending it from a personal inbox, so the team can't see the thread. Always use the shared inbox.

    STEP 2: Send the contract
    Who: Account Manager
    What to do: Fill in the contract template with the client's details and send it for signature.
    Expected output: Contract sent and waiting for signature.
    ⚠️ Common error: Using an old template. Always start from the current version.

    STEP 3: Collect the deposit
    Who: Account Manager
    What to do: Send the deposit invoice once the contract is signed.
    Expected output: Deposit paid.
    ⚠️ Common error: Starting work before the deposit clears.

    STEP 4: Add the client to the project tool
    Who: Account Manager
    What to do: Create the client's project and add their contact.
    Expected output: Project created with the client added.

    STEP 5: Book the kickoff call
    Who: Account Manager
    What to do: Send a scheduling link and confirm the time.
    Expected output: Kickoff call on the calendar.

    DEFINITION OF COMPLETE
    The contract is signed, the deposit is paid, the project exists in the project tool, and the kickoff call is booked.

    ESCALATION
    If the client hasn't signed within 5 business days, tell the business owner.

    VERSION HISTORY

    VersionDateAuthorChanges
    1.0[Date]Account ManagerFirst version

    New team members: Follow this SOP exactly for your first three onboardings, then suggest improvements.

    Next steps

    1. Have your account manager read it and correct anything that doesn't match how they work.
    2. Fill in the dates and save it where your team keeps its documents.

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

    About this skill

    The problem

    Most small teams run on processes that live in one person's head. When that person is out sick, goes on vacation, or leaves, the work stalls. Writing an SOP feels like a big chore, so it never gets done, or it gets written so vaguely that nobody can follow it.

    What it does

    • Takes your process in whatever form you have it: rough notes, bullet points, a voice memo transcript, or a plain description.
    • Asks for useful extras if you have them: who does the process, how often it happens, what starts it, what "done" looks like, and any compliance requirements.
    • Writes your SOP in one of three formats:
      • Step-by-step procedure for processes that always follow the same path.
      • Decision tree for processes with "if this, then that" choices.
      • Checklist for quality checks and recurring tasks.
    • Picks a format for you if you don't choose one.
    • Includes a full header with version number, effective date, next review date, and document owner, plus purpose, scope, trigger, what you need before you begin, and the roles involved.
    • Gives each step a person responsible, clear instructions, the expected result, and a note on the most common mistake.
    • Ends with a definition of complete, who to contact when something goes wrong, related documents, a version history, and a note for new team members.
    • Suggests how often to review the SOP based on how often the process runs.

    Why it beats prompting it yourself

    A quick prompt often gives you a vague list like "handle the order" or "check everything." This skill starts every step with an action verb, replaces fuzzy phrases like "as soon as possible" with specifics like "within 24 hours," and uses role titles instead of names so the SOP still works after someone leaves. In a decision tree, every question has a path for every answer. Every SOP says exactly what "done" looks like and what to do when something goes wrong.

    Use cases

    • A client onboarding process for a service business.
    • A weekly inventory count for a shop.
    • A decision tree for handling customer complaints, returns, or refunds.
    • An end-of-day closing checklist.
    • An employee offboarding procedure.

    Known limitations

    • It writes from what you tell it. It can't see your software or watch the process, so have the person who does the job review the steps.
    • It notes any compliance needs you mention, but it doesn't check your process against laws or regulations. It isn't legal or compliance advice.
    • It writes the SOP as text in the chat, not as a Word or PDF file. Paste it into your document tool to save it.
    • Decision trees are drawn in text, not as image diagrams.
    • It creates one SOP per use.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Business & Operations.

    Writes from what you tell it and can't see your software, so have the person who does the job review the steps. It doesn't check processes against laws or regulations and isn't legal or compliance advice. The SOP comes as text in the chat, not a Word or PDF file, and decision trees are drawn in text. One SOP per use.

    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 buying a skill.

    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 7 days ago

    Permissions

    No special permissions declared or detected

    Listed1 month ago
    Updated7 days ago

    What's inside

    Frequently Asked Questions

    One skill file (SKILL.md) that you add to Claude. It was built and tested for Claude. There are no extra templates or files.

    Use a step-by-step procedure when the process always goes the same way, a decision tree when it depends on choices along the way, and a checklist when you just need to confirm everything got done. If you don't choose, the skill picks one for you.

    Yes, as text. Paste the transcript of your voice memo and it turns it into clean steps.

    No. It uses role titles like "Account Manager," so the SOP still works when people change jobs.

    Every SOP includes a version number, a next review date, and a version history table, plus a suggested review schedule based on how often the process runs.

    New in Business & Operations