/check-prompt
Evaluate and improve AI prompt quality. Trigger with "check this prompt", "evaluate prompt quality", "improve this prompt".
$ npx -y skills add wasabeef/claude-code-cookbook --skill check-prompt --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition โ
- You can call itInvoke it directly when you want it.
- Slash command
/check-prompt
Context preview
The summary Claude sees to decide when to auto-load this skill.
Evaluate and improve AI prompt quality. Trigger with "check this prompt", "evaluate prompt quality", "improve this prompt".
SKILL.md
check-prompt.SKILL.mddescription: 'Evaluate and improve AI prompt quality. Trigger with "check this prompt", "evaluate prompt quality", "improve this prompt".'
allowed-tools:
- Read
- Grep
Evaluate and improve AI prompt quality
A comprehensive collection of best practices for evaluating and improving the quality of prompts for AI Agents. It systematizes knowledge gained from actual prompt improvement processes, covering all important aspects such as ambiguity elimination, information integration, enforcement enhancement, tracking systems, and continuous improvement.
Usage
# Check the quality of a prompt file
cat your-prompt.md
/check-prompt
"Check the quality of this prompt and suggest improvements"
Options
- None: Analyze current file or selected text
- `--category <name>`: Check only specific category (structure/execution/restrictions/quality/roles/improvement)
- `--score`: Calculate quality score only
- `--fix`: Automatically suggest fixes for detected issues
- `--deep`: Deep analysis mode (focus on ambiguity, information dispersion, and enforcement)
Basic Examples
# Evaluate overall prompt quality
cat devin/playbooks/code-review.md
/check-prompt
"Evaluate this prompt across 6 categories and suggest improvements"
# Deep analysis mode
/check-prompt --deep
"Focus on checking ambiguity, information dispersion, and lack of enforcement to suggest fundamental improvements"
# Check specific category
/check-prompt --category structure
"Check this prompt from the perspective of structure and clarity"
# Detect and fix ambiguous expressions
/check-prompt --fix
"Detect ambiguous expressions and suggest corrections for clarity"
---
Core Design Principles
Principle 1: Completely Eliminate Room for Interpretation
- **Absolutely Prohibited**: "In principle", "Recommended", "If possible", "Depending on the situation", "Use your judgment"
- **Must Use**: "Always", "Absolutely", "Strictly observe", "Without exception", "Mandatory"
- **Exception Conditions**: Strictly limited by numbers ("Only under the following 3 conditions", "Except in these 2 cases")
Principle 2: Strategic Integration of Information
- Completely integrate related important information into one section
- Summarize the overall picture in an execution checklist
- Thoroughly eliminate circular references and dispersion
Principle 3: Building Gradual Enforcement
- Clear hierarchy of ๐ด (Execution stop level) โ ๐ก (Quality important) โ ๐ข (Recommended items)
- Gradual upgrade from recommended to mandatory level
- Explicit indication of impact and countermeasures for violations
Principle 4: Ensuring Traceability
- All execution results can be recorded and verified
- Technically prevent false reporting
- Objective criteria for success/failure judgment
Principle 5: Feedback-Driven Improvement
- Learn from actual failure cases
- Continuous effectiveness verification
- Automatic detection of new patterns
---
๐ Comprehensive Check Items
1. ๐ Structure and Clarity (Weight: 25 points)
1.1 Priority Indication of Instructions (8 points)
- [ ] ๐ด๐ก๐ข priorities are clearly indicated for all important instructions
- [ ] Conditions for execution stop level are specifically and clearly defined
- [ ] Criteria for each priority level are objective and verifiable
- [ ] Priority hierarchy is consistently applied
1.2 Complete Elimination of Ambiguous Expressions (9 points)
- [ ] **Fatal ambiguous expressions**: 0 instances of "In principle", "Recommended", "If possible"
- [ ] **Use of mandatory expressions**: Appropriate use of "Always", "Absolutely", "Strictly observe", "Without exception"
- [ ] **Numerical limitation of exception conditions**: Clear boundaries like "Only 3 conditions"
- [ ] **Elimination of judgment room**: Use only expressions that cannot be multiple interpreted
- [ ] **Elimination of gray zones**: Clear judgment criteria for all situations
1.3 Strategic Integration of Information (8 points)
- [ ] Multiple location dispersion of important information is completely eliminated
- [ ] Related instructions are logically integrated into one section
- [ ] The overall picture is completely summarized in the execution checklist
- [ ] There are no circular references or infinite loops
2. ๐ฏ Executability (Weight: 20 points)
2.1 Completeness of Specific Procedures (7 points)
- [ ] All command examples are actually executable and verified
- [ ] Environment variables, prerequisites, and dependencies are clearly stated without omissions
- [ ] Error handling methods are specific and executable
- [ ] The order of procedures is logical and necessary
2.2 Ensuring Verifiability (7 points)
- [ ] Success/failure of execution results can be objectively determined
- [ ] Output examples, log formats, and expected values are specifically shown
- [ ] Testing methods and verification procedures can be implemented
- [ ] Checkpoints for confirming intermediate results are appropriately placed
2.3 Automation Adaptability (6 points)
- [ ] Format that allows easy scripting and CI/CD integration
- [ ] Clear separation between human judgment and AI execution points
- [ ] Support for batch processing and parallel execution
3. ๐ซ Clarification of Prohibited Items (Weight: 15 points)
3.1 Systematization of Absolute Prohibitions (8 points)
- [ ] Complete list of operations that must not be performed
- [ ] Explicit indication of impact level (minor/major/fatal) for each prohibited item violation
- [ ] Specific presentation of alternatives and avoidance methods
- [ ] Explanation of technical basis for prohibited items
3.2 Strict Limitation of Exception Conditions (7 points)
- [ ] Conditions allowing exceptions are specific and limited (numerical specification)
- [ ] Objective judgment criteria such as "Completely duplicate", "Explicitly stated"
- [ ] Clear boundaries without leaving gray zones
- [ ] Explicit indication of additional conditions and
Read more
description: 'Evaluate and improve AI prompt quality. Trigger with "check this prompt", "evaluate prompt quality", "improve this prompt".' allowed-tools: - Read - Grep
Evaluate and improve AI prompt quality
A comprehensive collection of best practices for evaluating and improving the quality of prompts for AI Agents. It systematizes knowledge gained from actual prompt improvement processes, covering all important aspects such as ambiguity elimination, information integration, enforcement enhancement, tracking systems, and continuous improvement.
Usage
# Check the quality of a prompt file cat your-prompt.md /check-prompt "Check the quality of this prompt and suggest improvements"
Options
- None: Analyze current file or selected text
- `--category <name>`: Check only specific category (structure/execution/restrictions/quality/roles/improvement)
- `--score`: Calculate quality score only
- `--fix`: Automatically suggest fixes for detected issues
- `--deep`: Deep analysis mode (focus on ambiguity, information dispersion, and enforcement)
Basic Examples
# Evaluate overall prompt quality cat devin/playbooks/code-review.md /check-prompt "Evaluate this prompt across 6 categories and suggest improvements" # Deep analysis mode /check-prompt --deep "Focus on checking ambiguity, information dispersion, and lack of enforcement to suggest fundamental improvements" # Check specific category /check-prompt --category structure "Check this prompt from the perspective of structure and clarity" # Detect and fix ambiguous expressions /check-prompt --fix "Detect ambiguous expressions and suggest corrections for clarity"
---
Core Design Principles
Principle 1: Completely Eliminate Room for Interpretation
- **Absolutely Prohibited**: "In principle", "Recommended", "If possible", "Depending on the situation", "Use your judgment"
- **Must Use**: "Always", "Absolutely", "Strictly observe", "Without exception", "Mandatory"
- **Exception Conditions**: Strictly limited by numbers ("Only under the following 3 conditions", "Except in these 2 cases")
Principle 2: Strategic Integration of Information
- Completely integrate related important information into one section
- Summarize the overall picture in an execution checklist
- Thoroughly eliminate circular references and dispersion
Principle 3: Building Gradual Enforcement
- Clear hierarchy of ๐ด (Execution stop level) โ ๐ก (Quality important) โ ๐ข (Recommended items)
- Gradual upgrade from recommended to mandatory level
- Explicit indication of impact and countermeasures for violations
Principle 4: Ensuring Traceability
- All execution results can be recorded and verified
- Technically prevent false reporting
- Objective criteria for success/failure judgment
Principle 5: Feedback-Driven Improvement
- Learn from actual failure cases
- Continuous effectiveness verification
- Automatic detection of new patterns
---
๐ Comprehensive Check Items
1. ๐ Structure and Clarity (Weight: 25 points)
1.1 Priority Indication of Instructions (8 points)
- [ ] ๐ด๐ก๐ข priorities are clearly indicated for all important instructions
- [ ] Conditions for execution stop level are specifically and clearly defined
- [ ] Criteria for each priority level are objective and verifiable
- [ ] Priority hierarchy is consistently applied
1.2 Complete Elimination of Ambiguous Expressions (9 points)
- [ ] **Fatal ambiguous expressions**: 0 instances of "In principle", "Recommended", "If possible"
- [ ] **Use of mandatory expressions**: Appropriate use of "Always", "Absolutely", "Strictly observe", "Without exception"
- [ ] **Numerical limitation of exception conditions**: Clear boundaries like "Only 3 conditions"
- [ ] **Elimination of judgment room**: Use only expressions that cannot be multiple interpreted
- [ ] **Elimination of gray zones**: Clear judgment criteria for all situations
1.3 Strategic Integration of Information (8 points)
- [ ] Multiple location dispersion of important information is completely eliminated
- [ ] Related instructions are logically integrated into one section
- [ ] The overall picture is completely summarized in the execution checklist
- [ ] There are no circular references or infinite loops
2. ๐ฏ Executability (Weight: 20 points)
2.1 Completeness of Specific Procedures (7 points)
- [ ] All command examples are actually executable and verified
- [ ] Environment variables, prerequisites, and dependencies are clearly stated without omissions
- [ ] Error handling methods are specific and executable
- [ ] The order of procedures is logical and necessary
2.2 Ensuring Verifiability (7 points)
- [ ] Success/failure of execution results can be objectively determined
- [ ] Output examples, log formats, and expected values are specifically shown
- [ ] Testing methods and verification procedures can be implemented
- [ ] Checkpoints for confirming intermediate results are appropriately placed
2.3 Automation Adaptability (6 points)
- [ ] Format that allows easy scripting and CI/CD integration
- [ ] Clear separation between human judgment and AI execution points
- [ ] Support for batch processing and parallel execution
3. ๐ซ Clarification of Prohibited Items (Weight: 15 points)
3.1 Systematization of Absolute Prohibitions (8 points)
- [ ] Complete list of operations that must not be performed
- [ ] Explicit indication of impact level (minor/major/fatal) for each prohibited item violation
- [ ] Specific presentation of alternatives and avoidance methods
- [ ] Explanation of technical basis for prohibited items
3.2 Strict Limitation of Exception Conditions (7 points)
- [ ] Conditions allowing exceptions are specific and limited (numerical specification)
- [ ] Objective judgment criteria such as "Completely duplicate", "Explicitly stated"
- [ ] Clear boundaries without leaving gray zones
- [ ] Explicit indication of additional conditions and
A collection of commands, roles, and automation scripts for Claude Code. Automate your workflow without unnecessary confirmations, allowing you to focus on what matters.
Repo: wasabeef/claude-code-cookbook
Other skills on claude-code-cookbook.
- /analyze-dependencies
Analyze project dependencies and evaluate architectural health. Trigger with "analyze dependencies", "detect circular dependencies", "architecture issues?", "check module coupling", "find layer violations". Generates dependency matrix, fan-in/fan-out analysis, and prioritized
Open skill - /analyze-performance
Performance analysis based on Core Web Vitals with UX scoring. Trigger with "analyze performance", "improve speed", "check Core Web Vitals", "page speed", "improve LCP", "identify performance issues".
Open skill - /check-fact
Verify information accuracy against codebase and documentation. Trigger with "is this correct?", "fact check", "verify this", "is this accurate?".
Open skill - /commit-message
Generate commit messages from staged changes. Trigger with "suggest commit message", "generate commit message", "what should the commit say?", "write commit message".
Open skill - /context7
Search technical documentation via Context7 MCP. Trigger with "check the docs", "look up documentation", "how to use this library?", "API reference".
Open skill - /design-patterns
Suggest design patterns and evaluate SOLID principles. Trigger with "suggest design patterns", "which patterns apply?", "check SOLID principles", "detect anti-patterns", "evaluate code design".
Open skill

