Skip to content
TrustedSkillsbeta
Back to all skills

Crap Analysis

Checked
aaronontheweb·vlatest·devops·MIT

Quickly identifies nonsensical or illogical statements in text, flagging potential errors or misleading information.

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 aaronontheweb/dotnet-skills --skill crap-analysis -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

aaronontheweb

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 aaronontheweb/dotnet-skills at e426ed93a9.

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

Commit
e426ed93a9
Manifest
skills/crap-analysis/SKILL.md
Scanned
1 file, 366 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, Crap Analysis, calculates a CRAP (Change Risk Anti-Patterns) score for code to identify potentially risky areas needing refactoring or testing. The CRAP score combines cyclomatic complexity (a measure of code intricacy) with test coverage data. A higher CRAP score indicates greater risk associated with modifying the code. This helps prioritize testing and development efforts.

When to use it

  • Evaluating code quality before making changes.
  • Identifying high-risk code that requires refactoring or additional testing.
  • Setting up automated test coverage collection for .NET projects.
  • Prioritizing which parts of the codebase need the most attention during testing.
  • Establishing thresholds for continuous integration/continuous delivery (CI/CD) pipelines based on code risk.

Key capabilities

  • Calculates a CRAP score using cyclomatic complexity and test coverage.
  • Provides a risk level assessment (Low, Medium, High) based on the calculated CRAP score.
  • Requires a coverage.runsettings file in the repository root for OpenCover format data collection.
  • Supports excluding specific files and attributes from coverage analysis.

Example prompts

  • "Calculate the CRAP score for this code."
  • "What is the risk level of this method?"
  • "Show me the methods with a CRAP score greater than 30."

Tips & gotchas

  • Requires an OpenCover-formatted coverage.runsettings file to be present in the repository root for accurate calculation.
  • The skill focuses on .NET projects and relies on cyclomatic complexity metrics included in the OpenCover format.
  • A high CRAP score doesn't always mean code is bad, but it does indicate a need for closer inspection and potential improvement.