2markdown
2markdown integration. Manage data, records, and automate workflows. Use when the user wants to interact with 2markdown data.
48
51%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/2markdown/SKILL.mdQuality
Discovery
25%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 is weak across all dimensions. It relies on the product name '2markdown' without explaining what the tool actually does, uses entirely generic action terms, and has a circular trigger clause that provides no real guidance for skill selection. It would be nearly impossible for Claude to correctly choose this skill over others based on this description alone.
Suggestions
Replace vague terms like 'manage data' and 'automate workflows' with specific concrete actions that 2markdown performs (e.g., 'Convert web pages and HTML content to clean Markdown format').
Add natural trigger terms users would actually say, such as 'convert HTML to markdown', 'web page to markdown', 'scrape website content', or whatever 2markdown's actual capabilities are.
Rewrite the 'Use when...' clause with specific, non-circular triggers (e.g., 'Use when the user wants to convert web content to Markdown, extract article text, or work with the 2markdown API').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without specifying any concrete actions. It doesn't explain what 2markdown actually does (e.g., convert web pages to markdown, scrape content). The actions listed are generic and could apply to almost any integration. | 1 / 3 |
Completeness | It has a weak 'what' (manage data, records, automate workflows) and includes a 'Use when...' clause, but the trigger condition ('interact with 2markdown data') is circular and uninformative—it essentially says 'use this when you need to use this.' The 'when' doesn't provide meaningful guidance for skill selection. | 2 / 3 |
Trigger Term Quality | The only specific keyword is '2markdown', which is the product name. Terms like 'data', 'records', and 'workflows' are overly generic and would not naturally be used by someone specifically needing 2markdown functionality. No natural trigger terms like 'convert to markdown', 'web scraping', or 'HTML to markdown' are included. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of '2markdown' as a specific product name provides some distinctiveness, but the generic terms 'manage data, records, and automate workflows' could easily overlap with dozens of other integration skills. Without specific capabilities described, it's hard to distinguish from other data management tools. | 2 / 3 |
Total | 6 / 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 integration skill with excellent actionability — every step has concrete CLI commands and clear state-handling logic. The main weaknesses are some unnecessary introductory explanation (what 2markdown is, who uses it) and a monolithic structure that could benefit from splitting detailed reference material into separate files. The workflow for connection management is particularly well done with explicit state checks and error handling.
Suggestions
Remove the introductory paragraph explaining what 2markdown is and who uses it — Claude doesn't need this context to perform the integration.
Consider splitting the proxy request flag table and detailed connection state handling into a separate reference file, keeping SKILL.md as a concise overview with links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what 2markdown is and who uses it — information Claude doesn't need. The Membrane CLI setup and authentication flow is somewhat verbose but mostly necessary. Some sections like 'Best practices' repeat what's already implied by the instructions. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste-ready CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. The flag reference table for proxy requests is specific and useful. | 3 / 3 |
Workflow Clarity | The multi-step connection flow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, error states) and instructions for what to do at each state. The polling/retry loop for connection readiness is a well-defined feedback loop. | 3 / 3 |
Progressive Disclosure | The content is a single monolithic file with no references to supporting documents. While the structure uses headers and subsections reasonably well, the connection setup details, proxy request documentation, and best practices could benefit from being split out or the overview section being more concise with references to detailed docs. | 2 / 3 |
Total | 10 / 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 | |
- Repository
- membranedev/application-skills
- Commit
f484c82
- 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.