abstract
Abstract integration. Manage data, records, and automate workflows. Use when the user wants to interact with Abstract data.
58
67%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/abstract/SKILL.mdQuality
Discovery
57%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 follows the correct structural pattern with a 'Use when' clause, but the actual content is extremely generic. 'Manage data, records, and automate workflows' could describe virtually any integration tool. The description fails to convey what Abstract actually is or what specific operations are supported, making it nearly useless for distinguishing this skill from other integration skills.
Suggestions
Replace generic actions with specific Abstract operations, e.g., 'Manage design branches, collections, and commits in Abstract. Export design assets, review changes, and track version history.'
Add domain-specific trigger terms that users would naturally say, such as 'design versioning', 'Sketch files', 'design branches', 'Abstract collections', or 'design review'.
Clarify what Abstract is (a design version control platform) to help distinguish it from other integrations with similarly generic descriptions.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The actions listed ('manage data, records, and automate workflows') are extremely vague and generic. There are no concrete, specific actions like 'create records', 'sync projects', or 'export design assets'. 'Abstract' as a product name is mentioned but the capabilities described could apply to almost any integration. | 1 / 3 |
Completeness | It does answer both 'what' (manage data, records, automate workflows) and 'when' (when the user wants to interact with Abstract data) with an explicit 'Use when' clause. While the content is vague, the structure is complete. | 3 / 3 |
Trigger Term Quality | It includes 'Abstract' as a keyword which is the product name, and generic terms like 'data', 'records', and 'workflows'. However, it lacks natural terms users would say when needing this skill, such as specific Abstract concepts (e.g., 'design versions', 'branches', 'collections', 'Sketch files') or file types. | 2 / 3 |
Distinctiveness Conflict Risk | 'Abstract' as a product name provides some distinctiveness, but 'manage data, records, and automate workflows' is so generic it could easily overlap with dozens of other integration skills. The description doesn't clarify what makes Abstract unique compared to other data/workflow tools. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid integration skill with excellent actionability and workflow clarity—every step has concrete CLI commands and the connection setup flow handles edge cases well with explicit state machine logic. The main weaknesses are some unnecessary introductory content about Abstract that wastes tokens, and the monolithic structure that could benefit from splitting detailed reference material into separate files.
Suggestions
Remove the introductory paragraph explaining what Abstract is—Claude already knows this. The 'Abstract Overview' entity list is also too vague to be useful; either provide actionable details about each entity or remove it.
Consider extracting the proxy request options table and detailed CLIENT_ACTION_REQUIRED handling into a separate reference file to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes unnecessary explanation of what Abstract is ('Abstract is a design collaboration platform...') which Claude already knows. The overview section listing entities (Task, Project, Section, etc.) with 'Use action names and parameters as needed' is vague filler. The Membrane CLI setup and proxy sections are reasonably efficient but could be tightened. | 2 / 3 |
Actionability | The skill provides concrete, executable CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Commands are copy-paste ready with clear flag explanations and JSON output options. | 3 / 3 |
Workflow Clarity | The multi-step connection workflow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, errors) and feedback loops (poll until ready, handle client actions, re-check state). The progression from install → authenticate → connect → discover actions → run actions is logical and well-structured with validation at each stage. | 3 / 3 |
Progressive Disclosure | The content is a single monolithic file with no references to supporting files. While the structure uses headers and sections reasonably well, the proxy request options table and detailed connection state handling could be split into separate reference files. For a skill of this length (~120 lines of content), some separation would improve navigability. | 2 / 3 |
Total | 10 / 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
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.