Automate Accredible Certificates tasks via Rube MCP (Composio). Always search tools first for current schemas.
58
40%
Does it follow best practices?
Impact
90%
22.50xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./composio-skills/accredible-certificates-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 too vague to effectively guide skill selection. It names the platform (Accredible) but fails to specify what certificate-related tasks can be performed and provides no guidance on when Claude should select this skill. The operational instruction about searching tools first doesn't help with skill selection.
Suggestions
Add specific actions like 'Create digital certificates, issue credentials to recipients, manage certificate templates, track credential analytics'
Add a 'Use when...' clause with trigger terms like 'digital certificates', 'credentials', 'badges', 'Accredible', 'certificate issuance'
Remove or relocate the operational guidance ('Always search tools first') to the skill body, as it doesn't help with skill selection
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Automate...tasks' without specifying what concrete actions can be performed. No specific capabilities like 'create certificates', 'issue credentials', or 'manage recipients' are mentioned. | 1 / 3 |
Completeness | The 'what' is extremely vague ('tasks') and there is no 'Use when...' clause or equivalent trigger guidance. The instruction to 'search tools first' is operational guidance, not selection criteria. | 1 / 3 |
Trigger Term Quality | Includes 'Accredible Certificates' and 'Composio' which are relevant domain terms, but lacks natural user phrases like 'digital badges', 'credentials', 'certificate issuance', or common variations users might say. | 2 / 3 |
Distinctiveness Conflict Risk | 'Accredible Certificates' provides some distinctiveness as a specific platform, but 'Automate...tasks via Rube MCP (Composio)' pattern could conflict with other Composio-based skills if multiple exist. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable template for Accredible Certificates automation via Rube MCP with clear structure and good organization. However, it lacks executable examples with realistic values, validation/error handling steps, and contains some redundant content between sections. The guidance is more descriptive than actionable.
Suggestions
Add a concrete end-to-end example with realistic values (e.g., creating a specific certificate) showing actual tool slugs and arguments
Include validation steps after tool execution - how to verify the operation succeeded and what to do if it fails
Consolidate the Setup and Core Workflow Pattern sections to eliminate redundancy around connection checking
Add error handling guidance - what errors might occur and how to recover from them
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundancy - the 'Core Workflow Pattern' section largely repeats information from earlier sections, and the prerequisites/setup sections overlap. Could be tightened by consolidating. | 2 / 3 |
Actionability | Provides concrete tool call patterns with parameter examples, but these are pseudocode-style representations rather than actual executable code. The tool calls show structure but lack complete, copy-paste ready examples with realistic values. | 2 / 3 |
Workflow Clarity | Steps are clearly sequenced (discover → check connection → execute), but lacks explicit validation checkpoints. No guidance on what to do if tool execution fails, no feedback loops for error recovery, and no verification that operations succeeded. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, a quick reference table, and external link to toolkit docs. Content is appropriately scoped for a SKILL.md file without unnecessary nesting or monolithic walls of text. | 3 / 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 | |
2790447
Table of Contents
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.