Plugin system — installable plugins with registry, day-1 ready
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 1
- Avg merge
- 7h 13m
- Merged PRs (30d)
- 31
Description
Build a plugin system so woltspace can be extended without touching platform code.
- Plugin manifest format (name, version, skills, hooks)
- Install from registry: 'install plugin X'
- Plugin registry (start simple: GitHub-hosted)
- Runtime: plugins add skills/tools available to sessions
- Agent-runtime agnostic: plugin format should not be hardcoded to Claude Code
Day 1 ready means the architecture is in place even if the registry is sparse at launch.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by mapping woltspace’s existing session, skill, tool, and command entry points, then define the manifest, GitHub-hosted registry, install flow, and agent-runtime-neutral boundary described here. Done means the architecture supports installed plugins adding skills and tools, even with a sparse registry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100