From claude-quest
Use when adding automated marketplace version notifications to a claude-quest plugin repo, or when a plugin repo needs to connect to the claude-quest automated version syncing system. Trigger whenever the user wants to set up tag-based version notifications, implement the notify-marketplace workflow, or enable automated marketplace updates after pushing a release tag. Also trigger if someone asks "how do I make claude-quest automatically update when I release?" or asks about connecting their plugin to the marketplace automation. Use this skill — don't just describe the steps.
How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-quest:plugin-version-syncThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When a plugin repo pushes a git tag, this workflow notifies claude-quest to automatically open and merge a PR updating the plugin's pinned version in the marketplace. This skill implements the outbound half of that automation.
When a plugin repo pushes a git tag, this workflow notifies claude-quest to automatically open and merge a PR updating the plugin's pinned version in the marketplace. This skill implements the outbound half of that automation.
Announce at start: "I'm using the plugin-version-sync skill to set up automated marketplace notifications."
The plugin name must exactly match the name field in claude-quest/.claude-plugin/marketplace.json.
Check .claude-plugin/plugin.json first:
jq -r '.name' .claude-plugin/plugin.json 2>/dev/null
If that returns nothing, look up the repo by its directory name:
| Repo | Plugin name |
|---|---|
| claude-plugin-audit-trail | audit-trail |
| claude-plugin-notifications | notifications |
| claude-plugin-dev-workflow | dev-workflow |
| claude-plugin-guardrails-git | guardrails-git |
| claude-plugin-guardrails-bash | guardrails-bash |
| claude-plugin-guardrails-docker | guardrails-docker |
| claude-plugin-guardrails-xcode | guardrails-xcode |
If the repo isn't in this table, ask the user — the name must be exact.
cat .github/workflows/notify-marketplace.yml 2>/dev/null
If the file exists and contains event_type: 'plugin-version-bump', the workflow is already configured. Verify the plugin name matches what you found in Step 1, then stop — no further changes needed.
Create .github/workflows/notify-marketplace.yml with the plugin name from Step 1 substituted for <PLUGIN-NAME>:
name: Notify Marketplace
on:
push:
tags: ['v*']
jobs:
notify:
runs-on: ubuntu-latest
steps:
- name: Dispatch version bump to claude-quest
uses: actions/github-script@v7
with:
github-token: ${{ secrets.MARKETPLACE_DISPATCH_TOKEN }}
script: |
await github.rest.repos.createDispatchEvent({
owner: 'MechanicalTyler',
repo: 'claude-quest',
event_type: 'plugin-version-bump',
client_payload: {
plugin: '<PLUGIN-NAME>',
version: context.ref.replace('refs/tags/v', '')
}
})
git add .github/workflows/notify-marketplace.yml
git commit -m "feat: add automated marketplace version notification"
After committing, surface the prerequisite they'll need to verify:
The
MARKETPLACE_DISPATCH_TOKENsecret must exist at your GitHub org level — it's a fine-grained PAT scoped toMechanicalTyler/claude-questwithActions: writepermission. If it's not already set up, ask the claude-quest maintainer.Once the secret is in place: push a tag like
v1.8.0and claude-quest will automatically open and merge a PR updating your plugin's version within ~60 seconds.
If the user reports problems after setup:
MARKETPLACE_DISPATCH_TOKEN is missing or expired at the org levelplugin value in the workflow doesn't match the name in claude-quest/.claude-plugin/marketplace.json; fix the name and push a new tagGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.
npx claudepluginhub mechanicaltyler/claude-quest --plugin claude-quest