No description
- each skill updates CLAUDE.md on completion with current phase and next step - plan-check handoff explicitly directs user to fresh session for orchestrate - add Edit tool to allowed-tools for CLAUDE.md management |
||
|---|---|---|
| .claude-plugin | ||
| plugins | ||
| .gitignore | ||
| README.md | ||
numencore-toolkit
Personal Claude Code plugin marketplace. Self-hosted on Forgejo.
Install
git clone ssh://git@git.numencore.com:2222/phatch/numencore-toolkit.git
claude plugin marketplace add ~/numencore-toolkit
claude plugin install numencore-core@numencore-toolkit
claude plugin install git-tools@numencore-toolkit
Verify with claude plugin list or /reload-plugins in an active session.
Plugin management
# List installed
claude plugin list
# Update marketplace (re-reads from disk)
claude plugin marketplace update numencore-toolkit
# Reinstall after editing skills (re-caches)
claude plugin install <plugin>@numencore-toolkit
# Disable/enable
claude plugin disable <plugin>@numencore-toolkit
claude plugin enable <plugin>@numencore-toolkit
# Uninstall
claude plugin uninstall <plugin>@numencore-toolkit
Development
Structure
plugins/<plugin-name>/
├── .claude-plugin/plugin.json
└── skills/<skill-name>/SKILL.md
Cache and skill registration
Claude Code caches plugin contents at install time under ~/.claude/plugins/cache/. The harness loads skills from the cache at startup, not from the source directory. This means:
- Adding or editing a skill requires re-caching. The source files on disk are not read at runtime.
claude plugin updatecompares version strings, not file contents. Ifplugin.jsonstill has the same version,updatereports "already at latest" and the cache stays stale.
To refresh the cache after adding or changing skills:
# Option A: bump version in plugin.json, then update
claude plugin update <plugin>@numencore-toolkit
# Option B: force re-cache via reinstall (no version bump needed)
claude plugin uninstall <plugin>@numencore-toolkit
claude plugin install <plugin>@numencore-toolkit
After re-caching, restart Claude Code — the harness loads skills at startup.
For faster iteration during development, bypass the cache entirely:
claude --plugin-dir ~/numencore-toolkit/plugins/<plugin-name>
Permissions whitelist
Each skill needs a permission entry in .claude/settings.local.json to run without manual approval:
"Skill(<plugin-name>:<skill-name>)"
Add this when creating a new skill.
Adding a new skill to an existing plugin
- Create
plugins/<plugin>/skills/<skill-name>/SKILL.md - Add
Skill(<plugin>:<skill-name>)to.claude/settings.local.json - Re-cache:
claude plugin uninstall <plugin>@numencore-toolkit && claude plugin install <plugin>@numencore-toolkit - Restart Claude Code
Adding a new plugin
- Create
plugins/<name>/.claude-plugin/plugin.json - Add skills under
plugins/<name>/skills/<skill-name>/SKILL.md - Register in
.claude-plugin/marketplace.json - Add
Skill(<name>:<skill-name>)entries to.claude/settings.local.json - Run
claude plugin marketplace update numencore-toolkit - Run
claude plugin install <name>@numencore-toolkit
Plugins
| Plugin | Description |
|---|---|
numencore-core |
Core toolkit — skill authoring, project scaffolding |
git-tools |
Git workflow — commit formatting, branch management |