Agent skill · operations · jeremylongshore
agency-os
Notion-as-source-of-truth dispatch board for running your work like an AI agency. One Tasks database is the source of truth; tasks flow Suggestion through Discussion, To-Do, In Progress, and Done with subtasks, recurring cadences, dependencies, and template subtrees. Batch execution fans approved To-Do rows out to parallel agents with per-task model selection. Use when capturing chat to Notion, running the To-Do queue, suggesting, approving, or discussing tasks, or coordinating multi-task batches. Trigger with "/agency-os" subcommands or natural-language variants ("add a suggestion: …", "let's discuss X", "run the queue").
Why this skill is useful
Adds a complete CLI interface for managing tasks in Notion with parallel execution capabilities that aren't available in public documentation.
What it needs
Requires @notionhq/notion-mcp-server, python3 installed locally. Requires notion account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
agency-os Notion-as-source-of-truth dispatch board. One Tasks database, one Hub page, one page per Corpus, one page each for General Guidance and Resources. The skill mutates Notion via the Notion MCP (mcpnotion- tools); only references/notion-pointers.json is committed to git. Skill name decision: the skill is named agency-os (matching the repo). All commands are /agency-os <cmd>. This is the single plugin entry point; there is no agency-os/notion sub-namespace. If you embed this plugin alongside others, prefix commands with agency-os to avoid collisions. Overview agency-os turns a single Notion database into a multi-status dispatch board for AI work. The model is intentionally narrow: One Tasks database is the source of truth for status, priority, model selection, and ownership. No parallel kanban tools. One Hub page holds the General Guidance, Resources, and Corpus pointers that every task consults. Tasks flow through five statuses: Suggestion → Discussion → To-Do → In Progress → Done. The dedup gate at each transition prevents accidental re-execution. run fans approved To-Do rows out to parallel agents. Each task carries its own model selection (Haiku for cheap fan-out, Sonnet for default, Opus for hard reasoning) and respects declared dependencies. The skill is stateless on disk — the only committed artifact is references/notion-pointers.json (database/page IDs). All runtime state lives in Notion. For the full architecture (status flow, sync protocol, workspace structure, pointer/cache format), see references/architecture.md. Prerequisites Notion MCP server installed: npx -y @notionhq/notion-mcp-server (declare in .mcp.json) Notion integration token (NOTIONTOKEN) with read+write access to your workspace. Add .env to .gitignore — never commit the token. A Notion Tasks database with the columns the skill expects (see references/architecture.md § "Workspace structure" for the schema). The /agency-os init command can scaffold this for you. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/agency-os--aa438c