ASSIST Claude Marketplace

A catalog of Claude Code plugins owned by the ASSIST Software GitHub organization and maintained by @liviumit.

Important

Security notice. Plugins can run commands, hooks, and MCP servers on your machine. Only install plugins you trust, and review a plugin's source before installing it.

Access

Claude Code uses your existing git credentials for install and updates — make sure you're authenticated via gh auth login or an SSH key loaded in ssh-agent.

Install the marketplace

/plugin marketplace add assist-software/claude-code-repository

Then install any plugin from it:

/plugin install <plugin-name>@assist-claude-marketplace

Note

The repository is claude-code-repository, but the marketplace registers under its own name, assist-claude-marketplace (from marketplace.json). That's why you add the repo path but install against @assist-claude-marketplace.

Or browse interactively with /plugin.

Available plugins

Plugin	Category	Description
prompt-engineering-suite	ai	Audit, author, fix, and initialise LLM prompts against a best-practices rubric.

Repository layout

assist-claude-marketplace/
├── .claude-plugin/
│   └── marketplace.json        # the catalog — lists every plugin and its source
├── plugins/                    # first-party plugins (relative-path sources)
│   └── prompt-engineering-suite/
│       ├── .claude-plugin/
│       │   └── plugin.json      # plugin manifest (name, version, author…)
│       ├── skills/<name>/SKILL.md
│       ├── commands/<name>.md
│       ├── agents/<name>.md
│       ├── templates/
│       └── README.md
├── external_plugins/           # (optional) third-party plugins referenced here
└── README.md

Warning

Component directories (skills/, commands/, agents/, hooks/) live at the plugin root, never inside .claude-plugin/. Only plugin.json goes in .claude-plugin/.

Add a new plugin

1. Create a directory under plugins/<your-plugin>/.
2. Add plugins/<your-plugin>/.claude-plugin/plugin.json:

   {
     "name": "your-plugin",
     "description": "What it does.",
     "version": "0.1.0",
     "author": { "name": "Your Name" }
   }

3. Add components at the plugin root: skills/, commands/, agents/, hooks/hooks.json, .mcp.json, .lsp.json.
4. Register it in .claude-plugin/marketplace.json under plugins:

   {
     "name": "your-plugin",
     "source": "./plugins/your-plugin",
     "description": "What it does.",
     "category": "development"
   }

   Because metadata.pluginRoot is set to ./plugins, you may also write "source": "your-plugin".
5. Validate and test (see below), then commit and push.

Reference an external plugin

Instead of a relative path, a plugin entry can point at another repo:

{
  "name": "deployment-tools",
  "source": { "source": "github", "repo": "owner/deploy-plugin", "ref": "v2.0.0" }
}

Supported source types: relative path (./...), github, url (any git host), git-subdir (monorepo subfolder), and npm.

Validate and test

# Validate the marketplace catalog
claude plugin validate .

# Validate a single plugin (checks SKILL/agent/command frontmatter + hooks.json)
claude plugin validate ./plugins/prompt-engineering-suite

# Try it locally before pushing
claude --plugin-dir ./plugins/prompt-engineering-suite

Versioning

• Set version in plugin.json and bump it on every release — users only get updates when the resolved version changes.
• Or omit version: each new git commit is then treated as a new version (simplest for active development).
• Don't set version in both plugin.json and the marketplace entry — plugin.json silently wins.

Contributing

Contributions are open to ASSIST Software org members — whether you're adding a new plugin or improving an existing one.

Workflow

1. Create a branch off main (git switch -c <plugin-or-fix-name>). Don't commit directly to main.
2. Make your change:
   • New plugin — follow Add a new plugin above.
   • Improving a plugin — edit files under plugins/<name>/ and bump the version in that plugin's plugin.json (see Versioning) so users actually receive the update.
3. Validate locally — your change must pass before review:

   claude plugin validate .                         # the catalog
   claude plugin validate ./plugins/<your-plugin>   # the plugin you touched

4. Test it loads: claude --plugin-dir ./plugins/<your-plugin>, then exercise its skills/commands/agents.
5. Open a pull request against main. Describe what changed and how you tested it.
6. A maintainer (@liviumit) reviews and merges. Once merged, org members pick it up with /plugin marketplace update.

Guidelines

• Naming: plugin and marketplace names are kebab-case (lowercase, digits, hyphens) — the Claude.ai sync rejects anything else.
• Structure: component dirs (skills/, commands/, agents/, hooks/) go at the plugin root — only plugin.json lives in .claude-plugin/.
• Docs: every plugin needs a README.md describing its components and how to invoke them.
• Catalog: register each plugin in .claude-plugin/marketplace.json with a clear description, a category, and keywords.
• Security: plugins run on teammates' machines — don't add hooks, MCP servers, or bin/ executables that do anything unexpected. Call out anything that touches the network or filesystem in the plugin's README.
• Self-contained: a plugin can't reference files outside its own directory (../shared) — it's copied to a cache on install. Use symlinks if you must share.

Questions or proposals? Open an issue or ping the maintainer.