agiled-automation
Automate Agiled tasks via Rube MCP (Composio). Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:haniakrim21/everything-claude-code --skill agiled-automation68
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/skillEvaluation — 92%
↑ 4.00xAgent success when using this skill
Validation for skill structure
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is too vague to be useful for skill selection. It names the integration (Agiled via Rube MCP/Composio) but fails to describe what specific capabilities are available or when Claude should select this skill. The procedural note about searching tools first is implementation guidance that doesn't help with skill selection.
Suggestions
Add specific capabilities that Agiled supports, such as 'manage CRM contacts, create invoices, track projects, log time entries'
Add an explicit 'Use when...' clause with trigger terms like 'Agiled', 'business management', 'client invoices', 'project tracking'
Remove the procedural guidance ('Always search tools first') from the description - this belongs in the skill body, not the selection-focused description
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Automate Agiled tasks' which is extremely vague - it doesn't specify what tasks can be automated (e.g., create projects, manage invoices, track time). 'Always search tools first' is procedural guidance, not a capability description. | 1 / 3 |
Completeness | The 'what' is extremely weak ('automate tasks' is not specific), and there is no 'when' clause or explicit trigger guidance. The description fails to answer either question adequately. | 1 / 3 |
Trigger Term Quality | Contains 'Agiled' which is a specific product name users might mention, and 'Rube MCP' and 'Composio' as technical terms. However, it lacks natural task-oriented keywords users would say like 'CRM', 'invoices', 'projects', 'clients', or 'time tracking'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Agiled' is a specific product name which provides some distinctiveness, but 'automate tasks via MCP' is generic enough to potentially conflict with other Composio/MCP-based automation skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that efficiently guides Claude through Agiled automation via Rube MCP. The workflow is clear with proper validation checkpoints, and the content respects token budget. The main weakness is that tool call examples use placeholder syntax rather than fully concrete examples, which slightly reduces immediate actionability.
Suggestions
Replace placeholder comments like '/* schema-compliant args from search results */' with a concrete example showing actual Agiled-specific arguments (e.g., creating a contact or task)
Add one complete end-to-end example showing a real Agiled operation from search through execution with actual field values
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of what Agiled or Composio are. Every section provides actionable information without padding or unnecessary context. | 3 / 3 |
Actionability | Provides concrete tool call patterns with parameter examples, but uses pseudocode-style blocks rather than fully executable code. The argument placeholders like '/* schema-compliant args from search results */' reduce copy-paste readiness. | 2 / 3 |
Workflow Clarity | Clear 3-step workflow with explicit sequencing (discover → check connection → execute). Includes validation checkpoint for connection status ('Confirm connection status shows ACTIVE before running any workflows') and error recovery guidance in Known Pitfalls. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from prerequisites to setup to workflow to pitfalls. External reference to toolkit docs is one level deep and clearly signaled. Quick reference table provides efficient navigation. | 3 / 3 |
Total | 11 / 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.