How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/alex-de-haas/docker-host --skill hosty-app-skillBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
Hosty App Skill
Use this skill to implement Hosty runtime apps in the shape expected by this repository. The supported contract is an app manifest with schemaVersion: "app.0.1".
Workflow
- Identify whether the user wants to create a new runtime app, wrap an existing app, update an app manifest, add Hosty identity/roles, configure data/backups, or validate an app.
- Treat
docs/features/runtime-app-manifest/feature.md,docs/features/domain-model/feature.md,docs/features/auth-gateway/feature.md,apps/core/src/Haas.Hosty.Core/RuntimeAppManifest.cs,apps/core/src/Haas.Hosty.Core/CoreLifecycleService.cs, andapps/demo-appas source of truth when implementation details matter. - Use
apps/demo-app/manifest.jsonas the manifest shape andhosty apps install apps/demo-app --runtime devas the local directory install pattern.
References
- Read
references/app-manifest.mdwhen authoring or reviewingmanifest.json, runtime profiles, service implementations, settings, storage, dependencies, endpoints, install/update behavior, or backups. - Read
references/app-auth-and-users.mdwhen adding app identity, app-owned roles, or scoped app directory access. - Read
references/app-manifest.md("MCP Interface") when adding or debugging an app's MCP endpoint — delegated- and scoped-token auth, the handshake's HTTP 202, and read-only annotations. - Read
references/app-feeds.mdwhen publishing or reviewing repository-ownedfeeds.jsonfor Marketplace discovery and Core-managed updates. - Read
references/app-launch-mode.mdwhen the app has a UI, to keep it from drawing the name and page navigation a shell already renders around it. - Read
references/demo-app-patterns.mdwhen validating against the repository Demo App. - Read
references/app-implementation-checklist.mdbefore final verification.
Local Validation
Use Core-managed runtime app lifecycle:
bash
hosty core start
hosty apps install apps/demo-app --runtime dev
hosty apps start com.haas.demo-appFor direct endpoint probes:
bash
TOKEN="$(hosty apps identity com.haas.demo-app --user user@docker-host.local --format token)"
curl -H "X-Docker-Host-Identity: $TOKEN" <assigned-demo-app-origin>/api/auth/identity
