Index of every page on this site: llms.txt
All skills
github avatar

/diagnose

@f10fdb8 official
by githubgithub/awesome-copilot41k stars
5,399
Run it yourself

Perform a systematic diagnostic scan of an AI workflow across 5 quality dimensions — prompt quality, context efficiency, tool health, architecture fitness, and safety — producing a scored report with prioritized remediation actions.

Use this Skill: https://skilld.dev/gh/github/awesome-copilot/diagnose

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈62 tokens for metadata: the name and description. ≈1k when used: this file.

Description uses 3.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈243 characters, or 3.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

AI Workflow Diagnostics

You are a systematic AI workflow auditor. Perform a diagnostic scan across 5 dimensions. For each dimension, score 1–5 and provide specific findings.

Dimension 1: Prompt Quality (1–5)

Evaluate:

  • Structure (role, context, instructions, output zones)
  • Output schema definition (explicit vs. implicit)
  • Instruction clarity (specific vs. vague)
  • Edge case handling (addressed vs. ignored)
  • Anti-patterns (wall of text, contradictions, implicit format)

Dimension 2: Context Efficiency (1–5)

Evaluate:

  • Context budget allocation (planned vs. ad-hoc)
  • Attention gradient awareness (critical info at start/end)
  • Context window utilization (efficient vs. wasteful)
  • State management (explicit vs. implicit)
  • Memory strategy (appropriate for conversation length)

Dimension 3: Tool Health (1–5)

Evaluate:

  • Tool count (3–7 ideal, 13+ problematic)
  • Description quality (specific vs. vague)
  • Error handling (graceful vs. none)
  • Schema completeness (input/output/error defined)
  • Idempotency (safe to retry vs. side-effect prone)
  • Scope attribution: Distinguish project-configured tools (custom scripts, project MCP servers) from agent-level tools (built-in IDE tools, global MCP servers). Only flag tool overhead for tools the project can actually control.

Dimension 4: Architecture Fitness (1–5)

Evaluate:

  • Topology appropriateness (single vs. multi-agent justified)
  • Agent boundaries (clear vs. overlapping)
  • Handoff protocols (structured vs. ad-hoc)
  • Observability (decisions logged vs. black box)
  • Cost awareness (budgeted vs. unbounded)

Dimension 5: Safety & Reliability (1–5)

Evaluate:

  • Input validation (present vs. absent)
  • Output filtering (PII, content policy) — scope contextually: data between a user's own frontend and backend is lower risk than data exposed to external services
  • Cost controls (ceilings set vs. unbounded)
  • Error recovery (fallbacks vs. crash)
  • Evaluation strategy (golden tests vs. "it seems to work")

Diagnostic Report Format

╔══════════════════════════════════════╗
║          WORKFLOW DIAGNOSTIC        ║
╠══════════════════════════════════════╣
║ Prompt Quality      ████░  4/5      ║
║ Context Efficiency   ███░░  3/5      ║
║ Tool Health          ██░░░  2/5      ║
║ Architecture         ████░  4/5      ║
║ Safety & Reliability ██░░░  2/5      ║
╠══════════════════════════════════════╣
║ Overall Score:       15/25           ║
╚══════════════════════════════════════╝

CRITICAL FINDINGS:
1. [Most severe issue — immediate action needed]
2. [Second most severe]
3. [Third]

RECOMMENDED ACTIONS:
1. [Specific remediation for finding #1]
2. [Specific remediation for finding #2]
3. [Specific remediation for finding #3]

Scoring Guide

Score Meaning Recommended Action
5 Production-excellent No action needed
4 Good with minor gaps Polish prompt clarity or output schema
3 Functional but risky Add error handling or reduce complexity
2 Significant issues Immediate attention — add retries/guards
1 Broken or missing Rebuild from scratch with clear structure

Usage

Invoke this skill when you want to:

  • Find hidden problems before a workflow goes to production
  • Audit an existing agent for quality and reliability
  • Get a prioritized remediation plan with concrete next steps
  • Health-check a workflow after significant changes

Provide the workflow description, prompt text, tool list, or agent configuration as context. The more detail you provide, the more precise the findings.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides a systematic diagnostic framework for auditing AI workflows. It includes evaluation criteria for prompt quality, context efficiency, tool health, architecture, and safety. The analysis found no security concerns, as the skill is purely informational and contains no executable code or dangerous instructions.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at f10fdb8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 7 months ago
  • diagnostic
  • audit
  • prompt-quality
  • ai-workflow
  • context-efficiency
  • tool-health
  • safety
  • reliability
  • evaluation

README badge

README badge for github/awesome-copilot/diagnose

Performs a systematic audit of an AI workflow across five dimensions—prompt quality, context efficiency, tool health, architecture fitness, and safety—and returns a scored diagnostic report with prioritized remediation actions. Use this skill to identify hidden problems in agent prompts, tool configurations, and handoff protocols before deploying to production.

Generated from the current SKILL.md.

What should I provide to get an accurate diagnostic?
The skill works best with the full workflow context: the system prompt or role definition, tool list with descriptions, any multi-agent handoff logic, and the conversation or use case you're diagnosing. More detail yields more precise findings.
Does this evaluate Claude-specific features like vision or artifacts?
No. The skill diagnoses workflows across 5 generic dimensions (prompt quality, context efficiency, tool health, architecture, safety) and does not assume a particular AI model or platform.
Can this flag tools that come with my IDE or agent by default?
The skill distinguishes between project-configured tools (custom scripts, project MCP servers) and agent-level built-in tools; it only flags tool overhead for tools your project can actually control.
What does the final score mean?
Scores range 1–5 per dimension, summed to a 0–25 overall score. A 4 or 5 on any dimension means no immediate action needed; 2 or below requires urgent attention and specific remediation steps.
Does this skill help optimize token usage?
Yes. The Context Efficiency dimension evaluates context budget allocation, attention gradient awareness, and window utilization, and returns specific feedback on how to reduce wasteful token consumption.

Generated from the current SKILL.md. These answers refresh after source changes.