// Query standard operating procedures relevant to your current context or task.
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).
Author or update a custom SOP (a reusable procedure / playbook) for your team.
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 | Get SOPs |
| description | Query standard operating procedures relevant to your current context or task. |
| version | 1.0.0 |
| category | system |
| skillType | claude-skill |
| assignableRoles | ["developer","qa","tpm","designer","frontend-developer","backend-developer","fullstack-dev","qa-engineer","product-manager","architect","generalist","sales","support"] |
| triggers | ["get sops","standard procedures","how to","best practices"] |
| tags | ["system","sops","procedures","guidelines"] |
| execution | {"type":"script","script":{"file":"execute.sh","interpreter":"bash","timeoutMs":15000}} |
Query standard operating procedures (SOPs) relevant to your current context or task. SOPs contain team-defined guidelines, workflows, and best practices.
| Parameter | Required | Description |
|---|---|---|
context | Yes | Description of what you need SOPs for (e.g., "deploying to production") |
category | No | Filter by SOP category (e.g., "deployment", "testing", "code-review") |
role | No | Filter by role relevance (e.g., "developer", "qa") |
sessionName | No | Your session name. Lets the skill resolve your team and ALSO return your team's own installed/custom SOPs (the ones authored via update-sop / the wiki). |
teamId | No | Explicit team id (skips the sessionName lookup). |
The result includes both the global SOPs and — when your team is resolved — a Team SOPs section from your team's library (~/.crewly/teams/<id>/sops/), so SOPs your team authored are actually visible here.
bash config/skills/agent/core/get-sops/execute.sh '{"context":"publishing an XHS post","category":"marketing","sessionName":"crewly-marketing-ella"}'
JSON with matching SOPs including their titles, content, and applicability metadata, plus a Team SOPs section when a team is resolved.