Agent skills for deploying and using LibreSeal, a free, self-hosted secrets manager.
LibreSeal is an independent fork of Phase; this repository is a fork of phasehq/ai. It is not affiliated with or endorsed by Phase.
| Skill | Status | Purpose | Trigger phrase |
|---|---|---|---|
docker-compose |
Supported | Deploy LibreSeal from source with Docker Compose (homelab first, optional Let's Encrypt), back up and upgrade it | "deploy LibreSeal with Docker Compose" |
libreseal-usage |
Supported | Use a LibreSeal server safely from an agent with the libreseal CLI and a least-privilege service account |
"run my app with LibreSeal secrets" |
k8s, eks, aks |
Not adapted | Upstream Phase Helm/cloud guides, kept for reference. They deploy Phase images and charts, not LibreSeal | — |
With the skills CLI:
npx skills add Dos2Locos/libreseal-skills -s docker-compose
npx skills add Dos2Locos/libreseal-skills -s libreseal-usageOr copy a skill directory manually, e.g. for Claude Code:
git clone https://github.com/Dos2Locos/libreseal-skills.git
mkdir -p ~/.claude/skills
cp -R libreseal-skills/docker-compose ~/.claude/skills/libreseal-docker-compose
cp -R libreseal-skills/libreseal-usage ~/.claude/skills/libreseal-usageThe version-matched CLI guide is embedded in the CLI itself: a human runs libreseal ai enable to install it for the agent, or libreseal ai skill to print it.
- Agents get credentials only through
LIBRESEAL_HOST/LIBRESEAL_SERVICE_TOKENset by the user, from a service account restricted to the apps and environments they need — never an admin or personal token. - Secrets are injected into processes with
libreseal run; skills forbid printing them, putting them in prompts or writing them to version-controlled files. - The CLI's agent detection (blocking
printenvand friends) is defence in depth, not a security boundary.
libreseal-usage/examples/agent-demo.sh demonstrates the flow end to end and checks that access outside the token scope is denied.
Every pull request to main runs scripts/validate-skills.sh in GitHub Actions (job validate), and main only accepts pull requests with that check green. Run it locally before opening a PR (needs git, python3, openssl, docker; shellcheck optional):
scripts/validate-skills.shIt checks that each SKILL.md has front matter with name equal to its directory and a description, that shell scripts pass shellcheck, that every nginx block in the docs passes nginx -t (mark partial blocks with a first line starting # fragment), and that no .env files or LibreSeal/Phase tokens are committed. It does not contact any LibreSeal server.
See the LibreSeal README for the server, CLI and skills commits verified together.
MIT — see LICENSE. Original skills © Phase; LibreSeal changes released under the same license.