02 · Public source
GearCore
One capability registry and project-scoping layer across several agent harnesses.
Plugins and Skills package capabilities inside one harness. GearCore handles the registry and project rules underneath several harnesses.
View sourceProblem
The same Skill, plugin or MCP still needed to be registered across Claude, Codex and Kimi, then scoped again for each project.
Mechanism
- Keep the capability registry and project rules in one hub.
- Let a project narrow the global set, add local definitions, or override a backend with the same ID.
- Use list-skills for discovery and request-skill to activate one Skill and its declared tools.
Evidence
- Local tests
- 94 passed
- Covered behaviour
- Scope · visibility · activation
- Also covered
- Collisions · sync · CLI
- Workspace use
- ChronoCore at Level 0
Boundary
OAuth-backed MCPs are not handled cleanly yet: interactive authorization during startup can hold the hub until timeout and leave cleanup errors.
I have not measured token savings. Each harness also keeps its own installation and discovery path.