Skip to main content
skill CX Codex

self-hosted-release-validation — Claude Code skill

self-hosted-release-validation is a Claude Code skill that validates OSS self-hosted releases via Docker Compose. Evaluates SQLite persistence, agent sources, and beta readiness.

Apache-2.0 ★ 104 updated 2026-11-17

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add dodo-labs-ai/mem-forge --skill self-hosted-release-validation -a claude-code
Open on GitHub

What self-hosted-release-validation does

The skill validates self-hosted releases along the documented newcomer journey. It enforces an isolated Docker Compose project, loopback-only port bindings, a dedicated SQLite volume, UI and API startup, model configuration, source synchronization, and local MCP retrieval.

Execution relies on scripts/compose_smoke.sh. For model inference and embeddings, the script takes --ollama, an exported OPENROUTER_API_KEY, or explicit --generation-provider and --embedding-provider flags. Official release steps combine it with --quality alongside provider_smoke.py as detailed in docs/releasing-python-distribution.md.

Existing MemForge volumes or caches must remain untouched; tests run strictly on isolated data volumes. Persistence is verified by restarting the Compose stack against the existing volume and rechecking documents and MCP retrieval. The final review delivers a strict GO, CONDITIONAL GO, or NO-GO verdict.

What it helps with

  • test clean Docker Compose startup before publishing a release
  • verify SQLite volume persistence after restarting the service stack
  • audit source connector matrices across servers and local daemons
  • issue conservative GO or NO-GO decisions for public beta releases

Example prompts for the agent

  • Run the self-hosted release validation using scripts/compose_smoke.sh in an isolated project
  • Execute the Docker Compose smoke test with --quality and OPENROUTER_API_KEY
  • Verify SQLite persistence across restarts and provide a beta readiness verdict

How to install self-hosted-release-validation

1Skills CLI (Vercel)

npx skills add dodo-labs-ai/mem-forge --skill self-hosted-release-validation -a claude-code

2Manually: put the files in place

~/.claude/skills/self-hosted-release-validation/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/self-hosted-release-validation/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about self-hosted-release-validation

How to install self-hosted-release-validation in Claude Code?

Run npx skills add dodo-labs-ai/mem-forge --skill self-hosted-release-validation -a claude-code. The definition is saved to ~/.claude/skills/self-hosted-release-validation/SKILL.md.

What does self-hosted-release-validation check?

It tests loopback Docker Compose startup, SQLite data persistence across restarts, real daemon jobs for local sources, and local MCP retrieval.

What is required to run self-hosted-release-validation?

You need Docker Compose, the repository script scripts/compose_smoke.sh, and either local Ollama or an exported OPENROUTER_API_KEY for embedding and generation models.

Source text

SKILL.md · Apache-2.0
---
name: self-hosted-release-validation
description: "Validate an OSS self-hosted release through the newcomer Docker Compose path: isolated Compose project, SQLite persistence, source support matrix, local-agent sources and a public-beta GO/NO-GO. Use for compose smoke tests, release validation and beta-readiness reviews."
---

# OSS Self-Hosted Release Validation

- Validate self-hosted releases through the documented newcomer path: a clean Docker Compose project, loopback-only ports unless explicitly testing exposure, the default SQLite-backed data volume, Admin UI/API startup, first-run model configuration, a representative source sync, memory retrieval, and the packaged local MCP path.
- `scripts/compose_smoke.sh` runs this newcomer path in an isolated Compose project (add `--ollama`, export `OPENROUTER_API_KEY`, or name each model kind's provider with `--generation-provider` and `--embedding-provider` for the model, sync and retrieval steps) and prints a table for the PR or release notes. A release runs it with `--quality`, beside `provider_smoke.py`, as the release guide, `docs/releasing-python-distribution.md`, states.
- Use an isolated Compose project and dedicated volume for smoke tests. Never reuse or delete a developer's existing MemForge volume, source data, plugin cache, or external service state merely to obtain a clean result.
- Prove SQLite persistence by restarting the API or Compose stack against the same isolated data volume and rechecking sources, documents, memories, keyword/vector health, and MCP retrieval.
- Treat source support as an execution matrix, not a registry count. For each registered source type, state whether server collection, local-agent collection, credentials, browser sessions, VPN/internal reachability, or an external provider is required. Classify each type as verified, unsupported by design, blocked by a missing prerequisite, or failed.
- Exercise local-agent sources through the real server-issued job and daemon path. A direct package injection may diagnose the service boundary, but it does not prove that the documented daemon workflow works.
- For public-beta readiness, separately assess newcomer reproducibility, first-run UX, error messages, documentation accuracy, default data/privacy boundaries, and obvious exposure or secret-handling footguns. Give a conservative `GO`, `CONDITIONAL GO`, or `NO-GO`, with the smallest required fixes or disclosure language.
- Do not present fixture-backed LLM/provider behavior as production-provider validation. Record the fixture contract, then distinguish it from real connector credentials and model-provider coverage.

© dodo-labs-ai · Apache-2.0 · dodo-labs-ai/mem-forge

Similar skills

All skills for DevOps and infrastructure →
self-hosted-funnel-launch autonnel The self-hosted-funnel-launch skill takes a self-hosted funnel from an empty install to published pages, checkout, an upsell and a thank-you step. Use it when an agent must deploy and edit the funnel over MCP. CX Codex +1 131,900installs grimmory-self-hosted-library reason-machines grimmory-self-hosted-library helps AI agents configure and run the self-hosted Grimmory book manager in Docker, set up e-reader sync, and extend its Spring Boot backend. CX Codex +1 1,300installs n8n-self-hosting czlonkowski n8n-self-hosting takes an agent from a fresh Linux VM to a running self-hosted n8n over SSH: Docker Compose, Caddy with automatic HTTPS, secrets generated on the box. CX Codex +1 2,400installs spring-boot-project-creator giuseppe-trisciuoglio spring-boot-project-creator — a skill that automates Spring Boot project creation (3.x or 4.x) via Spring Initializr with architecture selection (DDD or Layered), JPA setup, OpenAPI documentation, and Docker Compose services. CX Codex +1 3,700installs test-environments kindlmann test-environments designs an environment strategy across dev, CI, preview, and staging. It helps isolate per-PR stacks and eliminate flaky integration tests caused by unstubbed third-party APIs. CX Codex +1 1,600installs docker bobmatnyc docker is a Claude Code skill for packaging applications and dependencies into Docker containers. It covers Dockerfiles, image builds, and multi-service setups with Compose. CX Codex +1 1,100installs

From the same set8

memory memory is a Claude Code hook that loads MemForge guidance and MCP memory tools at session start. It triggers automatically whenever a session starts, resumes, or compacts. CX Codex ★ 104repo stars memory memory is a Claude Code plugin that connects to MemForge search and memory tools. Session-start guidance appears automatically; retrieval runs on request. CX Codex ★ 104repo stars memory memory is a Claude Code plugin that links the agent to the MemForge API via a local MCP proxy. It adds session guidance and on-demand memory lookup tools. CX Codex ★ 104repo stars lifecycle-canary-convergence lifecycle-canary-convergence is a Claude Code skill that checks Memory lifecycle state through an inventory, dry-run, apply, and audit. It runs before another retry or canary. CX Codex +1 ★ 104repo stars memforge-setup memforge-setup is a Claude Code skill for configuring MemForge workspace routing. It runs on requests to bind or remove a project binding, or to diagnose workspace selection. CX Codex +1 ★ 104repo stars plugin-release-validation plugin-release-validation is a Claude Code skill that validates MemForge memory plugin releases via remote marketplace paths. Runs when testing RC tags, checking caches, hooks, and MCP servers. CX Codex +1 ★ 104repo stars memforge-daemon-setup memforge-daemon-setup is a Claude Code skill that installs and configures the MemForge local daemon as a macOS or Linux user service. It runs for requests to connect, inspect, repair, or remove that service. CX Codex +1 ★ 104repo stars

Project sponsors

Companies that keep this analytics open