Eleven role packs turn Claude instructions into installable units
The root README lists 11 plugins for productivity, sales, customer support, product management, marketing, legal, finance, data, enterprise search, bio-research, and plugin management. A pack can contain a manifest, an MCP configuration, slash commands, reusable skills, and sub-agents. This is more useful than a folder of loose prompts because Claude Cowork and Claude Code know when to activate skills and how to expose named commands such as call preparation or query writing.
The repository's best idea is packaging a whole job rather than one clever instruction. The sales pack can pair research and outreach workflows with CRM connectors. The finance pack covers journal entries, reconciliations, statements, close work, and audit support. Bio-research reaches literature and laboratory systems. Those descriptions are broad, but the README is candid about their status: all 11 are generic starting points that become useful after a company adds its terminology, tools, and process rules.
Two Claude Code commands install a pack, then configuration begins
The documented Claude Code path uses 2 commands: one adds anthropics/knowledge-work-plugins as a marketplace, and the other installs a named plugin. Cowork users can install from Claude's plugin directory. Once present, relevant skills activate automatically and slash commands become available. That is a short installation path for the file-based portion of the product, and the Apache-2.0 repository license leaves room for internal edits and redistribution under its terms.
Installation is only the first boundary. MCP connectors point Claude at services such as Slack, Notion, HubSpot, Jira, BigQuery, and Microsoft 365. Each chosen service brings its own account, authorization, and data-access decision. The README tells teams to edit .mcp.json, add company context, and adjust workflows. A legal or finance pack needs more than valid JSON: someone qualified must decide which sources Claude may read, which actions it may take, and who reviews the result.
What happened when we ran it
Our sandbox targeted bio-research/skills/instrument-data-to-allotrope at commit a6d8653 because that directory contains an installable Python project. Installation succeeded in 18 seconds, adding 35 packages and taking 37 MB on disk. The build completed in 4 seconds. Pip-audit reported 0 known vulnerabilities in the installed set. The environment was an unprivileged Debian container with 3 CPUs, 8 GB of RAM, Python 3.12, and no secrets.
There was no test script or target, so the test step was skipped. The 6.9 MB checkout held 1,137 files and about 9,921 lines of source. Our scan found 6 CI workflow files, no Dockerfile, and no tests directory. These results verify that one nested skill's dependencies installed and its build completed. They do not verify all 11 role packs, Claude's skill activation, any remote MCP connection, or the correctness of work produced through those instructions.
One Python skill makes the no-code description too broad
The README says every component is Markdown and JSON with no code or build steps. Our 4-second build found a meaningful exception inside the bio-research plugin. Its instrument-data-to-allotrope skill includes Python scripts for converting laboratory files to Allotrope Simple Model JSON, flattening output to CSV, exporting parser code, and checking the result. Its requirements pin allotropy, pandas, openpyxl, and pdfplumber, which account for the 35 packages installed in our run.
That skill also labels itself an example and tells adopters to customize schemas, ontology mappings, and proprietary instrument formats. Its validator uses a December 2024 Allotrope specification and can treat unknown values as warnings unless strict mode is selected. Those details are sensible, yet they raise the review burden. A scientist should confirm instrument support and field mappings, while a data engineer should inspect generated parser code before it enters a production pipeline. The missing test target leaves those checks to the adopter.
Open issue 933 matches blank URLs in the current sales pack
Issue 933 reports 24 blank Gmail and Google Calendar connector entries across 12 plugin manifests at commit be9c0da. The current sales/.mcp.json still gives both services empty URLs. According to the report, Claude Code registers those entries and then shows connection failures with no endpoint to reach. The issue describes cache editing or disabling the whole plugin as the available workarounds. That is specific friction in a collection whose value depends heavily on connected services.
A separate open report, issue 1031, says Gmail, Google Calendar, and Slack are redeclared per plugin, which can force repeated authorization when several packs use the same account. We did not run authenticated connectors in our no-secret sandbox, so these are issue findings rather than lab reproductions. Administrators should install one pack first, inspect claude mcp list, and settle connector ownership before handing several role plugins to a department.
A September 12 push shows activity despite no release feed
GitHub recorded the last push on September 12, 2026, along with 23,981 stars and 77 combined issues and pull requests. GitHub issue search returned 68 actual open issues. The latest-release endpoint returned 404, so there is no current GitHub release tag to cite. That absence complicates version pinning, but it does not signal abandonment when code moved on the same day and users were filing concrete reports during the preceding week.
Anthropic Skills is the closer choice when you want individual skills without an 11-role package. The MCP Servers repository suits teams that mainly need reference tool connections and will author their own operating instructions. Wshobson's Agents is aimed more at coding work and supports several agent hosts. Knowledge Work Plugins is strongest inside a Claude-only organization that has owners for permissions, prompt review, and output review. The 18-second nested install is easy; making each role reflect the company is the actual project.