Agent skill
marketplace-workflow
Use when user explicitly says "marketplace", "move to marketplace", "publish to marketplace", or "add to my marketplace". Never use for creating skills/rules in dotfiles or project-level locations.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/marketplace-workflow
SKILL.md
Marketplace Workflow
Workflow for moving user-level content (~/.claude/) to jasonkuhrt/claude-marketplace.
Paths
| What | Path |
|---|---|
| Marketplace repo (GitHub) | https://github.com/jasonkuhrt/claude-marketplace |
| Marketplace repo (local) | ~/projects/jasonkuhrt/claude-marketplace |
| User-level source | ~/.claude/ |
| Collaborative projects | ~/projects/heartbeat-chat/* |
Workflow
-
Identify target plugin: Check existing plugins in marketplace. If thing fits one, use it. If none, multiple, or ambiguous, ask user with suggestions for new plugin name/concept.
-
Check context:
- If in collaborative project (
~/projects/heartbeat-chat/*): ask if plugin should install at project level instead of user level - Otherwise: default to user-level install
- If in collaborative project (
-
Create/update plugin: Add command/skill/rule to the target plugin in the marketplace repo.
-
Install: Configure plugin to install at appropriate level (user or project).
-
Post-migration actions: Use AskUserQuestion with multiSelect to offer:
- "Remove source" - Delete original file(s) from source location (destructive)
- "Commit to marketplace" - Create commit in marketplace repo
- "Push to remote" - Push marketplace commits (only if commit was made)
Existing Plugins
Check ~/projects/jasonkuhrt/claude-marketplace/plugins/ for current plugins before suggesting new ones.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?