CtrlK
BlogDocsLog inGet started
Tessl Logo

agiled

Agiled integration. Manage Organizations, Leads, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Agiled data.

Install with Tessl CLI

npx tessl i github:membranedev/application-skills --skill agiled
What are skills?

75

Does it follow best practices?

Validation for skill structure

SKILL.md
Review
Evals

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 Agiled integration with a clear 'Use when' clause, making it complete. However, it relies on the vague verb 'Manage' rather than listing specific actions, and could benefit from additional natural trigger terms that users might associate with CRM functionality.

Suggestions

Replace 'Manage' with specific actions like 'Create, update, delete, and query Organizations, Leads, Pipelines...'

Add natural trigger terms users might say, such as 'CRM', 'sales pipeline', 'contacts', or 'customer data'

DimensionReasoningScore

Specificity

Names the domain (Agiled) and lists entity types (Organizations, Leads, Pipelines, Users, Goals, Filters), but uses vague action word 'Manage' without specifying concrete actions like 'create', 'update', 'delete', or 'query'.

2 / 3

Completeness

Explicitly answers both what ('Manage Organizations, Leads, Pipelines, Users, Goals, Filters') and when ('Use when the user wants to interact with Agiled data') with a clear trigger clause.

3 / 3

Trigger Term Quality

Includes 'Agiled' as a key trigger term and lists relevant entity names, but misses natural variations users might say like 'CRM', 'sales pipeline', 'contacts', or 'customer management'.

2 / 3

Distinctiveness Conflict Risk

'Agiled' is a specific product name that creates a clear niche; unlikely to conflict with other CRM or integration skills due to the explicit product reference.

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 skill provides solid, actionable guidance for Agiled integration via Membrane CLI with executable commands and a useful actions reference table. However, it includes unnecessary introductory content about what Agiled is, lacks validation/error-handling workflows, and could benefit from better progressive disclosure by moving the large actions table to a separate reference file.

Suggestions

Remove the introductory paragraph explaining what Agiled is - Claude already knows this and it wastes tokens

Add validation checkpoints after key steps (e.g., 'Verify connection succeeded: membrane connection list --json | grep agiled')

Include error recovery guidance (e.g., what to do if authentication fails or actions return errors)

Move the popular actions table to a separate ACTIONS.md reference file and link to it from the main skill

DimensionReasoningScore

Conciseness

The skill is mostly efficient but includes some unnecessary explanation (e.g., 'Agiled is an all-in-one business management platform' and the overview section describing what Agiled is). The Membrane CLI setup instructions are reasonable but could be tightened.

2 / 3

Actionability

Provides fully executable commands throughout with specific examples for CLI installation, login, connection setup, action discovery, and running actions. The proxy request section includes concrete flag documentation and usage patterns.

3 / 3

Workflow Clarity

Steps are listed for setup and connection but lack explicit validation checkpoints. No feedback loops for error recovery (e.g., what to do if connection fails, how to verify actions succeeded). The workflow is sequential but missing verification steps.

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 skill is somewhat monolithic with all content inline rather than pointing to detailed references for advanced usage.

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

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.