2markdown
2markdown integration. Manage data, records, and automate workflows. Use when the user wants to interact with 2markdown data.
55
44%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
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 a generic template-style integration description that fails to communicate what 2markdown actually does or when it should be selected. The 'Use when' clause is circular, and the listed capabilities (manage data, records, automate workflows) are so generic they could describe virtually any integration tool. Without concrete actions or meaningful trigger terms, Claude would struggle to correctly select this skill.
Suggestions
Replace generic actions with specific 2markdown capabilities (e.g., 'Converts web pages and HTML content to clean Markdown format, extracts article text, processes URLs') so Claude knows what this tool actually does.
Rewrite the 'Use when' clause with natural trigger terms users would say, such as 'Use when the user wants to convert HTML to markdown, extract web page content, or mentions 2markdown, URL-to-markdown conversion, or web scraping to markdown format.'
Remove the circular reference to '2markdown data' and instead describe the actual data types and workflows involved (e.g., URLs, HTML documents, web content).
| 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 tool name. Terms like 'data', 'records', and 'workflows' are overly generic and would not naturally be used by someone specifically needing 2markdown functionality. No natural user phrases like 'convert to markdown', 'web scraping', or 'HTML to markdown' are included. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of '2markdown' as a specific tool 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/workflow tools. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a functional Membrane CLI integration skill with strong actionability — every operation has a concrete, executable command. The main weaknesses are some unnecessary introductory verbosity, a shallow overview section that adds no value, and missing error-handling/validation guidance in the workflow. The skill is largely a generic Membrane connector template with 2markdown-specific details limited to the connector key.
Suggestions
Remove or condense the introductory paragraph explaining what 2markdown is — Claude already knows this and it wastes tokens.
Remove or flesh out the empty '2markdown Overview' section (File/Conversion, Account/Subscription) — as-is it provides no actionable information.
Add error handling guidance: what to do when `membrane connect` fails, when action runs return errors, or when polling times out repeatedly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what 2markdown is and who uses it — information Claude doesn't need. The Membrane CLI pattern is mostly efficient but includes some unnecessary filler like 'so you can focus on the integration logic rather than auth plumbing.' Could be tightened. | 2 / 3 |
Actionability | Provides concrete, copy-paste-ready CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, polling, and running actions with parameters. Each command is specific and executable. | 3 / 3 |
Workflow Clarity | The steps are listed in a logical sequence (install → authenticate → connect → discover → create → run), and the action creation flow includes polling with state checking. However, there are no explicit validation checkpoints or error recovery feedback loops for the overall workflow — e.g., no guidance on what to do if connection fails or if action run returns an error. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear headings, but it's somewhat monolithic — the '2markdown Overview' section with File/Conversion/Account/Subscription bullets adds no value and could be removed or expanded. No references to external files for advanced topics. For a skill of this length, the organization is adequate but not optimal. | 2 / 3 |
Total | 9 / 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
56d7336
- 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.