agave
Agave integration. Manage data, records, and automate workflows. Use when the user wants to interact with Agave data.
58
67%
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/agave/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 benefits from naming a specific product (Agave) and including an explicit 'Use when...' clause, but it is severely lacking in specificity of capabilities. The actions described are generic platitudes that could apply to virtually any data platform integration, making it hard for Claude to confidently select this skill over others.
Suggestions
Replace vague actions like 'manage data' and 'automate workflows' with concrete Agave-specific operations (e.g., 'query Agave records, create entries, update fields, run automation pipelines').
Add Agave-specific trigger terms and domain context so users' natural language maps to this skill (e.g., mention specific Agave entity types, API operations, or common use cases).
Expand the 'Use when...' clause with more specific trigger scenarios (e.g., 'Use when the user mentions Agave, wants to query Agave records, sync Agave data, or automate Agave workflows').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The actions listed ('manage data, records, and automate workflows') are extremely vague and generic. There are no concrete actions like 'create records', 'query fields', 'trigger pipeline runs', etc. 'Manage data' and 'automate workflows' could apply to almost any integration. | 1 / 3 |
Completeness | It does answer both 'what' (manage data, records, automate workflows) and 'when' ('Use when the user wants to interact with Agave data'). The explicit 'Use when...' clause is present, though both parts are quite shallow in detail. | 3 / 3 |
Trigger Term Quality | The term 'Agave' is a specific product name that would serve as a natural trigger keyword. However, beyond that, the terms 'data', 'records', and 'workflows' are overly generic and not specific to Agave's domain. Missing variations or domain-specific terms users might say. | 2 / 3 |
Distinctiveness Conflict Risk | 'Agave' as a product name provides some distinctiveness, but 'manage data, records, and automate workflows' is so generic it could overlap with many other integration or data management skills. Without specifying what makes Agave unique, conflict risk remains moderate. | 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 strong actionability and workflow clarity — the CLI commands are concrete and the connection state machine is well-documented with clear branching logic. The main weaknesses are minor verbosity (introductory fluff, unexpanded overview section) and a somewhat monolithic structure that could benefit from splitting detailed reference material (like the proxy options table or state handling) into separate files.
Suggestions
Remove the introductory paragraph explaining what Agave is — Claude can infer this from context, and the official docs link suffices.
Either expand the 'Agave Overview' section with actionable details about each entity type or remove it entirely, as the bare bullet list adds no value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content includes some unnecessary explanation (e.g., 'Agave is a platform for managing and automating scientific workflows. It's used by researchers and scientists...') and the overview section listing Files, Folders, Apps, Tasks, Users adds little value without further detail. However, most of the content is reasonably efficient with concrete commands. | 2 / 3 |
Actionability | The skill provides fully 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 descriptions and a useful options table. | 3 / 3 |
Workflow Clarity | The multi-step connection workflow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, errors), polling instructions, and conditional branching. The flow from authentication through connection setup to action discovery and execution is well-structured with clear checkpoints. | 3 / 3 |
Progressive Disclosure | The content is structured with clear sections and headers, but it's somewhat monolithic for its length (~120 lines of substantive content). The Agave Overview section lists entities without linking to any detailed documentation or sub-files. There are no bundle files to reference, and the external docs link is provided but not leveraged for offloading detail. | 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.