ascora-automation
Automate Ascora tasks via Rube MCP (Composio). Always search tools first for current schemas.
67
53%
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 ./composio-skills/ascora-automation/SKILL.mdQuality
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 severely underdeveloped. It relies entirely on product names without explaining what Ascora is or what specific tasks can be automated. The lack of concrete actions and explicit trigger guidance makes it nearly impossible for Claude to know when to select this skill appropriately.
Suggestions
Add specific concrete actions that can be performed (e.g., 'Create jobs, manage schedules, generate invoices, track field service work')
Add a 'Use when...' clause with explicit triggers (e.g., 'Use when the user mentions Ascora, field service management, job scheduling, or work orders')
Briefly explain what Ascora is (e.g., 'field service management software') so Claude understands the domain context
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Automate Ascora tasks' which is extremely vague - it doesn't specify what kinds of tasks, what actions can be performed, or what Ascora even is. 'Always search tools first' is procedural guidance, not capability description. | 1 / 3 |
Completeness | The 'what' is extremely weak ('automate tasks' tells us nothing concrete), and there is no 'Use when...' clause or explicit trigger guidance. The description fails to answer either question adequately. | 1 / 3 |
Trigger Term Quality | Contains 'Ascora', 'Rube MCP', and 'Composio' as specific product names that users might mention, but lacks natural action-oriented keywords users would say like 'schedule', 'invoice', 'job management', or whatever Ascora actually does. | 2 / 3 |
Distinctiveness Conflict Risk | The specific product names 'Ascora' and 'Rube MCP (Composio)' provide some distinctiveness, but 'automate tasks' is generic enough to potentially conflict with other automation skills. Without knowing what Ascora does, overlap risk is unclear. | 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 Ascora automation via Rube MCP. The workflow is clear with appropriate validation checkpoints, and the content is concise without unnecessary explanation. The main weakness is that the 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 Ascora-specific arguments (e.g., creating a job or fetching customers)
Add one complete end-to-end example showing a real Ascora task from search through execution with actual response handling
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context about what Ascora or Composio are. | 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 pattern with explicit sequencing (discover → check connection → execute). Includes validation checkpoint for connection status and explicit guidance to confirm ACTIVE status before proceeding. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from prerequisites to setup to workflow to pitfalls. Quick reference table provides scannable summary. External toolkit docs linked appropriately without deep nesting. | 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 | |
- Repository
- ComposioHQ/awesome-claude-skills
- Commit
2790447
- 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.