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,…
In this repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- cli/CLAUDE.mdCLAUDE.md
- control-plane-api/CLAUDE.mdCLAUDE.md
- control-plane-ui/CLAUDE.mdCLAUDE.md
- e2e/CLAUDE.mdCLAUDE.md
- portal/CLAUDE.mdCLAUDE.md
- stoa-gateway/CLAUDE.mdCLAUDE.md
- analyticsSkill
- ci-debugSkill
- ci-fixSkill
- competitive-watchSkill
- councilSkill
- decomposeSkill
- extractSkill
- fill-cycleSkill
- generate-backlogSkill
- impactSkill
- memory-consolidateSkill
- monitor-cdSkill
- parallel-reviewSkill
- pr-guardianSkill
- rewriteSkill
- roadmapSkill
- spec-drivenSkill
- sync-planSkill
- verify-megaSkill
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
- Very specific: line 21
If not found: docs/platform-catalog.yaml (legacy location in stoa repo — may be stale)
- Very specific: line 22
If neither exists: warn the user and suggest cloning stoa-infra
- Very specific: line 24
Important: When updating the catalog (drift fixes, new services), always write to stoa-infra/docs/platform-catalog.yaml.
- Distinctive: line 30
Read the full catalog
- Distinctive: line 51
If kubectl is available, enrich with live status:
- Distinctive: line 88
If kubectl is available, add live state:
- Distinctive: line 94
If the service has an argocdApp, check sync status:
- Distinctive: line 101
Run the drift detection script:
- Distinctive: line 112
If the file is missing, regenerate:
- Very specific: line 140
NEVER display IP addresses, even if kubectl returns them — mask with <redacted>
- Distinctive: line 141
NEVER display secret values — only secret names
- Distinctive: line 142
If kubectl is not available, show catalog data only (no error, just note "live state unavailable")
- Very specific: line 143
Always show the catalog lastUpdated date so the user knows freshness
- Distinctive: line 144
If a service is missing from the catalog but visible in K8s, suggest adding it
≈ “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.
Files
/carto — Platform Service Catalog
Query the STOA platform service catalog for live infrastructure state.
Modes
| Command | What it does |
/carto or /carto all | Full inventory — all services with deploy status |
/carto <service> | Detail view of a single service + live state |
/carto drift | Run drift detection (catalog vs K8s live) |
/carto graph | Show the Mermaid dependency graph |
/carto secrets | Show 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:
~/hlfh-repos/stoa-infra/docs/platform-catalog.yaml(local clone — preferred)- If not found:
docs/platform-catalog.yaml(legacy location in stoa repo — may be stale) - 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)
- Read the full catalog
- 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 |
|---------|----------|-------|- 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/nullMode: <service> (single service detail)
- Find the service in the catalog by name
- 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}- 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- 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/nullMode: drift
Run the drift detection script:
./scripts/ops/catalog-sync.shPresent results to the user with context about what each drift means.
Mode: graph
- Read
docs/architecture-graph.md - Display the Mermaid graph and summary tables
- If the file is missing, regenerate:
./scripts/ops/catalog-graph.shMode: 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
lastUpdateddate 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 publicstoarepo - The graph (
docs/architecture-graph.md) is auto-generated and OK in the public repo (no sensitive data)
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
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.

