Skip to main content
skill CX Codex

wendy-self-hosted — Claude Code skill: keep the stack SaaS-free

A rule for agents touching Wendy interop code: the wendyos and wendy-agent stack has to run without the SaaS side. Useful for on-prem and airgapped setups.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add wendylabsinc/claude-skills --skill wendy-self-hosted -a claude-code
Open on GitHub

What wendy-self-hosted does

The skill states one requirement. The self-hosted path must always work. Any feature that only functions when pki-core, Wendy Cloud or wendy-auth are managed GCP services counts as unfinished, because Wendy's critical-infrastructure partners cannot route fleet control through a vendor's multi-tenant cloud.

Two references ship with it: references/identity-backends.md and references/review-checklist.md. They lay out the pluggable identity provider seam. Define the interface first, put the managed backend behind it as one option, then add a self-hosted backend or a stub tied to a tracked issue. Backend choice comes from config, not from sniffing the environment. Nothing in the code may assume the GCP metadata server, PSC, VPC-SC, Google's JWKS, Artifact Registry or a reachable cloud control plane.

This distills AAA Contract v0.21, and the contract wins on any disagreement. The rule is mandatory, and related skills wendy-aaa-interop, wendy-certificates, wendy-device-enrollment, wendy-device-interop and wendy-security-baselines all point back to it. A change that breaks the self-hosted path does not pass.

What it helps with

  • keep the self-hosted path intact while integrating with pki-core or wendy-auth
  • add a pluggable identity provider seam instead of hard-wiring GCP
  • define what a device does when the cloud is unreachable
  • audit interop code for hidden PSC and Google JWKS assumptions
  • make pki-core deployable on operator infrastructure

Example prompts for the agent

  • Check this feature against the wendy-self-hosted rule: does it work without Wendy Cloud?
  • Add a seam for a self-hosted identity backend, keep the managed one as a single option
  • What happens to a device if the cloud is unreachable at redemption time?

How to install wendy-self-hosted

1Skills CLI (Vercel)

npx skills add wendylabsinc/claude-skills --skill wendy-self-hosted -a claude-code

2Manually: put the files in place

~/.claude/skills/wendy-self-hosted/SKILL.md

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

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

Questions about wendy-self-hosted

How do I install wendy-self-hosted in Claude Code?

Run npx skills add wendylabsinc/claude-skills --skill wendy-self-hosted -a claude-code. The skill file lands at ~/.claude/skills/wendy-self-hosted/SKILL.md.

What does wendy-self-hosted do?

It makes the agent keep the self-hosted path of the Wendy stack working. A feature that only runs against managed GCP services is treated as incomplete.

Which platforms does the skill support?

Claude, Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode. GitHub Copilot uses a different install line: gh skill install wendylabsinc/claude-skills wendy-self-hosted.

Similar skills

All skills for DevOps and infrastructure →

From the same set7

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor