agave
Agave integration. Manage data, records, and automate workflows. Use when the user wants to interact with Agave data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill agave72
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
67%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 adequately identifies the Agave platform and includes a 'Use when' clause, which is good for completeness. However, the capabilities described are quite generic ('manage data, records, automate workflows') without specifying concrete actions or Agave-specific features. The trigger terms could be expanded to include more natural variations users might say.
Suggestions
Add specific concrete actions that Agave supports (e.g., 'create records, query datasets, trigger automation rules, sync external data sources')
Expand trigger terms to include Agave-specific terminology and common user phrases (e.g., 'Agave API, Agave records, Agave automation, construction data management')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Agave) and mentions some actions ('Manage data, records, and automate workflows'), but these are fairly generic and not comprehensive - doesn't specify what kinds of data, records, or workflows. | 2 / 3 |
Completeness | Explicitly answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Agave data'), meeting the requirement for explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes 'Agave' as a key trigger term and mentions 'data', 'records', 'workflows', but lacks variations or specific terminology users might naturally say (e.g., specific Agave features, API operations, or common use cases). | 2 / 3 |
Distinctiveness Conflict Risk | 'Agave' is a specific platform which helps distinctiveness, but 'manage data, records, and automate workflows' is generic enough to potentially overlap with other data management or workflow automation skills. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable CLI commands for Agave integration via Membrane with good documentation of flags and options. However, it could be more concise by removing explanatory fluff, and would benefit from explicit validation steps in workflows (e.g., verifying connection success before proceeding). The structure is adequate but the 'Popular actions' section is essentially empty.
Suggestions
Remove introductory explanations about what Agave is and Membrane's benefits - Claude already understands these concepts
Add validation checkpoints after key steps (e.g., 'Verify connection with `membrane connection list --json` before proceeding')
Either populate the 'Popular actions' section with actual common action IDs/examples, or remove the heading entirely
Consider adding error handling guidance for common failure scenarios (auth failures, invalid action IDs)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary explanation (e.g., 'Agave is a platform for managing and automating scientific workflows' and 'so you can focus on the integration logic rather than auth plumbing'). The overview section listing entities without context adds little value. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout with clear syntax, flags documented in a table, and copy-paste ready examples including JSON parameter passing. Commands are specific and complete. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection but lack validation checkpoints. No explicit verification steps after connection creation or action execution. The workflow for headless environments is mentioned but not fully sequenced. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. The 'Popular actions' section is empty (just tells user to discover), and there's no reference to external files for advanced topics or detailed API reference. | 2 / 3 |
Total | 9 / 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 | |
- 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.