0codekit
0codekit integration. Manage Workspaces. Use when the user wants to interact with 0codekit data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill 0codekit45
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
40%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 too vague to effectively guide skill selection. While it mentions the product name and includes a 'Use when' clause, it fails to specify what concrete actions the skill enables or what specific user requests should trigger it. The description would benefit significantly from listing specific capabilities and more natural trigger terms.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Create, list, delete, and configure workspaces in 0codekit').
Expand the 'Use when' clause with natural trigger terms users would say (e.g., 'Use when the user mentions 0codekit, workspace setup, project configuration, or asks to manage their development environment').
Clarify what '0codekit data' means by listing specific data types or operations (e.g., 'projects, configurations, team settings').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Manage Workspaces' and 'interact with 0codekit data' without specifying concrete actions. No specific operations like create, delete, list, or configure are mentioned. | 1 / 3 |
Completeness | Has a basic 'what' (manage workspaces) and includes a 'Use when' clause, but both are extremely vague. The 'when' trigger of 'interact with 0codekit data' is too generic to be useful for skill selection. | 2 / 3 |
Trigger Term Quality | Includes the product name '0codekit' and 'Workspaces' as keywords, but lacks natural variations users might say. Missing terms like 'workspace management', 'project', or specific action verbs users would use. | 2 / 3 |
Distinctiveness Conflict Risk | The product name '0codekit' provides some distinctiveness, but 'Manage Workspaces' and 'interact with data' are generic enough to potentially conflict with other workspace or data management skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has a useful core (Membrane CLI integration for 0codekit) buried under an enormous, unhelpful enumeration of data sources that dominates the content. The CLI instructions are reasonably actionable but lack error handling and validation steps. The opening statement 'I don't have enough information to do that' is confusing and unprofessional for a skill document.
Suggestions
Remove or move the massive '0codekit Overview' data source list to a separate reference file - it provides no actionable guidance and wastes significant tokens
Remove the confusing opening line 'I don't have enough information to do that' - skills should provide clear instructions, not express uncertainty
Add validation steps after key operations (e.g., 'Verify connection succeeded by running membrane connection list')
Add concrete input/output examples for the popular actions showing actual JSON payloads and expected responses
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains an extremely verbose and largely useless list of 400+ data source types with their components (Rows, Columns, etc.) that provides no actionable value. This massive enumeration wastes tokens on information Claude doesn't need and could infer. | 1 / 3 |
Actionability | The Membrane CLI commands are concrete and executable, but the skill opens with 'I don't have enough information to do that' which is confusing. The action examples lack complete input/output demonstrations, and the massive data source list provides no guidance on how to actually use any of them. | 2 / 3 |
Workflow Clarity | The setup flow (install CLI → login → connect → run actions) is reasonably clear, but lacks validation checkpoints. There's no guidance on error handling, verifying successful connections, or what to do when actions fail. | 2 / 3 |
Progressive Disclosure | The skill is a monolithic wall of text with the massive data source enumeration inline rather than in a separate reference file. The overview section should be a brief summary with links to detailed documentation, not 400+ bullet points. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (1415 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 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.