metrics-graphana
Skill8 starsChanged 11 days agoMITView on GitHub
Query Very Happy connection and RPC metrics, maintain its Grafana dashboard, and diagnose the private Prometheus collection path. Use for monitoring, Grafana, Prometheus, and connection-quality panels.
- Reads credentials
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Altman-conquer/agentrejointheir own version, first seen Apr 7, 2026
- slopus/happytheir own version, first seen Apr 7, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- slopus/happy★ 25ksame name
- Altman-conquer/agentrejoin★ 75same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-browserSkill
- control-flowSkill
- designSkill
- devSkill
- office-hoursSkill
- releaseSkill
- sessionsSkill
- agent-browserSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are 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.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Read docs/monitoring/README.md first: it owns the deployed topology, object names, data semantics and rollback.
- Very specific: line 24
Do not assume a repo .env, Basic Auth, or an initial Kubernetes admin Secret provides current Grafana access.
- Very specific: line 34
Start with up{job="very-happy"} and max(up{job="very-happy"}), then inspect browser_connection_stage_results_total and rpc_calls_total.
- Very specific: line 43
If the operator reconciles a new target but it is absent from runtime config, compare the generated Secret, the reloader's mounted config, …
≈ “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
Very Happy monitoring
Read docs/monitoring/README.md first: it owns
the deployed topology, object names, data semantics and rollback. Application
release remains owned by the release skill and docs/operations.md.
Choose the actual management path
- Production uses the existing sy Grafana/Prometheus stack. Reach its Kubernetes
API through
ssh k8s; verify host identity and current Service addresses before queries. A local kubeconfig context named sy is not evidence its credentials work. - The connection dashboard is managed by the dedicated ConfigMap documented in
the runbook. Edit
docs/monitoring/connection-quality.dashboard.json, resolve${DS_PROMETHEUS}to the verified existing data source UID when provisioning, and change only the owned ConfigMap after exporting its previous state. - Its existing provider has
allowUiUpdates=false. Do not switch to an API/UI overwrite, change the global provider, or install grafanactl just to update it. Other dashboards may have a different owner; inspect before changing them. - Do not assume a repo
.env, Basic Auth, or an initial Kubernetes admin Secret provides current Grafana access. An auth failure is not permission to reset a password. Never print credentials or persist session cookies in artifacts.
Query and verify
Resolve the Prometheus Service address using the cluster API, then query its
/api/v1/query or /api/v1/query_range from the authorized private host. Keep
operational artifacts under ~/code/github/skills/tmp/<task>/.
Start with up{job="very-happy"} and max(up{job="very-happy"}), then inspect
browser_connection_stage_results_total and rpc_calls_total. Use the checked-in
dashboard for PromQL; avoid duplicating expressions in this skill.
Creation of a ServiceMonitor or a dashboard is not verification. Check the Prometheus active targets, actual received samples, query responses, and the loaded dashboard's UID/data source separately. A stopped inactive blue-green slot is expected; absent samples are unknown, not zero failures or zero latency.
If the operator reconciles a new target but it is absent from runtime config,
compare the generated Secret, the reloader's mounted config, config_out, and
Prometheus /api/v1/status/config. The runbook records one stale reloader case;
do not infer every missing target needs a restart. Restore only the failed layer
within the authorized scope, then verify samples without restarting the TSDB.
Connection latency covers received, active foreground telemetry, not a complete availability SLO. Prefer a real operation on an owned account for verification; keep synthetic samples identifiable and out of mobile/region latency claims.
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.

