Menu
Propose or update a team norm (an operating agreement — canDelegate, escalation, rules of engagement) for your team.
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.
Assign a task to a specific agent via the task management system. Use when the orchestrator needs to target a particular agent with a known task ID. For agents self-assigning the next available task, use accept-task instead.
Send a message to all active agent sessions, excluding the orchestrator. Use when the orchestrator needs to announce information or coordinate the entire team at once. For messaging a single agent, use send-message instead.
| name | Update Team Norm |
| description | Propose or update a team norm (an operating agreement — canDelegate, escalation, rules of engagement) for your team. |
| version | 1.0.0 |
| category | system |
| skillType | claude-skill |
| assignableRoles | ["team-leader","tpm","product-manager","architect","generalist","developer","qa"] |
| triggers | ["update team norm","propose a norm","set a team rule","we should always","going forward the team should"] |
| tags | ["system","norms","governance","team"] |
| execution | {"type":"script","script":{"file":"execute.sh","interpreter":"bash","timeoutMs":15000}} |
Create or update a team norm — a durable operating agreement for your team (who may delegate to whom, escalation paths, decision rights, rules of engagement, recurring conventions). Use this when a lasting team-wide rule emerges that future work should follow — not for one-off task notes (use the wiki/memory for those) and not for reusable procedures (those are SOPs).
Norms you write land in the team's norm store and surface in the wiki under the team's Team Norms folder, where the owner can review and edit them. Treat this as proposing a norm: keep it concise, state the rule and when it applies.
| Parameter | Required | Description |
|---|---|---|
normId | Yes | Stable kebab-case id / filename, e.g. "code-commit", "delegation". |
content | Yes | The norm body (markdown). State the rule and its rationale. |
title | No | Human title, e.g. "Code Commit Norm". |
trigger | No | When this norm applies, e.g. "before_commit", "before_delegate". |
append | No | "true" to append to an existing norm 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-team-norm/execute.sh '{"normId":"delegation","title":"Delegation","trigger":"before_delegate","content":"Leads may delegate to their own team only; cross-team work goes through the orchestrator."}'
JSON { success, action: "created" | "updated", normId, path }.