No description
- Go Template 64.1%
- Python 31.6%
- Smarty 4.3%
The ticket-004 publication scan refused to push claude-resources: the scaffolder's secrets file lived inside the published working tree, and the README/SKILL named estate vault items and the vault CLI. The setup now states what credentials are needed and leaves retrieval to the reader's secret store, and the scaffolder reads ~/.config/claude-resources/scaffold.env instead of ~/projects/claude-resources/.env. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|---|---|---|
| .claude-plugin | ||
| plugins | ||
| skills | ||
| .gitignore | ||
| README.md | ||
claude-resources
Central Claude Code marketplace for the homelab. Holds the marketplace index
(.claude-plugin/marketplace.json), the per-project plugins under plugins/,
and (later) shared cross-project skills under shared/.
Install (one-time, per VM, user scope)
claude plugin marketplace add https://forgejo.towneygorm.cc/daniel/claude-resources.git --scope user
claude plugin install project-scaffold@claude-resources --scope user
Restart Claude Code (or start a new session) to load the plugin.
Development loop
Edit a plugin in place, then test it privately without affecting consumers:
# one-time, on the dev machine, scoped to this repo
claude plugin marketplace add ~/projects/claude-resources --scope local
Skill edits are picked up live; for command/hook/MCP/plugin.json changes run
/reload-plugins. Consumers stay pinned to the git-URL install and see nothing
until you merge to main and they run claude plugin update.