Skip to content
TrustedSkillsbeta
Back to all skills

Team Quality Assurance

Checked
catlog22·vlatest·testing·MIT

This skill analyzes team communications for quality issues like tone, clarity, and consistency, boosting collaboration & reducing misunderstandings.

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 catlog22/claude-code-workflow --skill team-quality-assurance -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

catlog22

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 catlog22/claude-code-workflow at 07491b04ac.

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

Commit
07491b04ac
Manifest
.codex/skills/team-quality-assurance/SKILL.md
Scanned
24 files, 2,670 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

What it does

This skill, Team Quality Assurance, orchestrates a multi-agent workflow to analyze team communications for quality issues related to tone, clarity, and consistency. It utilizes a sequence of specialized agents – scout, strategist, generator, executor, and analyst – to perform discovery, testing, and closed-loop analysis. The system supports parallel generation and iterative refinement (GC loops) within its workflow.

When to use it

  • Analyzing communication patterns in a software development team to identify areas for improvement.
  • Evaluating the effectiveness of team collaboration strategies and identifying potential misunderstandings.
  • Automating quality assurance processes related to team interactions, such as code reviews or documentation feedback.
  • Implementing closed-loop testing workflows where generated outputs are analyzed and iteratively refined.

Key capabilities

  • Multi-agent orchestration: Coordinates a sequence of specialized agents (scout, strategist, generator, executor, analyst).
  • Role-based architecture: Each agent operates within a defined role with specific responsibilities as outlined in roles/<role>/role.md.
  • Parallel generation: Supports the simultaneous creation of multiple outputs for faster analysis.
  • Closed-loop workflows: Enables iterative refinement through GC (generation and correction) loops.
  • Dynamic executor loop: The executor role has a dynamic inner loop, suggesting adaptable execution paths.

Example prompts

  • "Analyze team communications regarding the new feature implementation."
  • "Run a quality assurance workflow on our recent code review discussions."
  • "Evaluate the clarity and consistency of documentation feedback provided by the team."

Tips & gotchas

  • The skill requires understanding of the individual agent roles (scout, strategist, generator, executor, analyst) to effectively interpret results.
  • The coordinator role manages the overall workflow; ensure it is properly configured for optimal performance.
  • The executor role's dynamic inner loop suggests that its behavior may vary depending on the task at hand.