## Why The skill had no instruction to bump the catalog version after ADD, REMOVE, or UPDATE operations. Clients cache the marketplace catalog and use the version field to detect changes — without a bump, the new state is invisible until a forced refresh. ## Implementation Notes Added a Gotcha explaining the rule and semver convention (ADD/REMOVE → minor, UPDATE → patch). Added a dedicated "Bump catalog version" step to each mutating flow. Updated README to match. Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
18 lines
403 B
JSON
18 lines
403 B
JSON
{
|
|
"agents": "agents/",
|
|
"author": {
|
|
"email": "defame1297@rkdr.net",
|
|
"name": "Defame1297"
|
|
},
|
|
"description": "Skills and agents for creating, maintaining, and managing a Claude Code / Copilot CLI plugin marketplace.",
|
|
"hooks": "hooks.json",
|
|
"keywords": [],
|
|
"license": "MIT",
|
|
"mcpServers": ".mcp.json",
|
|
"name": "kyberforge",
|
|
"skills": [
|
|
"skills/"
|
|
],
|
|
"version": "1.0.3"
|
|
}
|