operations

Team Toolkit

A plugin marketplace of shared agents and skills for your team, designed to run primarily in Claude Cowork (and also works in Claude Code).

This single repo hosts multiple plugins. Teammates add the marketplace once and then install only the plugins they need.

This repo is also a teaching demo for how to package agents and skills as Claude Code / Cowork plugins and distribute them via a marketplace.

What's inside

This marketplace ships two plugins:

operations

Daily operations agents and skills.

• moneypenny (agent) — always-on executive assistant for morning briefings, email triage, schedule prioritization, task delegation, and end-of-day reviews.

brand-tools

Brand and content skills.

• applying-brand-guidelines (skill) — applies James Gray / JamesGray.AI brand voice, tone, and messaging guidelines to any content.

Install

In Claude Cowork (primary)

Inside a Cowork session:

/plugin marketplace add jamesgray007/team-toolkit
/plugin install operations@team-toolkit
/plugin install brand-tools@team-toolkit

The first command adds the marketplace once (you'll authenticate with GitHub the first time, since the repo is private). After that, every plugin in this marketplace is one /plugin install away.

Note for students: Cowork can install plugins from GitHub but cannot push changes back. To add new agents/skills, edit locally (or via the GitHub web UI) and push from your own machine — then run /plugin update <plugin-name> in Cowork to pull the new version.

In Claude Code

Same commands work:

/plugin marketplace add jamesgray007/team-toolkit
/plugin install operations@team-toolkit
/plugin install brand-tools@team-toolkit

For local development, clone and add the directory as a marketplace:

git clone https://github.com/jamesgray007/team-toolkit.git ~/Code/team-toolkit

/plugin marketplace add ~/Code/team-toolkit
/plugin install operations@team-toolkit

Repo layout

team-toolkit/
├── .claude-plugin/
│   └── marketplace.json              # Marketplace catalog — lists every plugin
├── plugins/
│   ├── operations/
│   │   ├── .claude-plugin/
│   │   │   └── plugin.json           # Manifest for the operations plugin
│   │   └── agents/
│   │       └── moneypenny.md
│   └── brand-tools/
│       ├── .claude-plugin/
│       │   └── plugin.json           # Manifest for the brand-tools plugin
│       └── skills/
│           └── applying-brand-guidelines/
│               ├── SKILL.md
│               └── references/
└── README.md

Three layers, three names:

Layer	Name here	Purpose
GitHub repo	team-toolkit	Where the code lives
Marketplace	team-toolkit	The catalog teammates add once
Plugins	operations, brand-tools	The individual things teammates install

The repo and marketplace happen to share a name, but the plugins are distinct.

For students: from idea to plugin in 3 stages

You don't write a plugin from scratch. You start small in a .claude/ folder, prove the idea works, then promote it to a plugin when it's worth sharing.

Stage 1 — Personal scratchpad: ~/.claude/

The fastest way to try a skill or agent. Files in your home directory are loaded by Claude Code in every project on your machine — no setup, no config.

~/.claude/
├── agents/
│   └── my-helper.md
└── skills/
    └── my-skill/
        └── SKILL.md

Use this when: you're experimenting and don't yet know if the agent/skill is even useful.

Stage 2 — Project-scoped: .claude/ in a repo

When the skill/agent is tied to a specific project (e.g., a codebase or workflow), put it in that project's .claude/ folder and commit it. Teammates who clone the repo get it automatically when they work in that directory.

my-project/
├── .claude/
│   ├── agents/
│   └── skills/
└── (rest of the project)

Use this when: the skill only makes sense in the context of one project, and you want it version-controlled with that project.

Stage 3 — Plugin: shareable, installable, versioned

When the skill/agent is mature and other people should have it regardless of which project they're in, promote it to a plugin in this marketplace.

The migration is just moving files — the agent/skill markdown doesn't change:

# Before (project-scoped)              # After (plugin)
.claude/agents/my-helper.md       →    plugins/my-plugin/agents/my-helper.md
.claude/skills/my-skill/          →    plugins/my-plugin/skills/my-skill/

Then add the plugin manifest and register it in the marketplace (see next section).

The .claude/ vs .claude-plugin/ distinction

• .claude/ = config for this project or user, only loaded in that context.
• .claude-plugin/ = manifest that turns a folder into a shareable, installable package.

Same idea — Claude config — different scope.

Adding a new plugin to this marketplace