skills.rest
skillcreatorai
skillcreatoraiCOMMUNITY
Explore all skills by this author →
Website𝕏@skillcreatoraiGitHub

review-a-skill

Evaluates skill quality, frontmatter validity, and safety before library inclusion.

1.1k|131|Updated Dec 17, 2025
Search Tags:#curation#CLI#quality check#Validation#skill review#FrontMatter#library management
One-click install
npx skills add https://github.com/skillcreatorai/Ai-Agent-Skills --skill review-a-skill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-a-skill
Source: https://github.com/skillcreatorai/Ai-Agent-Skills/tree/main/skills/review-a-skill
Command: npx skills add https://github.com/skillcreatorai/Ai-Agent-Skills --skill review-a-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deciding whether a skill deserves a place in a curated library requires checking content quality, metadata completeness, and safety, which is tedious and error-prone when done manually.

Core Features & Use Cases

  • Content Preview: Sanitizes and previews skill content to flag suspicious patterns before review.
  • Metadata Inspection: Reads catalog entries with JSON output and field filtering to verify descriptions, tags, and dependencies.
  • Curation Workflow: Supports validating structure, adding review notes, verifying skills, and safely removing them with dry-run checks.
  • Use Case: Before accepting a community-submitted skill, preview its content for injection patterns, validate its SKILL.md frontmatter, check whether other skills depend on it, then curate or remove it with a dry run first.

Quick Start

Review the skill named 'pdf-tools' and tell me whether to keep, curate, or remove it from my library.

Frequently Asked Questions about review-a-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a skill before adding it to my library?▼

Preview the skill content with npx ai-agent-skills preview, inspect its catalog metadata with info --format json, and validate its SKILL.md structure. Then decide to keep, curate, or remove based on description clarity, frontmatter validity, and absence of injection patterns.

How to safely remove a skill from a library?▼

First check dependencies with info --format json to see if other skills depend on it via dependencies.usedBy. Then run curate with --remove --dry-run to preview the change before executing the actual removal with --yes.

Does the preview command work for all skills?▼

No, the preview command only works for vendored house skills stored locally. Upstream cataloged skills only show their description and whyHere fields, so content-level safety review is limited for those entries.

Why does skill validation pass but the skill is still low quality?▼

The validate command only checks frontmatter structure, not content quality. Judging whether instructions are useful, accurate, or safe requires human or agent review of the actual skill body.

What are the limitations of automated skill review?▼

Automated checks cover structure and sanitization flags but cannot assess instructional quality or subtle prompt injection. Content judgment, dependency impact, and curation decisions still require deliberate review with dry-run safeguards.

Related Skills

Explore More Software Engineering Skills→
TeamDay-AITeamDay-AI
2

skills-manager

Discover, import, and normalize skills from registries into a library.

Official
Intermediate
The-Vibe-CompanyThe-Vibe-Company
2.4k

companion

Manage, publish, and install SKILL.md packages through a Companion workspace API.

Official
Advanced
semantica-agisemantica-agi
3.0k

provenance

Trace provenance metadata and audit trails within Semantica graphs.

Official
Intermediate
w7panelw7panel
182

development-review

Run linting, type checking, and code formatting checks for development standards.

Official
Advanced