Executable capability contracts
Skills can declare typed inputs/outputs, effects, capability/resource requirements, verification, and executable fixtures.
CONTRIBUTIONS SHOWCASE
Impact, not just commits.
SolKraft recognizes the different ways an open-source system gets better. Code matters. So do architecture ideas, testing, research, issue discovery, documentation, design, and community help. This showcase records the high-level outcomes contributors helped create.
FILTER THE SHOWCASE
Showing all 6 contribution areas.
Safer capability selection
Contract-aware admissibility, whole-route validation, typed dataflow, and explicit blocked states make selection easier to inspect.
Regressions become visible
Reusable CI runs contract checks, fixture assertions, packaging, installed MCP verification, and broad routing regression suites.
Ideas count as contribution
Recognition is based on project impact, not whether the contribution arrived as a pull request.
Clear support and contribution paths
Users can submit guided support issues, nominate contributors, and distinguish help requests from code contributions.
Public evidence and attribution
Contributors, ratings, nominations, changelog entries, and validation receipts are visible and reviewable.
CONTRIBUTOR PROFILES
Who moved the project forward.
Profile cards summarize each recognized contributor’s impact, earned badges, contribution areas, and public links. The same showcase filters apply to these cards.
CONTRIBUTOR 001 · COMMUNITY IDEA CONTRIBUTOR
Cozy
@Cozy2054934 · Berlin, Germany
Helped move SolKraft from descriptive skill metadata toward executable capability contracts that declare inputs, side effects, authority requirements, and CI-run pass/fail fixtures. That idea influenced Contract v1 fixture execution, contribution gates, safer capability selection, and visible regression failures.
Project-Shaping
Idea Architect
Executable Contracts
CI Impact
Contributor 001
Architecture
Routing
Verification
Community
Open source
Public impact trail: the contribution is documented on the Contributors page; the resulting executable-contract implementation landed publicly in SolKraft PR #17.
FEATURED CONTRIBUTION · 001
Cozy · @Cozy2054934
★★★★★
5/5 · PROJECT-SHAPING
Cozy’s idea work helped push SolKraft toward executable skill contracts and CI-visible regression protection. The project now has real contract fixtures, contribution gates, typed contract metadata in routing, and failures that surface instead of silently drifting.
★★★★★ Project-ShapingIdea ArchitectExecutable ContractsCI ImpactContributor 001
Nice—keep the skill contract executable: declare inputs, side effects, auth scope, and a few pass/fail fixtures, then run it in CI. That makes capability selection safer and regressions visible.
The skill layer is most useful when each skill declares inputs, side effects, auth scope, and a test contract. Then an agent can select capabilities without treating every tool as an opaque superpower