Knowledge Work Plugins: give a work assistant a shared task file
Knowledge Work Plugins: give a work assistant a shared task file
Understand Anthropic’s plugin collection through its productivity workflow, including local tasks, workplace memory and optional external connectors.
What you will learn
- What the collection supplies
- Follow one commitment
- Read the revision, not the slogan
Before you start
- Basic command-line and configuration reading
- Ability to work in a disposable authorized environment
Design an independent parser preview that exposes unsupported Markdown and conflicting headings before a dashboard save.
Key takeaways
- The host provides model execution.
- The dashboard and agent share TASKS.md.
- Local files do not provide multi-user coordination.
What the collection supplies
Knowledge Work Plugins packages domain instructions and integrations for Claude Cowork and Claude Code. It includes role-specific workflows such as sales and data analysis. The productivity plugin provides a concrete starting point: keep commitments in TASKS.md and workplace terminology in local memory files.
The host supplies the model and tool execution. Installing the collection does not create a standalone assistant service or provide access to your email. A connector definition, successful account authorization and permission for a particular action are separate conditions.
Follow one commitment
Consider a fictional request to prepare a project brief by Friday. Record its owner and deadline in TASKS.md, then teach the assistant what the project abbreviation means. The dashboard presents the same tasks in a board; you can inspect the underlying file when a card looks wrong.
This is useful for an individual who wants editable, portable work context. A shared Markdown file alone does not supply enterprise access control, transactional multi-user editing or reliable external task synchronization. Those requirements need separate evaluation.
Read the revision, not the slogan
This series reviews commit ebd7990c. The root README describes the collection broadly as Markdown and JSON, but productivity includes an HTML dashboard with JavaScript. We therefore inspect that implementation instead of describing the whole collection as code-free.
The following chapters cover a file-only trial before external connections. No Cowork session or live connector was executed for this series. Source inspection supports the described file behavior; it does not measure how accurately a model extracts commitments.
Decision guide
| Criterion | Option A | Option B |
|---|---|---|
| Best when | You need predictable behavior and easy auditing | You need adaptive optimization and have reliable telemetry |
| Main risk | May leave performance on the table | Can become difficult to explain or debug |
Implementation steps
- 1
Choose a disposable folder and fictional work context.
- 2
Identify one commitment with an owner and deadline.
- 3
Compare the task file with the dashboard before connecting accounts.
Copy-ready example
TASKS.md
CLAUDE.md
memory/glossary.md
memory/people/
memory/projects/Frequently asked questions
Does the plugin include Claude access?
No. A compatible host and its own account permissions are required.
Must I connect email immediately?
No. The productivity README supports manual tasks and memory without connectors.
Sources
- Knowledge Work Plugins / README.mdSource checked 2026-09-18
- Knowledge Work Plugins / productivity/README.mdSource checked 2026-09-18
- Knowledge Work Plugins / productivity/skills/task-management/SKILL.mdSource checked 2026-09-18
- Knowledge Work Plugins / productivity/skills/memory-management/SKILL.mdSource checked 2026-09-18