Source profileQuality 70/100

github/awesome-copilot/skills/diagnose/SKILL.md

diagnose

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.

Source repository stars
37,126
Declared platforms
0
Static risk flags
0
Last source update
2026-07-28
Source checked
2026-07-28
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSource

Decision brief

What it does—and where it fits

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

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/github/awesome-copilot --skill "skills/diagnose"
    Safe inspection promptEditorial

    Inspect the Agent Skill "diagnose" from https://github.com/github/awesome-copilot/blob/9933dcad5be5caeb288cebcd370eeeb2fc2f1685/skills/diagnose/SKILL.md at commit 9933dcad5be5caeb288cebcd370eeeb2fc2f1685. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      Usage

      Invoke this skill when you want to:

      Find hidden problems before a workflow goes to productionAudit an existing agent for quality and reliabilityGet a prioritized remediation plan with concrete next steps
    2. 02

      Dimension 1: Prompt Quality (1–5)

      Structure (role, context, instructions, output zones)

      Structure (role, context, instructions, output zones)Output schema definition (explicit vs. implicit)Instruction clarity (specific vs. vague)
    3. 03

      Dimension 2: Context Efficiency (1–5)

      Context budget allocation (planned vs. ad-hoc)

      Context budget allocation (planned vs. ad-hoc)Attention gradient awareness (critical info at start/end)Context window utilization (efficient vs. wasteful)
    4. 04

      Dimension 3: Tool Health (1–5)

      Tool count (3–7 ideal, 13+ problematic)

      Tool count (3–7 ideal, 13+ problematic)Description quality (specific vs. vague)Error handling (graceful vs. none)

    Permission review

    Static risk signals and limitations

    No configured static risk pattern was detected

    This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score70/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars37,126SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    github/awesome-copilot
    Skill path
    skills/diagnose/SKILL.md
    Commit
    9933dcad5be5caeb288cebcd370eeeb2fc2f1685
    License
    MIT
    Collected
    2026-07-28
    Default branch
    main
    View the original SKILL.md

    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

    ScoreMeaningRecommended Action
    5Production-excellentNo action needed
    4Good with minor gapsPolish prompt clarity or output schema
    3Functional but riskyAdd error handling or reduce complexity
    2Significant issuesImmediate attention — add retries/guards
    1Broken or missingRebuild 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.

    Alternatives

    Compare before choosing

    Computed 6145

    griffinwork40/agent-afk

    diagnose

    Parallel root-cause analysis for bugs and failing tests. Use when a test fails, a bug is reported, or behavior is unexplained — dispatches sub-agents to form and validate hypotheses in isolated worktrees.

    2026-07-280 platforms
    Computed 997

    event4u-app/agent-config

    design-review

    Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more.

    2026-07-280 platforms
    Computed 9831,966

    K-Dense-AI/scientific-agent-skills

    dask

    Distributed computing for larger-than-RAM pandas/NumPy workflows. Use when you need to scale existing pandas/NumPy code beyond memory or across clusters. Best for parallel file processing, distributed ML, integration with existing pandas code. For out-of-core analytics on single machine use vaex; for in-memory speed use polars.

    2026-07-280 platforms
    Computed 9831,966

    K-Dense-AI/scientific-agent-skills

    neurokit2

    Use NeuroKit2 to build or audit reproducible research workflows for physiological time-series preprocessing, event/interval analysis, multimodal alignment, variability, and complexity. Trigger when code imports neurokit2 or needs its current APIs, schemas, and method-aware validation—not for diagnosis or device validation.

    2026-07-280 platforms