0codekit
0codekit integration. Manage Workspaces. Use when the user wants to interact with 0codekit data.
36
33%
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/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.
This description is minimal and lacks specificity about what concrete actions the skill performs with 0codekit workspaces. While it benefits from referencing a specific product name ('0codekit') and includes a 'Use when' clause, both the capabilities and trigger conditions are too vague to effectively guide skill selection among many options.
Suggestions
List specific concrete actions the skill can perform, e.g., 'Create, list, update, and delete workspaces in 0codekit. Query workspace configurations and manage workspace members.'
Expand the 'Use when' clause with natural trigger terms users would say, e.g., 'Use when the user mentions 0codekit, workspace management, workspace creation, or needs to configure 0codekit projects.'
Add more detail about what '0codekit data' encompasses to help distinguish this skill from other integration or workspace management 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 includes a 'Use when...' clause, but the trigger is vague ('interact with 0codekit data') and doesn't provide meaningful guidance on when to select this skill. The 'Use when' clause exists but is too generic to be truly useful. | 2 / 3 |
Trigger Term Quality | It includes '0codekit' and 'Workspaces' as keywords, which are relevant if a user mentions those terms. However, it lacks natural variations or specific task-related terms users might say (e.g., 'create workspace', 'list projects', 'manage repos'). | 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 contains useful, actionable Membrane CLI instructions for connecting to 0codekit and running actions, but these are buried under an enormous, token-wasteful enumeration of hundreds of integrations that provides no actionable guidance. The opening statement 'I don't have enough information to do that' is counterproductive. The actionable sections (authentication, connection, action search/run, proxy) are decent but would benefit from better organization and the removal or externalization of the massive overview list.
Suggestions
Remove or move the massive 500+ line integration overview list to a separate reference file — it consumes enormous token budget without providing actionable guidance.
Remove the opening line 'I don't have enough information to do that. Can you tell me more about the app?' as it's confusing and anti-actionable in a skill file.
Add descriptions to the popular actions table entries instead of 'No description' — these should explain what each action does and what inputs are expected.
Structure the content as a clear end-to-end numbered workflow: 1) Install CLI → 2) Authenticate → 3) Connect → 4) Discover actions → 5) Run actions, with explicit validation/error handling at each step.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The massive 'Overview' section listing hundreds of integrations (spreadsheets, calendars, mailboxes, chat apps, databases, file types, programming languages, etc.) is extremely verbose and provides no actionable value. This consumes enormous token budget with a simple enumeration that Claude doesn't need and that provides no guidance on how to interact with any of these services. | 1 / 3 |
Actionability | The Membrane CLI commands for authentication, connection, action search, action execution, and proxy requests are concrete and copy-paste ready. However, the skill opens with 'I don't have enough information to do that' which is anti-actionable, and the massive overview list provides zero executable guidance. The popular actions table lacks descriptions, reducing actionability. | 2 / 3 |
Workflow Clarity | The connection workflow (ensure → check state → handle CLIENT_ACTION_REQUIRED → poll until READY) is reasonably well-sequenced with state-based branching. However, there's no explicit validation checkpoint after running actions, no error recovery guidance for failed action runs, and the overall flow from authentication through to action execution could be more clearly delineated as a numbered end-to-end workflow. | 2 / 3 |
Progressive Disclosure | The skill is a monolithic wall of text with the enormous overview list inline rather than in a separate reference file. There are no references to supporting files for the integration catalog, API details, or advanced usage. The content that should be split out (the 500+ line integration list) dominates the file and buries the actionable content. | 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 (1445 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
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.