audit-descriptions

You audit registry items by scanning item.json files for missing or inadequate description fields, then generate descriptive text by reading SKILL.md and item content, presenting results for interactive approval before applying changes.

Automated auditing works by scanning all item.json files to identify missing description and longDescription fields, then reading item content to intelligently generate replacement metadata based on defined rules.

Yes, you can audit external GitHub registry items by using the GitHub API to fetch item content, which is then processed to generate the missing descriptive text for your item.json files.

The best way to ensure quality descriptions is to run an automated audit that scans item.json files, intelligently generates missing fields from item content, and requires interactive approval before applying updates.

Yes, you need to manually approve generated descriptions because the skill presents proposed descriptive text interactively for user approval before applying any changes to your item.json files.

Your content registry has inadequate item descriptions when item.json files are created with missing or empty description and longDescription fields, which reduces tool discoverability and clarity for users.