agiled
Agiled integration. Manage Organizations, Leads, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Agiled data.
75
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/agiled/SKILL.mdQuality
Discovery
75%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 target platform (Agiled) and provides an explicit 'Use when' clause, making it functional for skill selection. However, it relies on the vague verb 'Manage' rather than listing specific actions, and it lacks natural trigger terms users might use such as 'CRM', 'sales pipeline', or action verbs like 'create', 'update', 'delete'.
Suggestions
Replace the vague 'Manage' with specific actions like 'Create, update, delete, and list Organizations, Leads, Pipelines, Users, Goals, and Filters'.
Add natural trigger terms users might say, such as 'CRM', 'sales pipeline', 'contacts', or 'deal tracking' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Agiled) and lists entity types (Organizations, Leads, Pipelines, Users, Goals, Filters), but 'Manage' is a vague verb that doesn't specify concrete actions like create, update, delete, or list. | 2 / 3 |
Completeness | Answers both 'what' (manage Organizations, Leads, Pipelines, Users, Goals, Filters in Agiled) and 'when' ('Use when the user wants to interact with Agiled data'), providing an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'Agiled' as a key trigger term and entity names like 'Leads', 'Pipelines', 'Organizations' which users might mention, but lacks action-oriented trigger terms (e.g., 'create lead', 'CRM', 'sales pipeline') and common variations users would naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | 'Agiled' is a specific product name that creates a clear niche, making it very unlikely to conflict with other skills. The entity types further narrow the scope. | 3 / 3 |
Total | 10 / 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 is a functional integration skill with strong actionability — all CLI commands are concrete and executable. The main weaknesses are some unnecessary explanatory content (what Agiled is, the overview bullet list), a large inline actions table that could be externalized, and missing error recovery/validation steps for key operations like running actions or handling connection failures.
Suggestions
Remove the opening paragraph explaining what Agiled is and the 'Agiled Overview' bullet list — Claude doesn't need this context to use the integration.
Add error handling guidance for failed action runs (e.g., what to check, how to retry) to improve workflow clarity.
Move the popular actions table to a separate reference file and link to it from the main skill to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Agiled is ('all-in-one business management platform...') is unnecessary context Claude already knows. The 'Agiled Overview' bullet list adds little value. The popular actions table is large but arguably useful. Some sections could be tightened. | 2 / 3 |
Actionability | Provides fully executable CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, polling, and running actions with input parameters. Commands are copy-paste ready with clear placeholders. | 3 / 3 |
Workflow Clarity | The workflow for creating and polling actions includes a clear sequence with state checking, but the overall document lacks explicit validation checkpoints. The authentication flow for headless environments is well-sequenced. However, there's no error recovery guidance for failed action runs or connection issues. | 2 / 3 |
Progressive Disclosure | Content is reasonably structured with clear sections, but the popular actions table is quite long and could be referenced externally. The document is somewhat monolithic — everything is inline with no references to supplementary files. For its length (~100 lines of content), the organization is adequate but not optimal. | 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
56d7336
- 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.