agent-skill-reviewer
Agent Skill Reviewer
Instructions
When the user asks you to review an Agent Skill, follow these steps to ensure the skill complies with the best practices.
1. Identify the Target
Determine the directory path of the Agent Skill to be reviewed. Read the directory structure and the content of the SKILL.md file.
2. Analyze Directory Structure
Check if the project follows the production-grade directory structure:
- Directory Name: Must use
kebab-case. - Core File: Ensure the core instruction file is named exactly
SKILL.md(uppercase). - Separation of Concerns: Look for proper subdirectories (e.g.,
scripts/for executable code,references/for docs,assets/for static files).
3. Review Naming Conventions
- Role-based Naming: Check if the skill name uses a Noun/Doer format instead of a Verb/Action format (e.g.,
agent-skill-reviewerinstead ofagent-skill-review).
4. Review Frontmatter (Metadata Layer)
- Read the YAML frontmatter of
SKILL.md. - Name: Verify that the
namefield is present and matches the directory name. - Description Formula: Verify that the
descriptionfollows the golden formula:[Function] + [Trigger Scenario] + [Keywords]. It must be specific enough for the LLM to reason about when to trigger the skill.
5. Review Instructions (Core Logic Layer)
- Clarity: Check if the instructions are clear, step-by-step, and easy for an LLM to follow.
- State & Concurrency: Ensure the skill does not attempt to handle highly concurrent parallel tasks within a single conversation thread, as skills modify the context state.
- Offloading: Ensure no complex logic is hardcoded in Markdown if it can be offloaded to an external tool or script (e.g., in
scripts/). - Progressive Disclosure: Verify that detailed supplementary knowledge is placed in
references/rather than cluttering the mainSKILL.md.
6. Report Findings
Present a structured review report to the user using the following format:
- Directory Structure & Naming: Pass/Fail with details.
- Frontmatter: Pass/Fail with details.
- Instructions: Pass/Fail with details.
- Recommendations: Provide actionable recommendations for any violations of best practices.
More from forceinjection/awesome-skills
doc-reviewer
审查技术文档。支持四种独立评审类型:大纲评审(检查目录与结构逻辑)、内容评审(检查文字准确性与代码质量)、资产评审(校验链接与引用合规)、格式评审(校对纯视觉排版与标点)。当用户请求审查或修正 Markdown 文档时使用。
5project-analyzer
Generate a comprehensive project documentation (whitepaper) based on deep codebase analysis, covering architecture, modules, testing, and deployment.
4dir-organizer
整理和优化项目目录结构。当用户请求整理目录、分类文件、清理无用文件或重构文件夹结构时调用此技能。
4code-reader
Use when you want to deeply understand an unfamiliar codebase and generate reusable cognitive skills from it, by providing a local path or GitHub URL
4md-summarizer
分析和总结指定的本地 Markdown 文件,并输出结构化的中文总结。当用户请求总结、分析或提取本地 Markdown 文档信息时调用此技能。
4update-submitter
Analyzes git status, groups related file changes, and generates standardized Conventional Commits. Invoke when the user wants to commit changes, submit updates, or create a PR.
3