agentleFS
Sign inStart free
sammasaksammasak/claude-code-skills/skills/verify-service/SKILL.md

verify-service

Skill1 starsChanged 28 days agoMITView on GitHub

Use when a homelab service was just deployed or changed, before reporting it done or live, including named apps behind Authentik. Not for diagnosing WHY a deploy or cluster is broken — route that to kubernetes-gitops.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Don't use curl -k; it hides cert-manager failures.

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Verify Service (homelab)

Done means observed healthy, not "Flux applied it". Pick the deepest level that applies:

  1. Flux landed it: flux get kustomizations apps shows your commit's revision and Ready.
  2. Pods: kubectl rollout status deployment/<name> -n <ns> --timeout=120s. Scale-to-zero apps (KEDA HTTP add-on) legitimately sit at 0 replicas; send a request first, then check.
  3. App health: hit the app's real health path, not /. Gated apps can't be checked from outside (see below), so go in-cluster:
    kubectl -n <ns> port-forward svc/<name> 18080:<port> &   # then:
curl -fsS http://localhost:18080/health
  4. Public route: curl -sS -o /dev/null -w '%{http_code} %{redirect_url}\n' https://<app>.sammasak.dev. If the Ingress carries the authentik-authentik-forward-auth middleware, the correct answer is a 302 to auth.sammasak.dev; that proves DNS, Traefik, TLS and forward-auth, not the app. Apps without the middleware (ntfy, public sites, apps doing their own OIDC) return 200. Read the Ingress annotations to know which to expect.
  5. UI: for a frontend, follow e2e-testing (use the playwright-login server for gated apps).

Traps

  • First request after idle can fail or time out during cold start; retry once before calling it broken.
  • Don't use curl -k; it hides cert-manager failures.
  • Levels 1-3 need cluster access; see kubernetes-gitops for where flux/kubeconfig live. Level 4 works from any host.
  • The verify-deployment agent covers levels 2 and 4 cheaply for ungated apps.
  • devenv tasks run gitops:unhealthy in ~/homelab-gitops lists anything not Ready cluster-wide.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free