2markdown
2markdown integration. Manage data, records, and automate workflows. Use when the user wants to interact with 2markdown data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill 2markdown55
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
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 fails to explain what 2markdown is or what specific capabilities it offers. The language is generic and circular ('interact with 2markdown data'), providing no meaningful guidance for skill selection. Without knowing what 2markdown does, Claude cannot effectively choose this skill over others.
Suggestions
Explain what 2markdown is and its primary function (e.g., 'Converts web pages and HTML content to clean Markdown format')
Add specific concrete actions the skill enables (e.g., 'convert URLs to markdown, extract article content, clean HTML formatting')
Include natural trigger terms users would say (e.g., 'convert to markdown', 'extract webpage content', 'HTML to markdown', 'scrape article')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Manage data, records, and automate workflows' without specifying concrete actions. It doesn't explain what 2markdown actually does or what specific operations are available. | 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 about actual use cases. | 2 / 3 |
Trigger Term Quality | The only trigger term is '2markdown' which is a product name. Generic terms like 'data', 'records', and 'workflows' are overly broad and wouldn't help distinguish this skill. No natural user language is included. | 1 / 3 |
Distinctiveness Conflict Risk | The '2markdown' product name provides some distinctiveness, but 'manage data, records, and automate workflows' is extremely generic and could overlap with dozens of other integration skills. | 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 skill provides solid, actionable CLI commands for integrating with 2markdown via Membrane, with good examples for common operations. However, it includes unnecessary introductory content about what 2markdown is, lacks validation checkpoints in workflows, and the overview section structure provides no actionable value. The best practices section is useful but the overall document could be more concise.
Suggestions
Remove the introductory paragraph explaining what 2markdown is and who uses it - Claude already knows this context
Either remove the '2markdown Overview' bullet hierarchy or replace it with actionable content explaining what operations are available
Add validation/error handling guidance after key commands (e.g., 'If connection fails, check...' or 'Verify connection with...')
Consider consolidating the 'First-time setup' and 'Connecting to 2markdown' sections into a clearer sequential workflow with numbered steps
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., describing what 2markdown is and who uses it) that Claude already knows. The Membrane CLI setup instructions are reasonable but could be tighter. | 2 / 3 |
Actionability | Provides fully executable CLI commands with clear syntax, including JSON parameter passing, proxy requests with flag documentation, and concrete examples for connection setup and action discovery. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection but lack explicit validation checkpoints. No feedback loops for error recovery when commands fail, and the workflow jumps between setup, connection checking, and action running without clear sequencing. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with sections, but the '2markdown Overview' section with File/Conversion/Account/Subscription hierarchy adds no value and could be removed or linked to external docs. No references to separate detailed files for advanced usage. | 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 | |
- 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.