accredible
Accredible integration. Manage data, records, and automate workflows. Use when the user wants to interact with Accredible data.
68
61%
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 ./skills/accredible/SKILL.mdQuality
Discovery
57%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 relies heavily on the 'Accredible' brand name for distinctiveness but fails to describe what Accredible actually does or what specific actions the skill enables. The 'what' and 'when' clauses are structurally present but substantively hollow, using generic phrases like 'manage data' and 'automate workflows' that provide no meaningful differentiation from other integration skills.
Suggestions
Replace vague terms like 'manage data, records, and automate workflows' with Accredible-specific actions such as 'issue digital certificates and badges, manage credential recipients, track credential views and shares'.
Add domain-specific trigger terms users would naturally say, such as 'credentials', 'certificates', 'badges', 'digital credentials', 'certification', or 'credential management'.
Expand the 'Use when' clause with specific scenarios like 'Use when the user mentions Accredible, digital credentials, issuing certificates, badge management, or credential tracking'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without specifying concrete actions. It doesn't mention what kind of data, what records, or what workflows — these are generic terms that could apply to almost any integration. | 1 / 3 |
Completeness | It does answer both 'what' (manage data, records, automate workflows) and 'when' (when the user wants to interact with Accredible data) with an explicit 'Use when' clause, even though both parts are vague in substance. | 3 / 3 |
Trigger Term Quality | It includes 'Accredible' as a key trigger term which is specific and useful, but lacks natural keywords users might say such as 'credentials', 'certificates', 'badges', 'digital credentials', or 'certification management' that are associated with the Accredible platform. | 2 / 3 |
Distinctiveness Conflict Risk | 'Manage data, records, and automate workflows' is extremely generic and could overlap with dozens of other integration skills. However, the 'Accredible' name provides some distinctiveness as a specific platform identifier. | 2 / 3 |
Total | 8 / 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 is a functional integration skill with strong actionability — all CLI commands are concrete and executable. However, it suffers from some wasted tokens (explanatory intro, description-less action table) and lacks explicit validation steps for destructive operations. The structure is adequate but could benefit from better progressive disclosure and a clearer end-to-end workflow sequence.
Suggestions
Remove the introductory paragraph explaining what Accredible is — Claude already knows this. Use those tokens for something more valuable like example workflows.
Either add meaningful descriptions to the popular actions table or remove it entirely, as 'No description' repeated 20 times wastes tokens without adding value.
Add explicit validation/confirmation guidance for destructive operations (delete-credential, delete-group) — e.g., 'Always confirm with the user before running delete actions' or 'Verify the credential/group exists before deleting.'
Consider adding a concrete end-to-end example (e.g., 'Create a credential and assign it to a group') showing the full workflow with actual commands chained together.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'Accredible is a platform for creating, issuing, and managing digital credentials...') that Claude already knows. The popular actions table has 'No description' for every entry, adding bulk without value. The overview section with bullet points is vague and doesn't earn its tokens. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste-ready CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, and running actions with parameters. The commands include specific flags and JSON input examples. | 3 / 3 |
Workflow Clarity | The workflow follows a logical sequence (install → authenticate → connect → discover → run), and the action creation flow includes polling with state checking. However, there are no explicit validation checkpoints for destructive operations like delete-credential or delete-group, and the overall flow is implicit rather than explicitly numbered/sequenced. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but it's somewhat monolithic — the popular actions table (with no descriptions) could be in a separate reference file. The overview section is too sparse to be useful, and there's no clear signaling to external references beyond the API docs link. | 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.
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
- membranedev/application-skills
- Commit
56d7336
- 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.