Soliplex Skills¶
soliplex-skills is shared infrastructure for releasing and upgrading
versioned filesystem skills (agentskills.io style:
a directory with a SKILL.md plus references/, scripts/, and assets/)
across the Soliplex projects:
| Repository | Skills it publishes |
|---|---|
soliplex |
soliplex-docs |
soliplex-template |
soliplex-template |
soliplex-concierge |
soliplex-concierge-installer, soliplex-concierge-room, soliplex-concierge-admin |
See the Skills catalog for what each skill does, where it runs (inside Soliplex or in an external coding agent), its source repo, and its latest release.
Status
This site documents the mechanisms these projects use and the library API that provides them. The library is implemented and tested (100% branch coverage).
What it provides¶
One importable, tested Python package holding the release/upgrade machinery a versioned filesystem skill needs:
versions—list/diff/upgradea published skill against its GitHub releases, driven by a per-skillSkillSpec.install—download, install / upgrade a published or local skill into a stack, and defang it for room-agent use (see Installing and upgrading skills).build— assemble a skill intodist/<name>/: copy the source tree, stampSKILL.mdwith the source commit, and validate it (with an optionalgeneratorhook for build-time content).releases/manifest/metadata/_archive— GitHub release access, theversion.jsonschema, reading/stampingSKILL.md'ssource_commit, and the download/verify/extract primitives the others build on.
Where to start¶
Read the Overview for the vocabulary and the release model, then the Mechanisms section for how building, publishing, and installation map onto the library API. The API reference is the full surface.
Go straight to Managing an installed skill: how to list published versions, diff your installed copy against a published one, and upgrade (or downgrade) in place.
Follow Adopt in a new repo: a step-by-step setup
with copy-paste-ready skill_versions.py, build_skill.py, and GitHub
Actions workflow examples.
How the skills use it¶
- Each skill bundles a thin
skill_versions.py. Because an installed skill runs in an environment wheresoliplex_skillsis not installed, it is a small PEP 723 script that declares# dependencies = ["soliplex-skills>=…"]in its inline metadata, lettinguvprovision the library at run time. It fills in aSkillSpecand delegates toSkillVersions. - Build scripts call
soliplex_skills.build.soliplex-templateandsoliplex-conciergebuild viabuild.build_skill(discover_skillsplus a loop for the multi-skill concierge repo); thesoliplex-docsbuilder passes ageneratorhook tobuild_skillfor its nav-derived documentation map. All reusemetadata.stamp_metadataand in-processskills_refvalidation. - Publishing lives in each repo's GitHub Actions workflow — dual-mode
releases, the
version.jsonmanifest, and prune-to-KEEP_ROLLING— and the build step it runs is the part that calls this library.