Skip to content
Back to skills

Sop Authoring

ASecurity

Guide for authoring clean, modular agent SOPs (Standard Operating Procedures) and skills according to AI OS context principles.

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 3, 2026
ai-agentsgogitapi

Works with

  • api

Security analysis

A100/100

Scanned September 3, 2026

npx -y skills add raffaelefarinaro/ciaobot --skill sop-authoring --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Sop Authoring?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Sop Authoring
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/raffaelefarinaro-sop-authoring/badge)](https://www.skillsdirectory.com/skills/raffaelefarinaro-sop-authoring)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: sop-authoring
description: Guide for authoring clean, modular agent SOPs (Standard Operating Procedures) and skills according to AI OS context principles.
---

# SOP & Skill Authoring Guide

Use this skill when drafting new agent SOPs, custom skills, or operational instructions for Ciaobot background routines.

> Skills are local folders: place `skills/<name>/SKILL.md` (or validated zip) then `ciao sync-skills`; workspace git sync propagates to other devices. No GitHub fetch.

## Core AI OS Principles

1. **Partition Expertise vs. Situational Context**:
   - **System Expertise (SOP)**: Fixed domain rules, step-by-step procedures, required parameters, and failure recovery. Keep static and clean.
   - **Situational Context**: Fleeting parameters passed per turn (e.g. today's date, current project, active workspace). Never embed transient session details into the permanent SOP.

2. **Skill Budgeting & Size Limits**:
   - Keep `SKILL.md` under **15,000 bytes** to prevent context bloat and model degradation.
   - If instructions exceed budget, split reference data into a `references/` or `examples/` subfolder.

3. **Frontmatter Specification**:
   ```yaml
   ---
   name: skill-name-kebab-case
   description: Actionable, concise summary of what this skill does and when to invoke it.
   ---
   ```

4. **SOP Structure Template**:
   - **Goal & Overview**: What the SOP accomplishes.
   - **Prerequisites & Tools**: Required commands or APIs.
   - **Execution Workflow**: Step 1, Step 2, Step 3.
   - **Error Handling & Fallbacks**: What to do when an API or command fails.
   - **Verification**: How to confirm success.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…