otel-remediate
Skill1 starsChanged 49 days agoApache-2.0View on GitHub
Propose a deployment-config diff (env vars / manifest fields) for a service with no application source to bootstrap but real native OTel support — e.g. a Keycloak deployment. Use for generatorSupported:false, inScope:true services that /otel-instrument refuses.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- otel-backendSkill
- otel-business-attrsSkill
- otel-collectorSkill
- otel-evaluateSkill
- otel-initSkill
- otel-instrumentSkill
- otel-uninstrumentSkill
- semconv-disciplineSkill
- new-backendSkill
- validate-pluginSkill
- business-attr-uxSkill
- collector-topologySkill
- deployment-remediationSkill
- language-maturitySkill
- semconv-disciplineSkill
- terraform-patternsSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
Follow the canonical procedure in this repo — it is the single source of truth:
- Very specific: line 12
Read commands/otel-remediate.md (repo root) and execute its steps.
- Very specific: line 15
Read skills/deployment-remediation/SKILL.md for the known-targets table (v1: Keycloak only) and the verified env var list — do not guess at …
≈ “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.
Files
otel-remediate (Codex bridge)
Requires the otel-as-code repo. The
commands//skills//agents/files referenced below live there — if they're not present in your workspace, stop and tell the user to add the repo (see AGENTS.md).
Follow the canonical procedure in this repo — it is the single source of truth:
- Read
commands/otel-remediate.md(repo root) and execute its steps. - Codex has no subagent dispatch: where it says to run the
deployment-remediation-genagent, readagents/deployment-remediation-gen.mdand perform that read-only diff-proposal yourself. - Read
skills/deployment-remediation/SKILL.mdfor the known-targets table (v1: Keycloak only) and the verified env var list — do not guess at another binary's config surface by analogy.
Args: $ARGUMENTS.
This workflow is print-only by design — it proposes a unified diff against the service's deployment manifest(s) and never writes it. Refuse plainly for any target not in the skill's known-targets table rather than guessing.
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.