Knowledge Work Plugins: give a work assistant a shared task file
Deploy Knowledge Work Plugins as a host configuration
Plan a versioned plugin rollout with file backups, connector approval and an explicit rollback instead of inventing a Docker service.
What you will learn
- Pin what the team actually uses
- Approve connectors individually
- Keep rollback at the file boundary
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
- A plugin rollout is not a new container service.
- Empty connector URLs need explicit resolution.
- Plugin removal and account revocation are separate.
Pin what the team actually uses
The deployment unit is a plugin installed into a compatible host, plus the workspace files it reads and changes. Record the plugin revision and host version. Updating marketplace content can change instructions even when the local task document remains unchanged.
For a pilot, retain a reviewed copy or release reference and document the installation method supported by the host. Do not assume the marketplace command itself pins ebd7990c. The commit here identifies our research snapshot, not a guarantee about a later install.
Approve connectors individually
The inspected productivity .mcp.json lists HTTP endpoints for several work services. Its Gmail and Google Calendar URL values are empty. An entry in this file therefore cannot be counted as a functioning integration or a completed deployment.
Use one approved test account and one connector at a time. Inspect the actual authorization scopes and host prompts, and test a harmless read before allowing writes. The README’s category list is not an authoritative inventory of authenticated services in your environment.
Keep rollback at the file boundary
Back up TASKS.md, CLAUDE.md and memory/ before changing plugin versions. Stop concurrent agent and board edits during the transition. Restore a tested plugin version and file snapshot together if the new instructions or serializer produce unwanted changes.
Disabling a plugin does not necessarily revoke an external account grant or remove retained workplace data. Track those separately in the rollout record. This is a deployment design based on inspected files, not a completed organizational rollout.
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
Record the host version, plugin revision and workspace location.
- 2
Validate one approved connector without enabling broad scans.
- 3
Preserve the previous plugin and memory snapshot for rollback.
Copy-ready example
{
"rolloutProposal": true,
"hostVersion": null,
"pluginRevision": "ebd7990cfa9495937da7726741e1ee6a96788565",
"approvedConnectors": [],
"backup": [
"TASKS.md",
"CLAUDE.md",
"memory/"
],
"liveConnectorTested": false
}Frequently asked questions
Are all listed services ready after installation?
No. Endpoint configuration, host support and account authorization must each be checked.
What belongs in a backup?
The task file, working memory, deep memory and the exact plugin version used to interpret them.
Sources
- Knowledge Work Plugins / README.mdSource checked 2026-09-18
- Knowledge Work Plugins / productivity/README.mdSource checked 2026-09-18
- Knowledge Work Plugins / productivity/.mcp.jsonSource checked 2026-09-18
- Knowledge Work Plugins / productivity/skills/task-management/SKILL.mdSource checked 2026-09-18