markdown-url
Route any website you need to visit through markdown.new by prefixing the URL. **WHEN TO USE:** - You would normally open a website link to read content (docs, blog posts, changelogs, GitHub issues, etc.) - You need a cleaner, Markdown-friendly view for copying notes or summarizing
78
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description has a clear structure with an explicit 'WHEN TO USE' section that addresses completeness well. However, it lacks specificity about concrete actions beyond URL prefixing and could benefit from more natural trigger terms users would actually say. The description is functional but could be more distinctive to avoid conflicts with general web-reading skills.
Suggestions
Add more natural trigger terms users might say, such as 'convert webpage to markdown', 'clean up article', 'readable version', or 'strip ads/formatting'
Increase specificity by listing concrete outcomes: 'converts webpages to clean markdown, removes ads and clutter, preserves headings and code blocks'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (website routing through markdown.new) and describes the action (prefixing URLs), but lacks comprehensive concrete actions. 'Read content' and 'cleaner view' are somewhat vague about what specific operations are performed. | 2 / 3 |
Completeness | Clearly answers both what (route websites through markdown.new by prefixing URL) and when (explicit 'WHEN TO USE' section with specific scenarios like reading docs, blog posts, copying notes, summarizing). | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'docs, blog posts, changelogs, GitHub issues' and 'Markdown-friendly', but misses common variations users might say like 'convert to markdown', 'readable version', 'strip formatting', or 'clean up webpage'. | 2 / 3 |
Distinctiveness Conflict Risk | The markdown.new service is specific, but 'reading content' and 'summarizing' could overlap with general web browsing or summarization skills. The trigger scenarios are broad enough to potentially conflict with other content-reading skills. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides clear, actionable guidance for URL rewriting with good workflow structure and explicit fallback handling. The main weaknesses are moderate verbosity in the policy section and some redundant explanations that could be tightened. Overall it's a solid skill that effectively teaches the markdown.new routing pattern.
Suggestions
Consolidate the 'Block/Failure Signals' and 'Fallback Behavior' sections into a single, more concise error-handling block
Remove explanatory phrases like 'do not drop the original scheme' that Claude can infer from the examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some redundancy - the policy section repeats concepts (block signals, fallback behavior) that could be consolidated, and some explanations like 'do not drop the original scheme' are unnecessary for Claude. | 2 / 3 |
Actionability | Provides concrete, executable guidance with specific URL rewrite examples, clear bash command for the CLI helper, and explicit lists of when to use vs skip the proxy. The examples are copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 4-step agent workflow with explicit validation (block/failure signals) and fallback behavior. The numbered steps for both the main workflow and fallback are unambiguous with clear decision points. | 3 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the policy section is lengthy and could potentially be split into a separate reference file. The skill is borderline monolithic at ~80 lines with no external references for detailed policies. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.