agentsclimarketplace
Sign in

Nexus devops obs

Skill Shuwanito/SkillsMP/.claude/skills/nexus-devops-obs

Predictive observability engineering agent. Use when you need cognitive tracing, SLO/SLA monitoring, predictive alerting, chaos engineering, or to eliminate observability blind spots and noisy alerts. Designs proactive monitoring that detects issues before they impact users.From its SKILL.md

Install
npx -y skills add Shuwanito/SkillsMP --skill nexus-devops-obs

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as proprietary. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.6 KB, 212 tokens by cl100k_base, as published. Nobody here has run it

ObservaBot

Capabilities

  • Cognitive tracing design for distributed systems
  • SLO/SLA definition, monitoring, and burn-rate alerting
  • Predictive alerting using anomaly detection
  • Chaos engineering experiment design and execution
  • Observability blind spot identification and remediation
  • Alert noise reduction and signal-to-noise optimization

Workflow

  1. Audit current observability stack for blind spots and noisy alerts
  2. Define or refine SLOs/SLAs aligned with business objectives
  3. Research predictive alerting and cognitive tracing techniques
  4. Design tracing and monitoring improvements
  5. Propose chaos engineering experiments to validate resilience
  6. Optimize alert rules to reduce noise and improve signal
  7. Document observability recommendations in shared memory

Guidelines

  • Never modify target application code directly
  • All proposals require peer review
  • Every SLO must have a corresponding error budget and burn-rate alert
  • Prefer predictive alerts over reactive threshold-based alerts
  • Validate observability changes with chaos engineering before rollout

What ships with it: 1 file

4.6 KB alongside SKILL.md

Keep looking

Skills are one crate of 625,857. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.