0codekit
0codekit integration. Manage Workspaces. Use when the user wants to interact with 0codekit data.
45
33%
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/0codekit/SKILL.mdQuality
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.
The description is minimal and vague, relying heavily on the product name '0codekit' for distinctiveness. It fails to enumerate specific capabilities beyond the generic 'Manage Workspaces' and the 'Use when' clause is too broad to provide meaningful selection guidance. The description would benefit significantly from listing concrete actions and more specific trigger terms.
Suggestions
List specific concrete actions the skill performs, e.g., 'Create, list, update, and delete workspaces in 0codekit. Manage workspace configurations and members.'
Expand the 'Use when...' clause with specific trigger terms users would naturally say, e.g., 'Use when the user mentions 0codekit, workspace management, creating or configuring workspaces, or references 0codekit projects.'
Add context about what '0codekit data' encompasses to reduce vagueness and improve distinctiveness from other integration skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Manage Workspaces' which is a single vague action. It doesn't list concrete actions like creating, deleting, listing, or configuring workspaces. '0codekit integration' and 'interact with 0codekit data' are abstract and non-descriptive. | 1 / 3 |
Completeness | It has a weak 'what' ('Manage Workspaces') and does include a 'Use when...' clause ('when the user wants to interact with 0codekit data'), but the 'when' is extremely vague and essentially restates the 'what' without adding meaningful trigger guidance. | 2 / 3 |
Trigger Term Quality | It includes '0codekit' and 'Workspaces' as keywords, which are relevant if a user mentions those terms. However, it lacks common variations or natural phrases a user might say (e.g., 'create workspace', 'list projects', specific operations). | 2 / 3 |
Distinctiveness Conflict Risk | '0codekit' is a specific product name which helps distinguish it, but 'Manage Workspaces' and 'interact with data' are generic enough to potentially overlap with other workspace or project 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.
The skill is severely bloated by an enormous inline list of 300+ integrations that provides no actionable guidance and wastes massive token budget. The Membrane CLI workflow sections are reasonably useful with concrete commands, but the skill lacks end-to-end examples and opens with a confusing 'I don't have enough information' statement. The content would be dramatically improved by removing the integrations list and adding a complete worked example.
Suggestions
Remove or move the massive '0codekit Overview' integrations list to a separate reference file — it consumes the vast majority of tokens while providing no actionable value.
Add a complete end-to-end example showing a real task (e.g., converting CSV to JSON) from connection setup through action execution with actual input/output.
Remove the 'I don't have enough information to do that. Can you tell me more about the app?' line — it's confusing and serves no purpose in a skill file.
Add descriptions to the popular actions table or remove entries that have 'No description' — currently the table adds little value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The massive '0codekit Overview' section is an enormous, repetitive list of hundreds of integrations (spreadsheets, calendars, mailboxes, chat apps, databases, file types, etc.) that provides no actionable value. This wastes an extreme number of tokens — the list alone is likely 80%+ of the content. Claude doesn't need to see 'Ecosia Calendar → Events → Columns' or 'Kloxo File' to use the tool. | 1 / 3 |
Actionability | The Membrane CLI commands are concrete and copy-paste ready (install, login, connection ensure, action list, action run with --input). However, the skill opens with 'I don't have enough information to do that' which is confusing, the popular actions table lacks descriptions, and there are no complete end-to-end examples showing input/output for a real task. | 2 / 3 |
Workflow Clarity | The workflow for connecting, searching actions, creating actions, and running them is present with state-handling guidance (BUILDING, READY, CLIENT_ACTION_REQUIRED). However, there's no single cohesive end-to-end workflow tying these steps together, and validation/error recovery is mentioned but not structured as explicit checkpoints in a numbered sequence. | 2 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with the massive integrations list inline rather than in a separate reference file. The overview list should be removed or linked externally. There are no references to separate files for advanced usage, API details, or the full integrations catalog. | 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 (1442 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 | |
- Repository
- membranedev/application-skills
- Commit
88db8c5
- 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.