ASSIST Claude Marketplace

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

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.

Available plugins

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

View prompt-engineering-suite →

Access

The repository is public. Claude Code uses your existing git credentials for install and updates — make sure you're authenticated via gh auth login or an SSH key 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.

Add a new plugin

Create a directory under plugins/<your-plugin>/.

Add plugins/<your-plugin>/.claude-plugin/plugin.json:

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

Add components at the plugin root: skills/, commands/, agents/, hooks/hooks.json, .mcp.json.

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

Validate, test, commit and push.

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

Repository layout

claude-code-repository/
├── .claude-plugin/
│   └── marketplace.json        # catalog — lists every plugin and its source
├── plugins/                    # first-party plugins
│   └── prompt-engineering-suite/
│       ├── .claude-plugin/
│       │   └── plugin.json
│       ├── skills/
│       ├── commands/
│       ├── agents/
│       └── README.md
└── README.md

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, git-subdir, npm.

Versioning

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

Validate and test

# Validate the marketplace catalog
claude plugin validate .

# Validate a single plugin
claude plugin validate ./plugins/prompt-engineering-suite

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

Contributing

Open to ASSIST Software org members — whether adding a new plugin or improving an existing one.

Workflow

Create a branch off main: git switch -c <plugin-or-fix-name>. Don't commit directly to main.
Make your change. Bump version in plugin.json so users receive the update.
Validate locally — your change must pass before review.
Open a pull request against main. A maintainer (@liviumit) reviews and merges.

Guidelines

Naming: plugin names are kebab-case — the Claude.ai sync rejects anything else.
Structure: component dirs 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.
Security: plugins run on teammates' machines — call out anything that touches the network or filesystem.
Self-contained: a plugin can't reference files outside its own directory — it's copied to a cache on install.

Licensed under the Apache 2.0 License · GitHub