accredible-certificates-automation
Automate Accredible Certificates 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 accredible-certificates-automation60
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/skillValidation 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 effectively guide skill selection. It names the integration (Accredible via Composio) but fails to specify what actions are possible or when Claude should use 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, manage recipient groups, track certificate status'
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 a usage trigger. | 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' and 'Rube MCP (Composio)' provide some specificity that distinguishes it from generic automation skills, but the vague 'tasks' language could still cause confusion with other certificate or automation-related skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
70%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 solid structural framework for Accredible Certificates automation with clear workflow sequencing and good organization. However, it suffers from some redundancy and lacks concrete, executable examples - the tool calls show placeholder arguments rather than real-world examples that would make the skill immediately actionable.
Suggestions
Replace placeholder arguments like '/* schema-compliant args from search results */' with at least one concrete example showing actual Accredible Certificates parameters (e.g., creating a credential or issuing a certificate)
Consolidate the repeated 'always search first' guidance - it appears in Prerequisites, Tool Discovery, and Known Pitfalls sections
Add a concrete end-to-end example showing a complete workflow (e.g., 'Issue a certificate to a recipient') with actual tool slugs and arguments
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundancy - the 'always search first' instruction appears multiple times, and the workflow pattern section largely repeats information from earlier sections. | 2 / 3 |
Actionability | Provides concrete tool call patterns with parameter structures, but examples use placeholder syntax rather than fully executable commands. The arguments are shown as comments ('/* schema-compliant args */') rather than real examples. | 2 / 3 |
Workflow Clarity | Clear 3-step workflow with explicit sequencing (discover → check connection → execute). Includes validation checkpoint (verify ACTIVE status before executing) and the Known Pitfalls section provides error recovery guidance. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from prerequisites to setup to workflow to pitfalls. Quick reference table provides scannable summary. External link to toolkit docs for deeper information without nesting. | 3 / 3 |
Total | 10 / 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.