-Automatically convert documentation websites, GitHub repositories, and PDFs into Claude AI skills in minutes.
42
42%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
57%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a clear and distinctive niche — converting external documentation sources into Claude skills — which makes it stand out among other skills. However, it lacks an explicit 'Use when...' clause and could benefit from more natural trigger terms that users would actually say. The leading hyphen also suggests a formatting issue.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to create a skill from a documentation site, GitHub repo, or PDF, or asks to import/scrape external sources into a skill.'
Include more natural trigger term variations such as 'create skill from docs', 'import repository', 'scrape documentation', 'turn a website into a skill', 'generate skill from PDF'.
Remove the leading hyphen which appears to be a formatting artifact and use third-person voice consistently, e.g., 'Converts documentation websites, GitHub repositories, and PDFs into Claude AI skills.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (converting docs to skills) and lists input sources (documentation websites, GitHub repositories, PDFs), but doesn't detail specific actions beyond 'convert' — e.g., what parsing, formatting, or validation steps are involved. | 2 / 3 |
Completeness | Describes what it does (convert documentation sources into Claude AI skills) but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric guidelines. | 2 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'documentation websites', 'GitHub repositories', 'PDFs', and 'Claude AI skills', but misses common user phrasings like 'create a skill from', 'import docs', 'scrape website', or 'turn repo into skill'. | 2 / 3 |
Distinctiveness Conflict Risk | The specific niche of converting external sources (docs websites, repos, PDFs) into Claude AI skills is quite distinctive and unlikely to conflict with other skills, as it targets a very particular workflow. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially an empty shell with no actionable content. It repeats the one-line description three times in slightly different wrappers and provides only a link to a GitHub repository. There are no instructions, examples, workflows, or useful information of any kind.
Suggestions
Add concrete, step-by-step instructions for how to convert documentation websites, GitHub repos, and PDFs into Claude skills (e.g., specific commands, tool usage, expected inputs/outputs).
Include at least one complete executable example showing the conversion process end-to-end, such as converting a specific documentation site into a SKILL.md file.
Define a clear workflow with validation checkpoints, e.g., 1) Fetch source content, 2) Parse and extract key information, 3) Generate skill structure, 4) Validate output format.
Remove the repeated description text and replace 'When to Use This Skill' boilerplate with actual use-case-specific guidance or remove the section entirely.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is almost entirely filler text that repeats the description verbatim multiple times. It contains no actual substance—just boilerplate wrappers around the same sentence repeated three times with no useful information added. | 1 / 3 |
Actionability | There are no concrete instructions, code examples, commands, or steps. The skill provides zero executable guidance—just a vague statement that it 'provides guidance and patterns' without actually providing any. | 1 / 3 |
Workflow Clarity | There is no workflow described at all. No steps, no sequence, no validation checkpoints—just a link to a source repository with no explanation of what to do. | 1 / 3 |
Progressive Disclosure | While there is a link to a source repository, the SKILL.md itself contains no meaningful overview content to serve as a starting point. There is no structured navigation or signposted references to deeper content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents