plugin-maintenance

Update Synapse Claude Code plugin and skill documentation across releases.

29|3|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/Vincentwei1021/Synapse --skill plugin-maintenance-vincentwei1021
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-maintenance
Source: https://github.com/Vincentwei1021/Synapse/tree/main/.claude/skills/plugin-maintenance
Command: npx skills add https://github.com/Vincentwei1021/Synapse --skill plugin-maintenance-vincentwei1021

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you correctly update the Synapse Claude Code plugin and its associated skill documentation without breaking hooks, MCP tool references, or versioned marketplace installs.

Core Features & Use Cases

  • Plugin & skill documentation alignment: keeps workflow steps, tool lists, and lifecycle guidance consistent across plugin and standalone skill docs.
  • Controlled version management: ensures plugin version bumps are performed in both plugin.json and marketplace.json to avoid mismatched releases.
  • Bash hook script compatibility: enforces Bash 3.2-safe changes for hook scripts so updates don’t fail on macOS/Claude Code environments.
  • Release and validation checklist: provides an end-to-end checklist for adding MCP tools, modifying hook scripts, testing locally, and upgrading installed users.

Quick Start

Ask the AI to produce a complete update plan for adding a new MCP tool, including which TypeScript files and which plugin/standalone documentation sections must be edited, plus the exact version-bump steps to release the change.

Frequently Asked Questions about plugin-maintenance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep Claude Code plugin documentation aligned when adding a new MCP tool?

To maintain Claude Code plugin documentation, update workflow steps, tool lists, and lifecycle guidance across both plugin and standalone skill docs when adding MCP tools. This prevents inconsistent tool or lifecycle guidance across releases by keeping all repository paths synchronized.

Why do my Synapse plugin hook scripts fail on macOS after a version bump?

Synapse plugin hook scripts fail on macOS when updates are not Bash 3.2-safe. Claude Code environments run macOS default Bash, so enforcing Bash 3.2-compatible syntax during hook script updates prevents execution failures across user environments.

What's the best way to synchronize versions between plugin.json and marketplace.json for a release?

The best way to synchronize versions is to perform version bumps in both plugin.json and marketplace.json simultaneously. This controlled version management avoids mismatched releases and ensures marketplace versioned deployments install correctly for both plugin and standalone skill variants.

What's the release checklist for updating Synapse plugin hook scripts and MCP tools?

The release checklist covers adding MCP tools, modifying hook scripts, testing locally, and upgrading installed users. It requires editing correct repository paths, validating Bash 3.2 compatibility, and synchronizing plugin.json and marketplace.json versions to ensure end-to-end release integrity.

Can I use this approach to maintain standalone skills separate from the Synapse plugin?

Yes, you can maintain standalone skills separate from the Synapse plugin. The maintenance process applies to both plugin and standalone skill variants, ensuring documentation alignment and versioned marketplace deployments work correctly regardless of the distribution format used.