Email, calendars, task management, and automation (7.8K skills)
Read and write Mastodon: verify the account, list own posts and followers, publish toots with native scheduling, upload media. Trigger phrases: mastodon, toot, post to mastodon, fediverse.
The English summary is being prepared. Showing the original description.
Work with Notion: search pages, read page properties, query databases, create pages, append blocks, update page properties. Trigger phrases: notion, notion page, notion database.
The English summary is being prepared. Showing the original description.
Read and write n8n: list workflows, inspect and update them, list executions. Trigger phrases: n8n, workflows.
The English summary is being prepared. Showing the original description.
Read and manage Asana tasks: my tasks, task details, create tasks. Trigger phrases: asana, my tasks, task list, todo.
The English summary is being prepared. Showing the original description.
Read and manage Calendly: list scheduled events, event types, invitees, and availability schedules; cancel bookings. Trigger phrases: calendly, my meetings, scheduled events, cancel booking.
The English summary is being prepared. Showing the original description.
List ClickUp workspaces and tasks, and create tasks. Trigger phrases: clickup, clickup tasks, my clickup list.
The English summary is being prepared. Showing the original description.
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the codebase or domain is unfamiliar, the user will "know it when they see it", a reference implementation must be understood before porting, mid-build deviations from the plan need capturing, or a finished change needs buy-in or verified understanding before merge. Pairs with [write-spec](../write-spec/SKILL.md) — walk the quadrants to burn off fog before slicing, and feed the finished map into the spec.
The English summary is being prepared. Showing the original description.
When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).
The English summary is being prepared. Showing the original description.
Use Claude Code as an independent `claude -p` subagent when the user explicitly asks for Claude, wants a second-agent opinion from Claude, or asks to delegate a well-scoped task to Claude. Supports selecting `--model` and thinking/effort level with defaults of the current `opus` alias and `high`.
The English summary is being prepared. Showing the original description.
You are a member of a Commonly workspace — a shared space where humans and AI agents from any origin collaborate in pods (chat rooms with memory). Use this whenever you are connected to Commonly via the commonly_* MCP tools: to read what's happening, post, remember things across sessions, react, DM other agents, and work the task board. Load it the moment you see any commonly_* tool available.
The English summary is being prepared. Showing the original description.
Install or verify the oma CLI and its runtimes (bun, uv, serena) before any oma-* skill, agent, or workflow runs an `oma` command. Use when `oma` is missing from PATH, when a skill says to run `oma ...` and the shell reports "command not found", or on the first task in a fresh Cursor or Grok Bot workspace.
The English summary is being prepared. Showing the original description.
Configure development tasks, git hooks, CI/CD, or release automation. Use when creating or fixing a repository development workflow.
The English summary is being prepared. Showing the original description.
Automated multi-agent orchestrator that spawns CLI subagents in parallel, coordinates via MCP Memory, and monitors progress. Use for orchestration, parallel execution, and automated multi-agent workflows.
The English summary is being prepared. Showing the original description.
Use when setting up or optimizing developer workflows in a monorepo, managing mise tasks, git hooks, CI/CD pipelines, database migrations, or release automation. Invoke for development environment setup, build automation, testing workflows, and release coordination.
The English summary is being prepared. Showing the original description.
Turn product requirements into scoped tasks with dependencies and acceptance criteria. Use for implementation planning and prioritization.
The English summary is being prepared. Showing the original description.
Coordinate assigned specialist tasks and handoffs manually. Use when supervising a multi-agent project step by step.
The English summary is being prepared. Showing the original description.
Dispatch and supervise parallel specialist agents with durable task state. Use when automated multi-agent execution is requested.
The English summary is being prepared. Showing the original description.
Generate daily team intelligence brief by cross-referencing GitHub, Linear, Slack, PostHog, meetings, and braindumps with two-way Linear sync-back
The English summary is being prepared. Showing the original description.
Personalize COG for your workflow - creates profile, interests, and watchlist files with guided setup (run this first!)
The English summary is being prepared. Showing the original description.
Process meeting recordings and notes into structured decisions, action items, and team dynamics with intelligent noise filtering
The English summary is being prepared. Showing the original description.
Produce and continuously maintain ONE living review document for a multi-item session — a cockpit header (Progress checklist, Working folder, Context) plus per-item review cards that you approve or request changes on directly in the doc or side panel. Use whenever a session has multiple deliverables you need to review/approve (meeting-processing + planning, multi-ticket work, briefs with several drafts, any "do X, then plan/draft Y and Z"). The doc is the interaction surface: you edit it (or reply in chat) to approve/change; the agent keeps it live as work progresses.
The English summary is being prepared. Showing the original description.
Run one task through the V-model verification loop: CP-2 plan → CP-3 build → CP-3v component verify → CP-4 integration verify (full lane) → CP-5 acceptance. The worker never grades its own homework; evidence rows trace back to AC-n. Opt-in: invoke with /closed-loop or by asking for the closed loop, proper verification, or an evidence trail. Ordinary work does not run this.
The English summary is being prepared. Showing the original description.
INVOKE THIS SKILL when using subagents, task planning, or human approval in Deep Agents. Covers SubAgentMiddleware, TodoList for planning, and HITL interrupts.
The English summary is being prepared. Showing the original description.
Discovers and installs community skills from the public registry. Use when the user mentions a technology, framework, or task that could benefit from specialized skills not yet installed, asks 'how do I do X', 'find a skill for X', or starts work in a new technology area. Proactively suggest when the user's task involves tools or frameworks without existing skills.
The English summary is being prepared. Showing the original description.