agentleFS
stoa-platformstoa-platform/stoa/.claude/skills/carto/SKILL.md

carto

Skill9 starsChanged 7 months agoApache-2.0View on GitHub

Query the STOA platform service catalog for live infrastructure state. The catalog lives in stoa-infra (private repo), NOT in the public stoa repo. Locate and read the catalog in this order: 1. ~/hlfh-repos/stoa-infra/docs/platform-catalog.yaml (local clone — preferred) 2. If not found: docs/platform-catalog.yaml (legacy location in stoa repo — may be stale) 3. If neither exists: warn the user and suggest cloning stoa-infra Important: When updating the catalog (drift fixes, new services), always write to stoa-infra/docs/platform-catalog.yaml. NEVER commit infra topology (hosts,…

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. About 0 are common, 9 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    If not found: docs/platform-catalog.yaml (legacy location in stoa repo — may be stale)

    line 21
  2. Very specific:

    If neither exists: warn the user and suggest cloning stoa-infra

    line 22
  3. Very specific:

    Important: When updating the catalog (drift fixes, new services), always write to stoa-infra/docs/platform-catalog.yaml.

    line 24
  4. Distinctive:

    Read the full catalog

    line 30
  5. Distinctive:

    If kubectl is available, enrich with live status:

    line 51
  6. Distinctive:

    If kubectl is available, add live state:

    line 88
  7. Distinctive:

    If the service has an argocdApp, check sync status:

    line 94
  8. Distinctive:

    Run the drift detection script:

    line 101
  9. Distinctive:

    If the file is missing, regenerate:

    line 112
  10. Very specific:

    NEVER display IP addresses, even if kubectl returns them — mask with <redacted>

    line 140
  11. Distinctive:

    NEVER display secret values — only secret names

    line 141
  12. Distinctive:

    If kubectl is not available, show catalog data only (no error, just note "live state unavailable")

    line 142
  13. Very specific:

    Always show the catalog lastUpdated date so the user knows freshness

    line 143
  14. Distinctive:

    If a service is missing from the catalog but visible in K8s, suggest adding it

    line 144

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

/carto — Platform Service Catalog

Query the STOA platform service catalog for live infrastructure state.

Modes

CommandWhat it does
/carto or /carto allFull inventory — all services with deploy status
/carto <service>Detail view of a single service + live state
/carto driftRun drift detection (catalog vs K8s live)
/carto graphShow the Mermaid dependency graph
/carto secretsShow secrets-to-services mapping

Step 1: Read the Catalog

The catalog lives in stoa-infra (private repo), NOT in the public stoa repo.

Locate and read the catalog in this order:

  1. ~/hlfh-repos/stoa-infra/docs/platform-catalog.yaml (local clone — preferred)
  2. If not found: docs/platform-catalog.yaml (legacy location in stoa repo — may be stale)
  3. If neither exists: warn the user and suggest cloning stoa-infra

Important: When updating the catalog (drift fixes, new services), always write to stoa-infra/docs/platform-catalog.yaml. NEVER commit infra topology (hosts, IPs, clusters, secrets) to the public stoa repo.

Step 2: Execute Based on Mode

Mode: all (default)

  1. Read the full catalog
  2. For each service, format a summary line:
## Platform Inventory — {metadata.lastUpdated}

### Core Services (K8s)
| Service | Type | Port | Prod Replicas | Health | ArgoCD |
|---------|------|------|---------------|--------|--------|
| control-plane-api | backend | 8000 | 2 | /health | control-plane-api |
| ... | ... | ... | ... | ... | ... |

### External Services (VPS)
| Service | Type | Host | Purpose |
|---------|------|------|---------|

### Clusters
| Cluster | Provider | Nodes |
|---------|----------|-------|
  1. If kubectl is available, enrich with live status:
kubectl get deployments -n stoa-system -o custom-columns='NAME:.metadata.name,READY:.status.readyReplicas,IMAGE:.spec.template.spec.containers[0].image' 2>/dev/null

Mode: <service> (single service detail)

  1. Find the service in the catalog by name
  2. Display all fields:
## {displayName} ({name})

Type: {type}
Tech: {tech}
Path: {path}
Port: {containerPort}
Image: {image}

### Deploy
- Prod: {deploy.prod.cluster}/{deploy.prod.namespace} ({deploy.prod.replicas} replicas)
- Staging: {deploy.staging...}

### Dependencies
- Depends on: {dependsOn[]}
- Consumed by: {exposedTo[]}

### Secrets
- {consumesSecrets[]}

### Health & Observability
- Health: {health}
- Metrics: {metrics}
- ArgoCD: {argocdApp}
- CI: {ciWorkflow}
  1. If kubectl is available, add live state:
kubectl get deployment {k8sName} -n {namespace} -o json 2>/dev/null
kubectl get pods -l app={k8sName} -n {namespace} -o wide 2>/dev/null
  1. If the service has an argocdApp, check sync status:
kubectl get application {argocdApp} -n argocd -o custom-columns='SYNC:.status.sync.status,HEALTH:.status.health.status' 2>/dev/null

Mode: drift

Run the drift detection script:

./scripts/ops/catalog-sync.sh

Present results to the user with context about what each drift means.

Mode: graph

  1. Read docs/architecture-graph.md
  2. Display the Mermaid graph and summary tables
  3. If the file is missing, regenerate:
./scripts/ops/catalog-graph.sh

Mode: secrets

Extract secrets mapping from the catalog:

## Secrets → Services Mapping

| Secret | Used By | Service Type |
|--------|---------|-------------|
| DATABASE_PASSWORD | control-plane-api | backend |
| KEYCLOAK_CLIENT_SECRET | control-plane-api | backend |
| KEYCLOAK_ADMIN_PASSWORD | stoa-gateway, keycloak | gateway, identity |
| ...

Flag any secret used by 0 or 3+ services as a potential concern.

Step 3: Output

Format output as a clean markdown table. Keep it concise — the catalog YAML has all details, the skill surfaces the most useful information at a glance.

Rules

  • NEVER display IP addresses, even if kubectl returns them — mask with <redacted>
  • NEVER display secret values — only secret names
  • If kubectl is not available, show catalog data only (no error, just note "live state unavailable")
  • Always show the catalog lastUpdated date so the user knows freshness
  • If a service is missing from the catalog but visible in K8s, suggest adding it
  • Catalog updates go to stoa-infra (private), NEVER to the public stoa repo
  • The graph (docs/architecture-graph.md) is auto-generated and OK in the public repo (no sensitive data)

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.