Menu
Author or update a custom SOP (a reusable procedure / playbook) for your team.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Plan and create a NESTED team hierarchy (parent coordination team + per-stream child teams) for a complex multi-stream goal. Use INSTEAD of recommend-team/materialize-team when the goal names 2+ parallel work-streams (e.g. frontend + backend + DevOps). Onboarding-only.
Search the live web for a query and return ranked results (title, URL, snippet) as JSON. Works with no API key (DuckDuckGo HTML fallback) and uses the Brave Search API or SerpAPI automatically when BRAVE_API_KEY / SERPAPI_KEY is set. Any agent can call it for research, competitor analysis, market/trend lookups, fact-checking, finding sources to cite, or grounding a non-software goal (marketing, growth, commerce) in real-world information.
Transcribe a local audio (or video) file to text with timestamps using Whisper. Defaults to local whisper.cpp (free, offline, word/segment-level timestamps) and automatically falls back to the OpenAI Whisper API (whisper-1) when the local engine is not installed. Any agent can call it for meetings, podcasts, voice notes, interviews, or video audio tracks.
Accept and take the next available task from the task queue. Use when an agent is idle and ready to pick up the highest-priority unassigned task. For assigning tasks to specific agents, use assign-task instead.
Register the agent as active with the Crewly backend on startup. Use when an agent first launches and needs to join the team and become visible to the orchestrator. For confirming responsiveness after registration, use heartbeat instead.
Analyze git changes and produce a structured code review with automated checks for missing tests, debug statements, potential secrets, large changes, and dependency modifications. Use when reviewing staged changes, unstaged diffs, recent commits, or branch comparisons before submitting a pull request. For task-level quality gates, use check-quality-gates instead.
| 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 }.