agiloft
Agiloft integration. Manage data, records, and automate workflows. Use when the user wants to interact with Agiloft data.
57
66%
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/agiloft/SKILL.mdQuality
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 correctly identifies the platform (Agiloft) and includes an explicit 'Use when' clause, which is good. However, the actions described are generic ('manage data, records, automate workflows') and lack the concrete specificity that would help Claude confidently select this skill. Adding more specific capabilities and trigger terms related to Agiloft's domain (e.g., contract lifecycle management) would strengthen it.
Suggestions
Add more specific concrete actions such as 'create and update contracts, run saved searches, configure approval workflows, manage contract lifecycle stages'.
Include additional natural trigger terms users might say, such as 'CLM', 'contract management', 'Agiloft API', or specific Agiloft entity types like 'contracts', 'approvals', 'clauses'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Agiloft) and some actions ('manage data, records, and automate workflows'), but these are fairly generic and not comprehensive — it doesn't list specific concrete actions like 'create contracts', 'query records', 'configure approval workflows', etc. | 2 / 3 |
Completeness | It answers both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with Agiloft data), with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes 'Agiloft' as a strong trigger term and mentions 'data', 'records', and 'workflows', but misses common variations users might say such as 'contract management', 'CLM', 'Agiloft API', or specific record types. | 2 / 3 |
Distinctiveness Conflict Risk | 'Manage data, records, and automate workflows' is quite generic and could overlap with other CRM/database/workflow skills. However, the explicit mention of 'Agiloft' provides some distinctiveness for that specific platform. | 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 coverage of authentication, connection management, action discovery, and proxy requests. Its main weaknesses are some unnecessary introductory content, a stub-like overview section that adds no value, and a lack of end-to-end workflow examples showing common Agiloft tasks. The connection state machine is well-documented but the overall document reads more as a reference than a guided skill.
Suggestions
Remove or condense the introductory paragraph about what Agiloft is and the empty Overview section (Knowledge Base/Article/Record etc.) — these add no actionable value and Claude already knows what CLM platforms are.
Add a concrete end-to-end example showing a common Agiloft task (e.g., searching for a contract record and updating it) to demonstrate the full workflow from connection to action execution.
Consider splitting the proxy request reference table and connection state machine details into a separate reference file to keep the main SKILL.md focused on the happy path.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'Agiloft is a contract lifecycle management (CLM) platform. It helps legal, procurement, and sales teams automate and manage contracts from creation to renewal.' and explaining what Membrane handles). The overview section listing Knowledge Base/Article/Record/Attachment/Saved Search/Report with no context adds little value. However, the command examples themselves are reasonably lean. | 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 parameter placeholders, and the proxy request flags table is a useful concrete reference. | 3 / 3 |
Workflow Clarity | The connection setup workflow is well-sequenced with state handling (READY, BUILDING, CLIENT_ACTION_REQUIRED, errors), but there are no explicit validation checkpoints or feedback loops for the overall integration workflow. The skill doesn't provide a clear end-to-end sequence for common Agiloft tasks — it's more of a reference for individual operations than a guided workflow. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but it's somewhat monolithic — the proxy request details, best practices, and connection state machine documentation could benefit from being split out or more clearly delineated. There are no references to supporting files, and the Agiloft Overview section is a stub that doesn't connect to anything useful. | 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 | |
- 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.