[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73BR91DQ3XDX9B48Q9B0YRK":3,"skill-same:01M73BR91DQ3XDX9B48Q9B0YRK":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M73BR91DQ3XDX9B48Q9B0YRK","review-skill-format",null,"Review a SKILL.md file for compliance with the agentskills.io standard. Checks YAML frontmatter fields, required sections, line count limits, procedure step format, and registry synchronization. Use when a new skill needs format validation before merge, an existing skill has been modified and requires re-validation, performing a batch audit of all skills in a domain, or reviewing a contributor's skill submission in a pull request.","roohe\u002Fagentic-super-skills","roohe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99054084?v=4","01M734WCDFP6RZVT5CNM00QR26","01M734WCE4BD0T4NZS5PCV9V5F",10,"MIT","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Freview-skill-format\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: review-skill-format\nlocale: caveman-lite\nsource_locale: en\nsource_commit: 82c77053\ntranslator: \"Julius Brussee homage — caveman\"\ntranslation_date: \"2026-04-26\"\ndescription: >\n  Review a SKILL.md file for compliance with the agentskills.io standard.\n  Checks YAML frontmatter fields, required sections, line count limits,\n  procedure step format, and registry synchronization. Use when a new skill\n  needs format validation before merge, an existing skill has been modified and\n  requires re-validation, performing a batch audit of all skills in a domain,\n  or reviewing a contributor's skill submission in a pull request.\nlicense: MIT\nallowed-tools: Read Grep Glob\nmetadata:\n  author: Philipp Thoss\n  version: \"1.2\"\n  domain: review\n  complexity: intermediate\n  language: multi\n  tags: review, skills, format, validation, agentskills, quality\n---\n\n# Review Skill Format\n\nValidate a SKILL.md file against the agentskills.io open standard. This skill checks YAML frontmatter completeness, required section presence, procedure step format (Expected\u002FOn failure blocks), line count limits, and registry synchronization. Use this before merging any new or modified skill.\n\n## When to Use\n\n- A new skill has been authored and needs format validation before merge\n- An existing skill has been modified and needs re-validation\n- Performing a batch audit of all skills in a domain\n- Verifying a skill created by the `create-skill` meta-skill\n- Reviewing a contributor's skill submission in a pull request\n\n## Inputs\n\n- **Required**: Path to the SKILL.md file (e.g., `skills\u002Fsetup-vault\u002FSKILL.md`)\n- **Optional**: Strictness level (`lenient` or `strict`, default: `strict`)\n- **Optional**: Whether to check registry sync (default: yes)\n\n## Procedure\n\n### Step 1: Verify File Exists and Read Content\n\nConfirm the SKILL.md file exists at the expected path and read its full content.\n\n```bash\n# Verify file exists\ntest -f skills\u002F\u003Cskill-name>\u002FSKILL.md && echo \"EXISTS\" || echo \"MISSING\"\n\n# Count lines\nwc -l \u003C skills\u002F\u003Cskill-name>\u002FSKILL.md\n```\n\n**Got:** File exists and content is readable. Line count is displayed.\n\n**If fail:** If the file does not exist, check the path for typos. Verify the skill directory exists with `ls skills\u002F\u003Cskill-name>\u002F`. If the directory is missing, the skill has not been created yet — use `create-skill` first.\n\n### Step 2: Check YAML Frontmatter Fields\n\nParse the YAML frontmatter block (between `---` delimiters) and verify all required and recommended fields are present.\n\nRequired fields:\n- `name` — matches directory name (kebab-case)\n- `description` — under 1024 characters, starts with a verb\n- `license` — typically `MIT`\n- `allowed-tools` — comma-separated or space-separated tool list\n\nRecommended metadata fields:\n- `metadata.author` — author name\n- `metadata.version` — semantic version string\n- `metadata.domain` — one of the domains listed in `skills\u002F_registry.yml`\n- `metadata.complexity` — one of: `basic`, `intermediate`, `advanced`\n- `metadata.language` — primary language or `multi`\n- `metadata.tags` — comma-separated, 3-6 tags, includes domain name\n\n```bash\n# Check required frontmatter fields exist\nhead -30 skills\u002F\u003Cskill-name>\u002FSKILL.md | grep -q '^name:' && echo \"name: OK\" || echo \"name: MISSING\"\nhead -30 skills\u002F\u003Cskill-name>\u002FSKILL.md | grep -q '^description:' && echo \"description: OK\" || echo \"description: MISSING\"\nhead -30 skills\u002F\u003Cskill-name>\u002FSKILL.md | grep -q '^license:' && echo \"license: OK\" || echo \"license: MISSING\"\nhead -30 skills\u002F\u003Cskill-name>\u002FSKILL.md | grep -q '^allowed-tools:' && echo \"allowed-tools: OK\" || echo \"allowed-tools: MISSING\"\n```\n\n**Got:** All four required fields present. All six metadata fields present. `name` matches directory name. `description` is under 1024 characters.\n\n**If fail:** Report each missing field as BLOCKING. If `name` does not match directory name, report as BLOCKING with the expected value. If `description` exceeds 1024 characters, report as SUGGEST with current length.\n\n### Step 3: Locale-Specific Validation (Translations Only)\n\nIf the frontmatter contains a `locale` field, the file is a translated SKILL.md. Perform these additional checks. If no `locale` field is present, skip this step.\n\n1. **Translation frontmatter fields** — Verify these five fields are present:\n   - `locale` — target locale code (e.g., `de`, `ja`, `zh-CN`, `es`)\n   - `source_locale` — origin locale (typically `en`)\n   - `source_commit` — commit hash of the English source used for translation\n   - `translator` — who or what produced the translation\n   - `translation_date` — ISO 8601 date of translation\n\n2. **Prose language scan** — Sample 3-5 body paragraphs (outside code blocks, frontmatter, and headings). Verify the prose is written in the target locale, not English. Ignore: code blocks, inline code, tool names, field names, file paths, and English terms that have no standard translation in the target language.\n\n3. **Code block identity check** — Compare code blocks in the translated file against the English source at `skills\u002F\u003Cskill-name>\u002FSKILL.md`. Code blocks must be identical (code is never translated). Flag any code block whose content differs from the English source.\n\n```bash\n# Check translation frontmatter fields\nfor field in \"locale:\" \"source_locale:\" \"source_commit:\" \"translator:\" \"translation_date:\"; do\n  grep -q \"^${field}\\|^  ${field}\" i18n\u002F\u003Clocale>\u002Fskills\u002F\u003Cskill-name>\u002FSKILL.md \\\n    && echo \"$field OK\" || echo \"$field MISSING\"\ndone\n```\n\n**Got:** All five translation fields present. Body paragraphs are in the target locale. Code blocks match the English source exactly.\n\n**If fail:** Report missing translation fields as BLOCKING. If body paragraphs are in English despite a non-English `locale`, report as BLOCKING — the file has untranslated prose. If code blocks differ from the English source, report as BLOCKING — code must not be translated or modified.\n\n### Step 4: Check Required Sections\n\nVerify all six required sections are present in the skill body (after frontmatter).\n\nRequired sections:\n1. `## When to Use`\n2. `## Inputs`\n3. `## Procedure` (with `### Step N:` sub-sections)\n4. `## Validation` (may also appear as `## Validation Checklist`)\n5. `## Pitfalls`\n6. `## Related Skills`\n\n```bash\n# Check each required section\nfor section in \"## When to Use\" \"## Inputs\" \"## Procedure\" \"## Pitfalls\" \"## Related Skills\"; do\n  grep -q \"$section\" skills\u002F\u003Cskill-name>\u002FSKILL.md && echo \"$section: OK\" || echo \"$section: MISSING\"\ndone\n\n# Validation section may use either heading\ngrep -qE \"## Validation( Checklist)?\" skills\u002F\u003Cskill-name>\u002FSKILL.md && echo \"Validation: OK\" || echo \"Validation: MISSING\"\n```\n\n**Got:** All six sections present. Procedure section contains at least one `### Step` sub-heading.\n\n**If fail:** Report each missing section as BLOCKING. A skill without all six sections is non-compliant with the agentskills.io standard. Provide the section template from the `create-skill` meta-skill.\n\n### Step 5: Check Procedure Step Format\n\nVerify each procedure step follows the required pattern: numbered step title, context, code block(s), and **Got:**\u002F**If fail:** blocks.\n\nFor each `### Step N:` sub-section, check:\n1. The step has a descriptive title (not just \"Step N\")\n2. At least one code block or concrete instruction exists\n3. An `**Got:**` block is present\n4. An `**If fail:**` block is present\n\n**Got:** Every procedure step has both **Got:** and **If fail:** blocks. Steps contain concrete code or instructions, not vague descriptions.\n\n**If fail:** Report each step missing Expected\u002FOn failure as BLOCKING. If steps contain only vague instructions (\"configure the system appropriately\"), report as SUGGEST with a note to add concrete commands.\n\n### Step 6: Verify Line Count\n\nCheck that the SKILL.md is within the 500-line limit.\n\n```bash\nlines=$(wc -l \u003C skills\u002F\u003Cskill-name>\u002FSKILL.md)\n[ \"$lines\" -le 500 ] && echo \"OK ($lines lines)\" || echo \"OVER LIMIT ($lines lines > 500)\"\n```\n\n**Got:** Line count is 500 or fewer.\n\n**If fail:** If over 500 lines, report as BLOCKING. Recommend using the `refactor-skill-structure` skill to extract code blocks >15 lines to `references\u002FEXAMPLES.md`. Typical reduction: 20-40% by extracting extended examples.\n\n### Step 7: Check Registry Synchronization\n\nVerify the skill is listed in `skills\u002F_registry.yml` under the correct domain with matching metadata.\n\nCheck:\n1. Skill `id` exists under the correct domain section\n2. `path` matches `\u003Cskill-name>\u002FSKILL.md`\n3. `complexity` matches frontmatter\n4. `description` is present (may be abbreviated)\n5. `total_skills` count at the top of the registry matches actual skill count\n\n```bash\n# Check if skill is in registry\ngrep -q \"id: \u003Cskill-name>\" skills\u002F_registry.yml && echo \"Registry: FOUND\" || echo \"Registry: NOT FOUND\"\n\n# Check path\ngrep -A1 \"id: \u003Cskill-name>\" skills\u002F_registry.yml | grep -q \"path: \u003Cskill-name>\u002FSKILL.md\" && echo \"Path: OK\" || echo \"Path: MISMATCH\"\n```\n\n**Got:** Skill is listed in the registry under the correct domain with matching path and metadata. Total count is accurate.\n\n**If fail:** If not found in registry, report as BLOCKING. Provide the registry entry template:\n```yaml\n- id: skill-name\n  path: skill-name\u002FSKILL.md\n  complexity: intermediate\n  language: multi\n  description: One-line description\n```\n\n## Validation\n\n- [ ] SKILL.md file exists at the expected path\n- [ ] YAML frontmatter parses without errors\n- [ ] All four required frontmatter fields present (`name`, `description`, `license`, `allowed-tools`)\n- [ ] All six metadata fields present (`author`, `version`, `domain`, `complexity`, `language`, `tags`)\n- [ ] `name` field matches directory name\n- [ ] `description` is under 1024 characters\n- [ ] All six required sections present (When to Use, Inputs, Procedure, Validation, Common Pitfalls, Related Skills)\n- [ ] Every procedure step has **Got:** and **If fail:** blocks\n- [ ] Line count is 500 or fewer\n- [ ] Skill is listed in `_registry.yml` with correct domain, path, and metadata\n- [ ] `total_skills` count in registry is accurate\n- [ ] (Translations only) All five translation frontmatter fields present (`locale`, `source_locale`, `source_commit`, `translator`, `translation_date`)\n- [ ] (Translations only) Body paragraphs are in the target locale, not English\n- [ ] (Translations only) Code blocks are identical to the English source\n\n## Pitfalls\n\n- **Checking frontmatter with regex only**: YAML parsing can be subtle. A `description: >` multiline block looks different from `description: \"inline\"`. Check both patterns when searching for fields.\n- **Missing the Validation section variant**: Some skills use `## Validation Checklist` instead of `## Validation`. Both are acceptable; check for either heading.\n- **Forgetting registry total count**: After adding a skill to the registry, the `total_skills` number at the top must also be incremented. This is a common miss in PRs.\n- **Name vs. title confusion**: The `name` field must be kebab-case matching the directory name. The `# Title` heading is human-readable and can differ (e.g., name: `review-skill-format`, title: `# Review Skill Format`).\n- **Lenient mode skipping blockers**: Even in lenient mode, missing required sections and frontmatter fields should still be flagged. Lenient mode only relaxes style and metadata recommendations.\n- **Translated skills with English prose**: A file with non-English frontmatter, non-English headings, and English body paragraphs passes all structural checks. Always verify body text language for translated skills — the `locale` field in frontmatter signals that prose must be in the target language, not English.\n\n## Related Skills\n\n- `create-skill` — The canonical format specification; use as the authoritative reference for what a valid SKILL.md looks like\n- `update-skill-content` — After format validation passes, use this to improve content quality\n- `refactor-skill-structure` — When a skill fails the line count check, use this to extract and reorganize\n- `review-pull-request` — When reviewing a PR that adds or modifies skills, combine PR review with format validation\n","# Review Skill Format\n\nValidate a SKILL.md file against the agentskills.io open standard. This skill checks YAML frontmatter completeness, required section presence, procedure step format (Expected\u002FOn failure blocks), line count limits, and registry synchronization. Use this before merging any new or modified skill.\n\n## When to Use\n\n- A new skill has been authored and needs format validation before merge\n- An existing skill has been modified and needs re-validation\n- Performing a batch audit of all skills in a domain\n- Verifying a skill created by the `create-skill` meta-skill\n- Reviewing a contributor's skill submission in a pull request\n\n## Inputs\n\n- **Required**: Path to the SKILL.md file (e.g., `skills\u002Fsetup-vault\u002FSKILL.md`)\n- **Optional**: Strictness level (`lenient` or `strict`, default: `strict`)\n- **Optional**: Whether to check registry sync (default: yes)\n\n## Procedure\n\n### Step 1: Verify File Exists and Read Content\n\nConfirm the SKILL.md file exists at the expected path and read its full content.\n\n```bash\n# Verify file exists\ntest -f skills\u002F\u003Cskill-name>\u002FSKILL.md && echo \"EXISTS\" || echo \"MISSING\"\n\n# Count lines\nwc -l \u003C skills\u002F\u003Cskill-name>\u002FSKILL.md\n```\n\n**Got:** File exists and content is readable. Line count is displayed.\n\n**If fail:** If the file does not exist, check the path for typos. Verify the skill directory exists with `ls skills\u002F\u003Cskill-name>\u002F`. If the directory is missing, the skill has not been created yet — use `create-skill` first.\n\n### Step 2: Check YAML Frontmatter Fields\n\nParse the YAML frontmatter block (between `---` delimiters) and verify all required and recommended fields are present.\n\nRequired fields:\n- `name` — matches directory name (kebab-case)\n- `description` — under 1024 characters, starts with a verb\n- `license` — typically `MIT`\n- `allowed-tools` — comma-separated or space-separated tool list\n\nRecommended metadata fields:\n- `metadata.author` — author name\n- `metadata.version` — semantic version string\n- `metadata.domain` — one of the domains listed in `skills\u002F_registry.yml`\n- `metadata.complexity` — one of: `basic`, `intermediate`, `advanced`\n- `metadata.language` — primary language or `multi`\n- `metadata.tags` — comma-separated, 3-6 tags, includes domain name\n\n```bash\n# Check required frontmatter fields exist\nhead -30 skills\u002F\u003Cskill-name>\u002FSKILL.md | grep -q '^name:' && echo \"name: OK\" || echo \"name: MISSING\"\nhead -30 skills\u002F\u003Cskill-name>\u002FSKILL.md | grep -q '^description:' && echo \"description: OK\" || echo \"description: MISSING\"\nhead -30 skills\u002F\u003Cskill-name>\u002FSKILL.md | grep -q '^license:' && echo \"license: OK\" || echo \"license: MISSING\"\nhead -30 skills\u002F\u003Cskill-name>\u002FSKILL.md | grep -q '^allowed-tools:' && echo \"allowed-tools: OK\" || echo \"allowed-tools: MISSING\"\n```\n\n**Got:** All four required fields present. All six metadata fields present. `name` matches directory name. `description` is under 1024 characters.\n\n**If fail:** Report each missing field as BLOCKING. If `name` does not match directory name, report as BLOCKING with the expected value. If `description` exceeds 1024 characters, report as SUGGEST with current length.\n\n### Step 3: Locale-Specific Validation (Translations Only)\n\nIf the frontmatter contains a `locale` field, the file is a translated SKILL.md. Perform these additional checks. If no `locale` field is present, skip this step.\n\n1. **Translation frontmatter fields** — Verify these five fields are present:\n   - `locale` — target locale code (e.g., `de`, `ja`, `zh-CN`, `es`)\n   - `source_locale` — origin locale (typically `en`)\n   - `source_commit` — commit hash of the English source used for translation\n   - `translator` — who or what produced the translation\n   - `translation_date` — ISO 8601 date of translation\n\n2. **Prose language scan** — Sample 3-5 body paragraphs (outside code blocks, frontmatter, and headings). Verify the prose is written in the target locale, not English. Ignore: code blocks, inline code, tool names, field names, file paths, and English terms that have no standard translation in the target language.\n\n3. **Code block identity check** — Compare code blocks in the translated file against the English source at `skills\u002F\u003Cskill-name>\u002FSKILL.md`. Code blocks must be identical (code is never translated). Flag any code block whose content differs from the English source.\n\n```bash\n# Check translation frontmatter fields\nfor field in \"locale:\" \"source_locale:\" \"source_commit:\" \"translator:\" \"translation_date:\"; do\n  grep -q \"^${field}\\|^  ${field}\" i18n\u002F\u003Clocale>\u002Fskills\u002F\u003Cskill-name>\u002FSKILL.md \\\n    && echo \"$field OK\" || echo \"$field MISSING\"\ndone\n```\n\n**Got:** All five translation fields present. Body paragraphs are in the target locale. Code blocks match the English source exactly.\n\n**If fail:** Report missing translation fields as BLOCKING. If body paragraphs are in English despite a non-English `locale`, report as BLOCKING — the file has untranslated prose. If code blocks differ from the English source, report as BLOCKING — code must not be translated or modified.\n\n### Step 4: Check Required Sections\n\nVerify all six required sections are present in the skill body (after frontmatter).\n\nRequired sections:\n1. `## When to Use`\n2. `## Inputs`\n3. `## Procedure` (with `### Step N:` sub-sections)\n4. `## Validation` (may also appear as `## Validation Checklist`)\n5. `## Pitfalls`\n6. `## Related Skills`\n\n```bash\n# Check each required section\nfor section in \"## When to Use\" \"## Inputs\" \"## Procedure\" \"## Pitfalls\" \"## Related Skills\"; do\n  grep -q \"$section\" skills\u002F\u003Cskill-name>\u002FSKILL.md && echo \"$section: OK\" || echo \"$section: MISSING\"\ndone\n\n# Validation section may use either heading\ngrep -qE \"## Validation( Checklist)?\" skills\u002F\u003Cskill-name>\u002FSKILL.md && echo \"Validation: OK\" || echo \"Validation: MISSING\"\n```\n\n**Got:** All six sections present. Procedure section contains at least one `### Step` sub-heading.\n\n**If fail:** Report each missing section as BLOCKING. A skill without all six sections is non-compliant with the agentskills.io standard. Provide the section template from the `create-skill` meta-skill.\n\n### Step 5: Check Procedure Step Format\n\nVerify each procedure step follows the required pattern: numbered step title, context, code block(s), and **Got:**\u002F**If fail:** blocks.\n\nFor each `### Step N:` sub-section, check:\n1. The step has a descriptive title (not just \"Step N\")\n2. At least one code block or concrete instruction exists\n3. An `**Got:**` block is present\n4. An `**If fail:**` block is present\n\n**Got:** Every procedure step has both **Got:** and **If fail:** blocks. Steps contain concrete code or instructions, not vague descriptions.\n\n**If fail:** Report each step missing Expected\u002FOn failure as BLOCKING. If steps contain only vague instructions (\"configure the system appropriately\"), report as SUGGEST with a note to add concrete commands.\n\n### Step 6: Verify Line Count\n\nCheck that the SKILL.md is within the 500-line limit.\n\n```bash\nlines=$(wc -l \u003C skills\u002F\u003Cskill-name>\u002FSKILL.md)\n[ \"$lines\" -le 500 ] && echo \"OK ($lines lines)\" || echo \"OVER LIMIT ($lines lines > 500)\"\n```\n\n**Got:** Line count is 500 or fewer.\n\n**If fail:** If over 500 lines, report as BLOCKING. Recommend using the `refactor-skill-structure` skill to extract code blocks >15 lines to `references\u002FEXAMPLES.md`. Typical reduction: 20-40% by extracting extended examples.\n\n### Step 7: Check Registry Synchronization\n\nVerify the skill is listed in `skills\u002F_registry.yml` under the correct domain with matching metadata.\n\nCheck:\n1. Skill `id` exists under the correct domain section\n2. `path` matches `\u003Cskill-name>\u002FSKILL.md`\n3. `complexity` matches frontmatter\n4. `description` is present (may be abbreviated)\n5. `total_skills` count at the top of the registry matches actual skill count\n\n```bash\n# Check if skill is in registry\ngrep -q \"id: \u003Cskill-name>\" skills\u002F_registry.yml && echo \"Registry: FOUND\" || echo \"Registry: NOT FOUND\"\n\n# Check path\ngrep -A1 \"id: \u003Cskill-name>\" skills\u002F_registry.yml | grep -q \"path: \u003Cskill-name>\u002FSKILL.md\" && echo \"Path: OK\" || echo \"Path: MISMATCH\"\n```\n\n**Got:** Skill is listed in the registry under the correct domain with matching path and metadata. Total count is accurate.\n\n**If fail:** If not found in registry, report as BLOCKING. Provide the registry entry template:\n```yaml\n- id: skill-name\n  path: skill-name\u002FSKILL.md\n  complexity: intermediate\n  language: multi\n  description: One-line description\n```\n\n## Validation\n\n- [ ] SKILL.md file exists at the expected path\n- [ ] YAML frontmatter parses without errors\n- [ ] All four required frontmatter fields present (`name`, `description`, `license`, `allowed-tools`)\n- [ ] All six metadata fields present (`author`, `version`, `domain`, `complexity`, `language`, `tags`)\n- [ ] `name` field matches directory name\n- [ ] `description` is under 1024 characters\n- [ ] All six required sections present (When to Use, Inputs, Procedure, Validation, Common Pitfalls, Related Skills)\n- [ ] Every procedure step has **Got:** and **If fail:** blocks\n- [ ] Line count is 500 or fewer\n- [ ] Skill is listed in `_registry.yml` with correct domain, path, and metadata\n- [ ] `total_skills` count in registry is accurate\n- [ ] (Translations only) All five translation frontmatter fields present (`locale`, `source_locale`, `source_commit`, `translator`, `translation_date`)\n- [ ] (Translations only) Body paragraphs are in the target locale, not English\n- [ ] (Translations only) Code blocks are identical to the English source\n\n## Pitfalls\n\n- **Checking frontmatter with regex only**: YAML parsing can be subtle. A `description: >` multiline block looks different from `description: \"inline\"`. Check both patterns when searching for fields.\n- **Missing the Validation section variant**: Some skills use `## Validation Checklist` instead of `## Validation`. Both are acceptable; check for either heading.\n- **Forgetting registry total count**: After adding a skill to the registry, the `total_skills` number at the top must also be incremented. This is a common miss in PRs.\n- **Name vs. title confusion**: The `name` field must be kebab-case matching the directory name. The `# Title` heading is human-readable and can differ (e.g., name: `review-skill-format`, title: `# Review Skill Format`).\n- **Lenient mode skipping blockers**: Even in lenient mode, missing required sections and frontmatter fields should still be flagged. Lenient mode only relaxes style and metadata recommendations.\n- **Translated skills with English prose**: A file with non-English frontmatter, non-English headings, and English body paragraphs passes all structural checks. Always verify body text language for translated skills — the `locale` field in frontmatter signals that prose must be in the target language, not English.\n\n## Related Skills\n\n- `create-skill` — The canonical format specification; use as the authoritative reference for what a valid SKILL.md looks like\n- `update-skill-content` — After format validation passes, use this to improve content quality\n- `refactor-skill-structure` — When a skill fails the line count check, use this to extract and reorganize\n- `review-pull-request` — When reviewing a PR that adds or modifies skills, combine PR review with format validation\n",{"name":5,"locale":23,"license":14,"metadata":24,"translator":31,"description":32,"allowed-tools":33,"source_commit":34,"source_locale":35,"translation_date":36},"caveman-lite",{"tags":25,"author":26,"domain":27,"version":28,"language":29,"complexity":30},"review, skills, format, validation, agentskills, quality","Philipp Thoss","review","1.2","multi","intermediate","Julius Brussee homage — caveman","Review a SKILL.md file for compliance with the agentskills.io standard. Checks YAML frontmatter fields, required sections, line count limits, procedure step format, and registry synchronization. Use when a new skill needs format validation before merge, an existing skill has been modified and requires re-validation, performing a batch audit of all skills in a domain, or reviewing a contributor's skill submission in a pull request.\n","Read Grep Glob","82c77053","en","2026-04-26","master","f483e54f3ad5f202a77d45f2e57f8d970b71195f","skills_library\u002Freview-skill-format",2,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills","https:\u002F\u002Fgithub.com\u002Froohe","yoou.link","2026-05-19 15:56:07",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add roohe\u002Fagentic-super-skills --skill review-skill-format",{"tool":51,"command":52},"bunx","bunx skills add roohe\u002Fagentic-super-skills --skill review-skill-format",{"tool":54,"command":55},"pnpm","pnpm dlx skills add roohe\u002Fagentic-super-skills --skill review-skill-format","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Freview-skill-format\u002FSKILL.md",true,[],[60,67,74,81,88,95],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M73D865CZME2FCMKA4PQM348","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M73D7Z64J4ABWZJD7P44XBBF","youtube-downloader","Download and process YouTube content for research. Use when: downloading competitor videos for analysis; extracting audio for podcasts; getting transcripts for content repurposing; archiving webinars; research content curation","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyoutube-downloader\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M73D7K8778TGZV3GJFR3703D","yc-pitch-deck","Create a compelling startup pitch deck that follows the structure proven to raise billions from top investors. Master the YC and Sequoia formats that get founders funded. Use when: **Fundraising** to create investor pitch decks; **YC application** to structure your narrative; **Demo Day prep** to craft your 2-minute pitch; **Angel investors** to communicate your opportunity; **Partnership pitches** to structure compelling asks","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyc-pitch-deck\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M73D70KJSE0E8Z28YMNNRT04","x-twitter-scraper","Use when the user needs X (Twitter) data or confirmation-gated X actions through Xquik: tweet search, user lookup, follower extraction, media download, monitoring, webhooks, MCP, SDKs, posting, likes, DMs, and profile updates. Requires a Xquik API key. Never ask for X login material.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fx-twitter-scraper\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M73D6ED01GV077R7K4NZNFZJ","write-vignette","Create R package vignettes using R Markdown or Quarto. Covers vignette setup, YAML configuration, code chunk options, building and testing, and CRAN requirements for vignettes. Use when adding a Getting Started tutorial, documenting complex workflows spanning multiple functions, creating domain-specific guides, or when CRAN submission requires user-facing documentation beyond function help pages.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-vignette\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M73D69YJR0BK3NFHE0CYG3EF","write-validation-documentation","Write IQ\u002FOQ\u002FPQ validation documentation for computerized systems in regulated environments. Covers protocols, reports, test scripts, deviation handling, and approval workflows. Use when validating R or other software for regulated use, preparing for a regulatory audit, documenting qualification of computing environments, or creating and updating validation protocols and reports for new or re-qualified systems.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-validation-documentation\u002FSKILL.md",[],[]]