Swift Stream Skills is a curated public collection of source-owned Agent Skills. Skills stay maintained in their original repositories while this repository provides one trusted place for discovery, validation, provenance, and installation.
The complete federation, trust, publication, naming, failure, and automation model is documented in Repository Mechanics.
- Prepare a source repository — migrate legacy skill files into canonical
<skill-name>/SKILL.mdpackages and classify public versus local skills; a source repository needs no federation notifier workflow, federation secret, OIDC setup, wake URL, signing key, or central credential. - Add a repository — register a new source, choose its skills root and public namespace prefixes, then let federation discover its skills automatically.
- Update a registered repository — change its description, branch, skills root, prefixes, or verified GitHub location.
- Remove a repository — revoke source trust and automatically remove its generated skills from the collection.
Federation trust and configuration changes are pull requests in this repository. Issues are for guidance and questions only.
| I want to… | Open |
|---|---|
| Register a new repository | Add federation source |
| Change a registered repository | Update federation source |
| Revoke a registered repository | Remove federation source |
| Ask a question | Open a help issue |
Each request needs a central request branch (not a fork in Wave 1) containing exactly one .federation-request file (add-source, update-source, or remove-source, with a final newline) and the exact body grammar from the matching template. After registration, ordinary skill content changes publish through polling and do not need another registry PR.
Multi-major products (for example a stable
release/4line and amainline): one source can declare multiple publication lines with disjoint prefixes (vapor4,vapor5). UsePublication lines:in the ADD/UPDATE body. See How to Add and Repository Mechanics.
Ordinary skill additions, edits, and removals do not require a registry PR. Once a source is registered, its current prefix-matching skills are discovered from the accepted source tree and published through validated automation. After a source is accepted in central federation.json, central scheduled polling (about every 15 minutes) reconciles its current source state and publication. A maintainer can manually dispatch reconciliation sooner; a normal source change may otherwise take until the next successful poll to appear centrally.
Browse the collection with GitHub CLI's Agent Skills support:
gh skill install swiftstream/skills
Install a specific skill by name:
gh skill install swiftstream/skills <skill-name>
gh skill is a preview installation route. It is not the semantic authority for the Agent Skills format or for this repository's federation mechanics.
The catalog below is generated from accepted federation.json source metadata and the validated metadata of currently published skill packages. Do not edit the generated section by hand.
A strongly typed, declarative, composable Swift SQL query-building library.
| Skill | Description |
|---|---|
| swifql-custom-extensions | Create downstream custom SwifQL functions, fluent helpers, structural continuations, custom clause ownership, or reusable extension libraries. Use in consuming apps or packages, not for modifying SwifQL's built-in source, functions, builders, dialects, or renderer. |
| swifql-query-building | Build, translate, review, or prepare SQL in downstream Swift code that imports SwifQL. Use for application or package query construction and preparation, not for changing SwifQL's own builders, functions, dialect implementation, renderer, or core source. |
Source repositories own their skill content. federation.json owns central trust/configuration. Generated skills/**, federation.lock.json, and the Skill Store catalog record the accepted publication state.
Normal source content changes can publish automatically after validation. Adding, reconfiguring, relocating, or removing a trusted source always requires an explicit manual federation-registry merge.
See Repository Mechanics for the complete state machines and security boundaries.