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
72%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/markdown-url/SKILL.mdQuality
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.
The description is reasonably well-structured with a clear 'WHEN TO USE' section that explicitly addresses both what the skill does and when to use it. Its main weaknesses are that the core capability is somewhat narrowly described (essentially just URL prefixing for markdown conversion), and the trigger terms could be broader to capture more natural user phrasings. The skill could also be more distinctive by clarifying how it differs from general web browsing or content fetching skills.
Suggestions
Add more natural trigger terms users might say, such as 'fetch URL', 'read webpage', 'web content', 'browse site', or 'convert page to markdown'.
Clarify distinctiveness by explicitly stating when NOT to use this skill (e.g., 'Do not use for API calls or programmatic web scraping') to reduce conflict with similar web-access skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a specific mechanism ('route through markdown.new by prefixing the URL') and mentions some use cases (docs, blog posts, changelogs, GitHub issues), but the core action is somewhat narrow and not fully elaborated with multiple concrete actions beyond 'visit' and 'get a cleaner view'. | 2 / 3 |
Completeness | The description clearly answers both 'what' (route URLs through markdown.new for cleaner Markdown views) and 'when' (explicit 'WHEN TO USE' section with two clear trigger conditions: opening website links to read content, and needing a cleaner Markdown-friendly view). | 3 / 3 |
Trigger Term Quality | Includes some natural terms like 'website link', 'docs', 'blog posts', 'changelogs', 'GitHub issues', 'Markdown-friendly view', 'summarizing'. However, it misses common trigger terms users might say like 'fetch URL', 'read webpage', 'scrape', 'browse', or 'web content', and 'markdown.new' itself is a niche tool name that users may not mention. | 2 / 3 |
Distinctiveness Conflict Risk | The markdown.new routing mechanism is fairly distinctive, but the broader framing of 'visit a website to read content' could overlap with general web browsing, URL fetching, or web scraping skills. The description could conflict with any skill that involves reading web content. | 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 is a solid, actionable skill with clear workflow steps, concrete URL rewrite examples, and well-defined fallback behavior. Its main weakness is moderate verbosity—some sections are repetitive (policy, notes/exceptions, and fallback overlap), and the content could be tightened by ~20-30% without losing clarity. The workflow clarity is excellent with explicit failure detection and recovery paths.
Suggestions
Consolidate the 'Notes / Exceptions' section into the 'Policy: When To Use' section to eliminate redundancy about when not to use markdown.new.
Tighten the block/failure signals into a compact bullet list without the subsection header, since it's only 4 items and could be folded into the fallback behavior section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some redundancy—the policy section, fallback behavior, and notes/exceptions overlap in explaining when not to use markdown.new. The block/failure signals section is useful but could be more compact. Some phrasing like 'the rendered Markdown and/or the raw Markdown' is unnecessarily hedging. | 2 / 3 |
Actionability | The rewrite rule is concrete with clear examples showing input→output transformations. The workflow steps are specific and executable, the policy section gives concrete categories of when to use vs skip, and block/failure signals are explicitly enumerated. The CLI helper provides a copy-paste ready command. | 3 / 3 |
Workflow Clarity | The agent workflow is clearly sequenced (rewrite → visit → extract → use), with explicit fallback behavior on failure. Block/failure signals serve as validation checkpoints, and the fallback sequence (attempt once → switch to original → note the failure) provides a clear error recovery loop. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers, but everything is in a single file that runs fairly long. The policy section, block/failure signals, and fallback behavior could potentially be condensed or the detailed policy could be split into a reference file. However, for a skill of this complexity, keeping it in one file is borderline acceptable. | 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.
- Repository
- am-will/codex-skills
- Commit
633b7e0
- 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.