Skip to main content

general-quality

General response quality evaluation. Always applicable regardless of domain. Covers response structure, actionability, clarity, and hallucination detection.

Quellinformationen

Repository
databricks-solutions/ai-dev-kit
Letzte Quellaktivität
16. März 2026 um 17:21
Erkannte Sprache von SKILL.md
Englisch
Sterne
1.942
Forks
428

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

SKILL.md wird angezeigt

SKILL.md
Quellanweisungen · Schreibgeschützte Vorschau
name
general-quality
description
General response quality evaluation. Always applicable regardless of domain. Covers response structure, actionability, clarity, and hallucination detection.
metadata
{"category":"evaluation","version":"1.0","applies_to":[]}
## General Quality Rubric When evaluating any Claude Code agent trace, check these dimensions: ### 1. Actionable Output - Can the user directly use the response (copy-paste code, follow steps)? - Are code examples complete and runnable, not fragments? - Are file paths, table names, and API references concrete? ### 2. Structured Response - Code is in fenced code blocks with correct language tags - Steps are numbered or bulleted for multi-step tasks - Explanations are concise — answer first, context after ### 3. No Hallucination - All referenced APIs, functions, and parameters must actually exist - Databricks features must be current (not deprecated) - Tool names in traces must match real MCP tool names - No invented catalog/schema/table names unless the user specified them ### 4. Conciseness - Answers the question without excessive preamble or disclaimers - Doesn't repeat the question back - Doesn't explain basic concepts the user didn't ask about ### 5. Error Handling - If the agent encountered errors during execution, did it recover? - Did it explain errors to the user when relevant? - Did it avoid silently swallowing failures?
Auf GitHub ansehen