add-actuator
Skill4 starsChanged 4 months agoMITView on GitHub
Add health/info/metrics actuator endpoints to a pico-boot app, or contribute HealthIndicator/InfoContributor components. Use when adding Kubernetes probes, health checks, or observability endpoints.
In this repository12 other files it gives its agents.
- add-appSkill
- add-authSkill
- add-celery-taskSkill
- add-componentSkill
- add-controllerSkill
- add-repositorySkill
- add-server-authSkill
- add-testsSkill
- add-validationSkill
- init-projectSkill
- pico-conventionsSkill
- releaseSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Add pico-actuator health/info endpoints for: $ARGUMENTS
- Very specific: line 62
Keep check() cheap; cache expensive probes (indicators are singletons — store the last result + timestamp on self).
- Very specific: line 64
Never point livenessProbe at /health or /health/ready: a slow dependency would restart healthy pods.
- Distinctive: line 66
Put only recoverable dependencies behind readiness (database, broker).
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Add Actuator
Add pico-actuator health/info endpoints for: $ARGUMENTS
What pico-actuator provides
GET /actuator/health— overall status + per-component detail (200/503)GET /actuator/health/live— liveness (alwaysUP; wire tolivenessProbe)GET /actuator/health/ready— readiness (aggregate; wire toreadinessProbe)GET /actuator/info— static config + dynamic contributorsGET /actuator/metrics— Prometheus default registry (needspico-actuator[metrics])
Steps
- Add dependency to
pyproject.toml:
The endpoints appear with zero config — pico-boot auto-discovers the module."pico-actuator>=0.2.2", - Optional config in
application.yaml(all fields have defaults):actuator: show_components: true # per-indicator detail in /health check_timeout_seconds: 5.0 # per-indicator time budget info: app: my-service - Contribute a health indicator — a
@componentsatisfying theHealthIndicatorprotocol (nameattr +check()); no registration:
Indicators run concurrently, each bounded byfrom pico_ioc import component @component class DbHealth: name = "db" def __init__(self, engine: Engine): self.engine = engine def check(self): # sync or async; dict or truthy self.engine.connect().close() return {"status": "UP"}check_timeout_seconds. A raising or timed-out indicator reports its componentDOWN— the endpoint never 500s. - Contribute /info data the same way with
contribute() -> dict(InfoContributorprotocol).
Rules
- Keep
check()cheap; cache expensive probes (indicators are singletons — store the last result + timestamp onself). - Never point
livenessProbeat/healthor/health/ready: a slow dependency would restart healthy pods. - Put only recoverable dependencies behind readiness (database, broker).
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.

