Plugin Manifest

Configuration du plugin via marketplace.json.

Structure

{
  "id": "mon-plugin",
  "name": "Mon Plugin",
  "description": "Description courte",
  "version": "1.0.0",
  "author": "Votre nom",
  "license": "MIT",
  "homepage": "https://github.com/user/mon-plugin",
  "keywords": ["plugin", "claude"],
  "repository": {
    "type": "git",
    "url": "https://github.com/user/mon-plugin.git"
  }
}

Champs

Champ	Type	Obligatoire	Description
`id`	string	✅	ID unique du plugin
`name`	string	✅	Nom d'affichage
`description`	string	✅	Description courte
`version`	string	✅	Version sémantique
`author`	string	✅	Nom de l'auteur
`license`	string	❌	Type de licence
`homepage`	string	❌	URL du site/documentation
`keywords`	array	❌	Tags de recherche
`repository`	object	❌	Info du repo Git

Exemple complet

{
  "id": "email-analyzer",
  "name": "Email Analyzer",
  "description": "Analyze emails for spam, validity and domain information",
  "version": "2.1.0",
  "author": "Claude Plugins Team",
  "license": "MIT",
  "homepage": "https://github.com/plugin-factory/email-analyzer",
  "keywords": ["email", "validation", "spam", "analysis"],
  "repository": {
    "type": "git",
    "url": "https://github.com/plugin-factory/email-analyzer.git"
  }
}

Bonnes pratiques

Utilisez des IDs kebab-case et uniques
Incrémentez la version sémantiquement
Gardez la description courte et claire
Ajoutez des keywords pour la découverte
Maintenir un repository public quand possible