agiloft
Agiloft integration. Manage data, records, and automate workflows. Use when the user wants to interact with Agiloft data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill agiloft72
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 has a solid structure with explicit 'what' and 'when' clauses, and the Agiloft product name provides some distinctiveness. However, the capabilities listed are quite generic ('manage data, records, automate workflows') and could benefit from more specific actions and trigger terms that reflect what Agiloft actually does (contract lifecycle management, etc.).
Suggestions
Add more specific concrete actions like 'create contracts, update records, query tables, trigger approval workflows' to improve specificity
Include domain-specific trigger terms users might naturally say such as 'contract management', 'CLM', 'contract lifecycle', or specific Agiloft table/object names
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Agiloft) and mentions some actions ('Manage data, records, and automate workflows'), but these are fairly generic and not comprehensive - doesn't specify what types of records, what workflow automations, or concrete operations like create/update/delete. | 2 / 3 |
Completeness | Explicitly answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Agiloft data') with a clear trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'Agiloft' as a key trigger term and 'data', 'records', 'workflows', but missing common variations users might say like 'contract management', 'CLM', specific Agiloft features, or API-related terms. | 2 / 3 |
Distinctiveness Conflict Risk | 'Agiloft' is a distinct product name which helps, but 'manage data, records, and automate workflows' is generic enough to potentially overlap with other CRM/database/workflow skills. The 'Agiloft data' trigger helps but could be more specific. | 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 Agiloft integration via Membrane, with good executable examples. However, it includes unnecessary introductory content, lacks validation checkpoints in workflows, and has a confusing overview section that doesn't connect to actionable guidance. The structure could benefit from clearer decision trees and error handling.
Suggestions
Remove or minimize the introductory paragraph about what Agiloft is - Claude already knows this. The overview bullet list (Knowledge Base, Article, etc.) should either be removed or explained with actionable context.
Add validation steps after key operations, e.g., 'Verify connection succeeded: membrane connection list --json | grep CONNECTION_ID'
Add a decision tree or clearer workflow for 'check existing connection -> use it OR create new one' rather than presenting them as separate sections
Include example output snippets showing what successful responses look like so Claude can verify operations completed correctly
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'Agiloft is a contract lifecycle management platform' and the overview section with bullet points that don't add actionable value). The Membrane CLI setup and usage sections are reasonably efficient but could be tighter. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout with clear syntax examples. Commands are copy-paste ready with proper flags and JSON output options. The proxy request section includes a helpful options table. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection but lack validation checkpoints. No explicit error handling or verification steps after running actions. The workflow for checking existing connections vs creating new ones could be clearer with decision points. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. The overview section with bullet points (Knowledge Base, Article, Record, etc.) is cryptic and doesn't link to any detailed documentation. No references to external files for advanced topics. | 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.