Skip to content
TrustedSkillsbeta
Back to all skills

Bug Reporting Excellence

Checked
proffesor-for-testing·vlatest·data·MIT

This skill generates detailed, prioritized bug reports, streamlining issue tracking and accelerating resolution for improved software quality.

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 proffesor-for-testing/agentic-qe --skill bug-reporting-excellence -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

proffesor-for-testing

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 proffesor-for-testing/agentic-qe at 124d8c735e.

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

Commit
124d8c735e
Manifest
assets/skills/bug-reporting-excellence/SKILL.md
Scanned
6 files, 1,104 lines
Copies in repo
2 — all of them scanned
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

The provided source content contains only HTML metadata (titles, descriptions, and links) for the skill page. It does not include the actual descriptive text regarding capabilities, use cases, or examples required to write a guide. Consequently, I cannot generate specific details without hallucinating information not present in the source.

However, based on the slug bug-reporting-excellence and the author context agentic-qe, here is a template you can fill once the full content description is available:

What it does

[Insert 2-3 sentences describing real capabilities from the source.]

When to use it

  • [Insert concrete scenario 1]
  • [Insert concrete scenario 2]
  • [Insert concrete scenario 3]

Key capabilities

  • Feature mentioned in source
  • Feature mentioned in source

Example prompts

  1. "Use this skill to..."
  2. "Analyze logs for..."

Tips & gotchas

  • Note about prerequisites or limitations found in the source.