alex-de-haas/docker-host

hosty-app-skill

Build, wrap, or update Hosty runtime apps.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/alex-de-haas/docker-host --skill hosty-app-skill

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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

  1. 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.
  2. 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, and apps/demo-app as source of truth when implementation details matter.
  3. Use apps/demo-app/manifest.json as the manifest shape and hosty apps install apps/demo-app --runtime dev as the local directory install pattern.

References

  • Read references/app-manifest.md when authoring or reviewing manifest.json, runtime profiles, service implementations, settings, storage, dependencies, endpoints, install/update behavior, or backups.
  • Read references/app-auth-and-users.md when 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.md when publishing or reviewing repository-owned feeds.json for Marketplace discovery and Core-managed updates.
  • Read references/app-launch-mode.md when 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.md when validating against the repository Demo App.
  • Read references/app-implementation-checklist.md before 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-app

For 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

관련 작업