Skill Compliance Check Tool

Task Objectives

• This Skill is used to: check whether one or more Skills comply with best practice specifications
• Capabilities include: reading Skill files, verifying naming, preface section, directory structure, file cleanup, dependency metadata and other dimensions, generating inspection reports
• Trigger conditions: when users need to verify Skill quality, such as "Check if all skills comply with specifications", "Verify skill directory structure", "Check if this skill meets requirements"

Preparations

• No special dependencies

Operation Steps

Standard Process

Step 1: Read Inspection Specifications

• Read references/checklist.md to understand the complete 19-item inspection checklist
• Read references/quality-standards.md to understand the background explanations of each inspection item

Step 2: Check a Single Skill

• Read the

  SKILL.md

  file of the target Skill
• Check the directory structure and file list
• Verify item by item according to the 19-item inspection checklist in checklist.md:
  1. Naming specification check (3 items): directory name format, directory name suffix, best practice suffix
  2. Preface section check (5 items): name field exists, name matches directory name, description exists, description is single-line, description length
  3. Directory structure check (3 items): SKILL.md exists, fixed structure directories, empty directory check
  4. File cleanup check (1 item): temporary file cleanup
  5. Dependency metadata check (2 items): dependency.python format, dependency.system format
  6. README.md record check (5 items): README.md exists, skills/ directory exists, Skill is in skills/, Skill is recorded, record format is correct

Step 3: Batch Check Multiple Skills (Automatic Traversal)

• Check if Skills are located under the

  skills/

  directory
• Use the directory traversal command to list all Skills under the target directory:
  bash

  find /workspace/projects/skills -maxdepth 1 -name "SKILL.md" -exec dirname {} \;

• After obtaining the list of all Skill directories, repeat the inspection process in Step 2 for each Skill

Step 4: Generate Inspection Report

• Summarize all inspection results
• Generate a report for each Skill, including:
  • Details of 19 inspection items (pass/warning/error)
  • Overall status (pass/warning/error)
  • Repair suggestions
• Provide overall statistics: number of Skills, pass rate, most common issues

Step 5: Issue Repair (Optional)

• If issues are found during inspection, perform repairs according to user needs:
  • Automatic repair: For issues that can be safely repaired automatically (such as deleting temporary files, deleting empty directories), perform repairs directly
  • Manual confirmation: For issues that require judgment (such as renaming directories, modifying description, modifying name field), provide repair suggestions and wait for user confirmation
• Refer to the inspection level explanations and repair suggestions in references/quality-standards.md
• Re-verify after repair to confirm that the issue has been resolved and no new issues have been introduced

Resource Index

• Inspection Checklist: See references/checklist.md
  • Content: Complete 19-item Skill inspection checklist (naming specifications, preface section, directory structure, file cleanup, dependency metadata, README.md records)
  • When to read: Read before starting the inspection, and compare item by item during the inspection process
• Quality Standards: See references/quality-standards.md
  • Content: Background explanations of each inspection item, definition of passing standards, inspection level explanations (pass/warning/error)
  • When to read: Refer to when understanding the background of inspection items and determining repair priorities

Notes

• When performing batch checks, it is recommended to process a large number of Skills in batches
• Must re-verify after repairing issues

Usage Examples

Example 1: Check a Single Skill

1. Read inspection specifications
2. Read

   /workspace/projects/check-all-skills/SKILL.md

3. Check directory structure
4. Verify checklist items one by one
5. Output inspection report

Example 2: Batch Check Multiple Skills (Automatic Traversal)

1. Read inspection specifications
2. Use the command in Step 3 to list all Skills under this directory
3. Execute the inspection process in Step 2 for each Skill
4. Generate a summary report

Example 3: Check and Automatically Repair Issues

1. Read inspection specifications and issue repair guidelines
2. Use the command in Step 3 to identify all Skills in the current working directory
3. Execute the inspection process in Step 2 for each Skill
4. Perform repairs according to Step 5:
   • For issues that can be automatically repaired: perform repairs directly
   • For issues requiring confirmation: provide repair suggestions and ask the user for consent
5. Re-verify after repair
6. Generate a repair report

Example 4: Check Specific Dimensions

1. Only check items related to naming specifications
2. Only check items related to directory structure
3. Output the results of these two types of inspections