Skip to content
TrustedSkillsbeta
Back to all skills

Silent Degradation Audit

Checked
rysweet·vlatest·other

Identifies subtle performance declines in systems over time, revealing hidden degradation risks before major failures occur.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add rysweet/amplihack --skill silent-degradation-audit -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

rysweet

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned rysweet/amplihack at 84424457d5.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
84424457d5
Manifest
.claude/skills/silent-degradation-audit/SKILL.md
Scanned
17 files, 4,314 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill performs an audit to identify and document instances of silent degradation in a system or process. It analyzes historical data, logs, and performance metrics to pinpoint subtle declines in quality that might not be immediately obvious. The resulting report highlights areas needing attention before they escalate into major issues.

When to use it

  • Proactive maintenance: Regularly assess critical systems (e.g., a customer service chatbot) to catch performance dips early.
  • Post-incident analysis: Investigate periods of reduced user satisfaction or unexpected errors to determine root causes.
  • After code deployments: Verify that new releases haven't introduced subtle regressions in system behavior.
  • Monitoring complex workflows: Track the efficiency and accuracy of multi-step processes, like order fulfillment or data processing pipelines.

Key capabilities

  • Historical Data Analysis
  • Log File Examination
  • Performance Metric Tracking
  • Report Generation

Example prompts

  • "Audit the customer service chatbot's response quality over the last month."
  • "Analyze server logs for signs of silent degradation in processing speed since the latest update."
  • "Generate a report on order fulfillment accuracy, highlighting any recent declines."

Tips & gotchas

The effectiveness of this skill depends heavily on having sufficient historical data and well-defined performance metrics. Without adequate baseline information, identifying "degradation" is difficult.