Package JSON

[eddiejaoude]

Can this be made more useful with scripts section?

[NavinPayPal]

Thanks for flagging this, @eddiejaoude! Right now package.json is mostly there for npm/marketplace metadata (name, version, license, keywords) — the plugin itself is just markdown/JSON config (skills, commands, hooks, .mcp.json), so there's no build or test step currently wired up.

Could you say more about what you had in mind for the scripts section? A few possibilities that come to mind on our end:

• A validate script to JSON-check .claude-plugin/plugin.json, marketplace.json, and .mcp.json
• A lint script for the markdown in skills/ and commands/
• Something else you were picturing (e.g. a local dev/install convenience script)?

Happy to scope this once we know what use case you're targeting.

[eddiejaoude]

Thanks @NavinPayPal . Yes I was thinking of the lint and prettier commands for the script section