// Author or update a custom SOP (a reusable procedure / playbook) for your team.
List the recurring cron tasks the orchestrator has scheduled FOR you — call before self-scheduling so you don't create duplicates that fire N× reports.
Schedule a future check-in that creates a WorkItem for you or another agent at a specific time (one-shot or bounded recurring).
Query standard operating procedures relevant to your current context or task.
Read your team's norms (operating agreements — canDelegate, escalation, rules of engagement) relevant to the current moment.
Propose or update a team norm (an operating agreement — canDelegate, escalation, rules of engagement) for your team.
Decompose a parent Mission (OKR) into child OKRs one cascade tier down (company→team→project) as a PROPOSAL. The runtime drafts the child objectives + Key Results; the skill submits them to the backend as pending_approval. Children are NOT active until the human owner approves. Output includes an [APPROVE] block naming the parent and proposed children for the owner's decision.
| name | Update SOP |
| description | Author or update a custom SOP (a reusable procedure / playbook) for your team. |
| version | 1.0.0 |
| category | system |
| skillType | claude-skill |
| assignableRoles | ["team-leader","tpm","product-manager","architect","generalist","developer","qa","qa-engineer","backend-developer","frontend-developer","fullstack-dev"] |
| triggers | ["update sop","write a sop","document the procedure","create a playbook","standardize how we"] |
| tags | ["system","sops","procedures","team"] |
| execution | {"type":"script","script":{"file":"execute.sh","interpreter":"bash","timeoutMs":15000}} |
Create or update a custom SOP for your team — a reusable procedure /
playbook for how to do a class of work (e.g. "publishing an XHS post",
"running a release"). The SOP is written into the team's own SOP store
(~/.crewly/teams/<id>/sops/) and surfaces in the wiki under the team's
SOPs folder, alongside SOPs installed from the catalog. The owner can edit
it in the wiki UI.
Use this for durable, repeatable procedures — not one-off task notes (use the
wiki/memory) and not team governance rules (those are team norms — use
update-team-norm). Prefer installing an existing catalog SOP when one fits;
author a custom SOP only when the team needs something the catalog lacks.
| Parameter | Required | Description |
|---|---|---|
sopId | Yes | Stable kebab-case id / filename, e.g. "xhs-posting". |
content | Yes | The SOP body (markdown). The steps/procedure. |
title | No | Human title, e.g. "XHS Posting Checklist". Required when creating. |
category | No | Optional sub-folder, e.g. "common", "marketing". |
append | No | "true" to append to an existing SOP instead of overwriting. |
teamId | No | Team to write to. Defaults to the team resolved from sessionName. |
sessionName | No | Your session name, used to resolve the team when teamId is omitted. |
updatedBy | No | Who authored the change (your agent/session name). |
bash config/skills/agent/core/update-sop/execute.sh '{"sopId":"xhs-posting","title":"XHS Posting Checklist","category":"marketing","content":"1. Draft hook.\n2. Add 3-5 tags.\n3. Post 7-9pm."}'
JSON { success, action: "created" | "updated", sopId, title, category, path, relativePath }.