aria-knowledge
claudecodexKnowledge management, decision discipline, codebase understanding, plan pre-mortems, and release retrospectives for Claude Code
40 skills · 12 MCP servers · hooks
Knowledge management for Claude Cowork — capture, organize, and apply durable knowledge across your work, available in any project workspace via a persistent folder grant. Companion to aria-knowledge for Claude Code; both share one knowledge folder so insights flow between conversational and engineering work. Default knowledge folder.
Not in a marketplace yet, so it loads for one session with --plugin-dir.
Plugin aria-cowork in mikeprasad/aria-knowledge. Commands read from the repo's manifest — 5 days ago.
clip-threadCapture a chat or email thread from a connected MCP to the knowledge intake. Use when user says "/aria-cowork:clip-thread" or "archive this conversation". Pulls thread content from ~~chat (Slack, Teams) or ~~email (Gmail, MS365) MCP into intake/clippings/ for review. (Cowork variant — namespaced-onl
clipSave a URL or text snippet to the knowledge intake for later review. Use when user says "/aria-cowork:clip" or "/aria-cowork:save". Quick capture without leaving the session — clipped items are reviewed at the next /aria-cowork:audit-knowledge run. (Cowork variant — namespaced-only.)
extract-docPull insights from a single doc or page (Notion, Google Doc, Confluence, etc.) into the standard intake backlog. Use when user says "/aria-cowork:extract-doc", "extract insights from this doc", "pull learnings from this page", "mine this Notion page for knowledge", "extract from this Confluence". Di
aria-setupConfigure aria-cowork on first run or after updates. Verifies your knowledge folder is reachable from this Cowork session, guides you through adding it to claude_desktop_config.json for persistent multi-session access if needed, scaffolds the folder structure, and writes the canonical aria-config.md
askResearch a question, check existing knowledge first, draft a knowledge doc from the answer, and save directly to the appropriate category. Use when user says "/aria-cowork:ask", "ask about", "research and save", "I want to learn about", "what is the pattern for". Skips backlogs — the user reviews th
audit-configAudit project configuration and documentation for drift, staleness, and broken references. Use when user says "/aria-cowork:audit-config", "/aria-cowork:config-audit", "config audit", "docs audit", "check setup", "audit configs", "review CLAUDE.md files", or at the first aria-cowork skill invocation
audit-knowledgeScan the attached knowledge folder for extractable items, run idea-routing dispositions, archive cleared content, and rebuild the index. Triggers — "/aria-cowork:audit-knowledge", "/aria-cowork:knowledge-audit", "audit knowledge", "scan intake". (Cowork variant — namespaced-only.)
backlogView and manage pending backlog items. Use when user says "/aria-cowork:backlog", "/aria-cowork:backlog insights", "/aria-cowork:backlog clear", "what is pending", "show backlogs", "check backlog status". (Cowork variant — namespaced-only.)
contextLoad relevant knowledge by topic. Queries the tag index and presents matching promoted files for selective loading into context. Use when user says "/aria-cowork:context stripe", "/aria-cowork:context api pagination", "/aria-cowork:context architecture", "load knowledge about...", "what do we know a
daily-auditFirst-message audit substitute for Cowork. Use when user says "/daily-audit", "/aria-cowork:daily-audit", "audit check", "daily check", "session start audit", or at the start of a Cowork session to surface audit-cadence status. Cowork has no SessionStart hook (per ADR-004); this skill is the manual
digestCross-tool rollup of what is pending, what shipped, and what is blocked across chat / email / project tracker / docs. Use when user says "/aria-cowork:digest", "weekly digest", "cross-tool rollup", "what is pending across my tools", "summarize this week", "standup digest". Probes all 4 ~~categories
extractExtract uncaptured knowledge from the current conversation before it is lost to compaction. Use after completing a task, before switching context, before large exploratory work (multi-file reads, codebase scans), or when the user signals session end. Trigger: "/aria-cowork:extract", "extract knowled
foundational-reviewFoundational review before an irreversible decision (freeze, format/schema/spec tag, public flip, major re-scope): verdict + premises + A–F + irreversibility inventory → design spec → plan → /prospect. Requires a named decision (else redirects). (Cowork variant — namespaced-only; no subagents.)
handoffPassoff package — for future-you (restart) or a coworker (brief mode). Default/auto emit a next-session opener + PROGRESS/CLAUDE/memory + a commit message + "/aria-cowork:extract"; brief = 80-150 word coworker prose; snap defers /extract via a snapshot. Done-with-no-passoff → "/aria-cowork:wrapup".
helpShow available aria-cowork commands. Use when user says "/aria-cowork:help", "aria help", "what commands are available", "list commands", "what can aria-cowork do". (Cowork variant — namespaced-only.)
indexRebuild the knowledge tag index. Scans promoted files, normalizes tags, flags untagged files, suggests freeform-to-known promotions, detects stale files, and regenerates index.md. Use when user says "/aria-cowork:index", "rebuild index", "update index", "reindex knowledge". (Cowork variant — namespa
intakeCapture knowledge into the intake tree, dispatching by input shape — a bare URL or text snippet clips whole; "extract {src}" decomposes it into the backlogs; "doc {src}" captures one doc via a 5-section template; "thread {id|url}" pulls a Slack/Teams/Gmail conversation via MCP; files/dirs/globs bulk
interviewELICIT knowledge by interviewing the user, then stage to intake/ for manual review (elicit-side counterpart to /extract /intake /clip). Modes: 'project' (scope a build), 'knowledge' (a topic into the KB), 'deep-dive' (rationale behind something you built — needs a basis). Use when user says '/aria-c
meeting-notesFold a meeting transcript or notes into structured intake. Use when user says "/aria-cowork:meeting-notes", "capture meeting notes", "fold this meeting transcript", "process this Granola export", "archive this standup". Accepts a ~~docs URL (Notion, Confluence) OR pasted transcript text. (Cowork var
prospectStructured pre-mortem on a plan BEFORE execution: per-step risk verdicts (PROCEED/SHRINK/SPLIT/DEFER/KILL), evidence-sourcing pass, simpler-alternative discipline, growing failure-mode library. Triggers — "/aria-cowork:prospect", "pre-mortem this plan". (Cowork variant — namespaced-only.)
readiness-auditIs it clean/legal/consistent to ship for THIS event? Surface-audit sibling of /foundational-review: sequential probes → re-verify load-bearing claims → tiered findings (Tier 0/High/Med/Low) → phased remediation. Read-only; no anchor needed. (Cowork variant — namespaced-only; no subagents.)
retrospectStructured retrospective on a shipped commit range, release, PR, commit, or session: per-fix validation, evidence-sourcing pass, re-diagnosis, action verdicts, growing failure-mode library. Triggers — "/aria-cowork:retrospect", "retrospect this". (Cowork variant — namespaced-only.)
rulesQuick lookup into working rules. Use when user says "/aria-cowork:rules", "/aria-cowork:rules 22", "/aria-cowork:rules dependencies", "look up rule about...", "what rule covers...", or references a specific rule number. (Cowork variant — namespaced-only.)
snapshotSave a snapshot of the current Cowork conversation to the knowledge intake on demand. Use when user says "/aria-cowork:snapshot", "snapshot the session", "save this conversation", "capture the transcript", "archive this session". Schema-identical to aria-knowledge''s /snapshot output, but with cowor
statsShow knowledge base health metrics — file counts, backlog depth, audit status, tag stats, and coverage gaps. Use when user says "/aria-cowork:stats", "knowledge stats", "how is my knowledge base", "show stats", "knowledge health", "dashboard". (Cowork variant — namespaced-only.)
sync-decisionsMirror approved decisions from the knowledge folder out to a connected ~~docs MCP (Notion, Confluence, Google Docs). Use when user says "/aria-cowork:sync-decisions", "mirror decisions to Notion", "push decisions to wiki", "sync ADRs to Confluence", "export decisions externally". WRITE-side skill —
wrapupClose out cleanly when work is done — no passoff. Updates PROGRESS/CLAUDE/memory, emits a commit message, runs "/aria-cowork:extract". Not for passoff (use "/aria-cowork:handoff"). Triggers — "/aria-cowork:wrapup" (auto|snap), "wrap up", "I am done", "close out", "end session". (Cowork variant — nam
slackconnects to: https://mcp.slack.com/mcp
ms365connects to: https://microsoft365.mcp.claude.com/mcp
gmaillinearconnects to: https://mcp.linear.app/mcp
asanaconnects to: https://mcp.asana.com/v2/mcp
atlassianconnects to: https://mcp.atlassian.com/v1/mcp
mondayconnects to: https://mcp.monday.com/mcp
clickupconnects to: https://mcp.clickup.com/mcp
notionconnects to: https://mcp.notion.com/mcp
boxconnects to: https://mcp.box.com/
egnyteconnects to: https://mcp.egnyte.com/mcp
google docsKnowledge management, decision discipline, codebase understanding, plan pre-mortems, and release retrospectives for Claude Code
40 skills · 12 MCP servers · hooks
Validation probe for aria-cowork. Tests whether a Cowork plugin can read and write the user-attached knowledge folder, verifies bidirectional access with aria-knowledge in Code, and (v0.2.0) tests whether Cowork can read the existing aria-knowledge config at ~/.claude/aria-knowledge.local.md when ~/.claude/ is attached as an additional workspace folder. Install once, run /aria-probe, uninstall.
1 skill
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.