Knowledge Work Plugins: give a work assistant a shared task file
Try productivity with one task and one known abbreviation
Create an inspectable first result, preserve existing memory and distinguish a missing connector from a file-editing problem.
What you will learn
- Prepare an isolated working folder
- Exercise the smallest useful loop
- Finish with a reversible edit
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
- Existing CLAUDE.md files need protection.
- A command being listed does not prove connector authorization.
- The first result should be checked in the file.
Prepare an isolated working folder
Use a new folder without an existing CLAUDE.md. That filename may already contain important project instructions elsewhere; do not replace it with a memory template. Keep the first trial independent of a production repository or personal document archive.
The root README documents adding the marketplace and installing a named plugin. Its productivity README shows an older-looking alternative installation spelling. Start from the root marketplace flow, inspect the host’s command list and confirm the installed productivity plugin before continuing.
Exercise the smallest useful loop
The task skill refers to /productivity:start and the shared TASKS.md file. Initialize in the disposable folder, add one fictional task and read the resulting Markdown. Check the title, owner and due date against the request instead of accepting a plausible-looking card.
Add an invented abbreviation with one unambiguous meaning, then ask what it means. If the response is wrong, inspect CLAUDE.md and memory/glossary.md. This separates missing stored context from a model that misinterprets context already present.
Finish with a reversible edit
Mark the fictional task complete and confirm the checkbox and destination section in the file. Keep a copy before testing board edits, because dashboard serialization is designed for its task format rather than arbitrary Markdown documents.
If browser file access is unavailable, use the Markdown file for the trial and record the dashboard limitation. Stop before comprehensive account scanning. To undo the exercise, restore the saved demo files and disable only the plugin installed for this trial.
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
Install productivity from the reviewed marketplace and confirm the host command list.
- 2
Initialize a fresh folder and add one fictional task.
- 3
Check completion in TASKS.md, then restore the saved demo if needed.
Copy-ready example
claude plugin marketplace add anthropics/knowledge-work-plugins
claude plugin install productivity@knowledge-work-pluginsFrequently asked questions
Why does my command differ from the README?
The repository contains differing examples. Inspect the installed host and plugin command list; do not assume every spelling works everywhere.
What if the dashboard cannot open the file?
Continue the file-only exercise and investigate browser file-access support separately.
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