accredible
Accredible integration. Manage data, records, and automate workflows. Use when the user wants to interact with Accredible data.
58
67%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 benefits from naming the specific platform (Accredible) and including an explicit 'Use when' clause, but it is severely lacking in specificity about what actions can be performed. The generic phrases 'manage data, records, and automate workflows' could apply to virtually any integration skill, making it hard to distinguish and unlikely to trigger for users who don't already know the Accredible brand name.
Suggestions
Replace vague terms like 'manage data, records, and automate workflows' with concrete Accredible-specific actions such as 'issue digital credentials, create certificates, manage badge templates, track credential analytics'.
Add natural trigger terms users would say, such as 'credentials', 'certificates', 'badges', 'digital certifications', 'credential management', or 'Accredible API'.
Expand the 'Use when' clause with specific scenarios like 'Use when the user needs to issue, revoke, or track digital credentials, certificates, or badges through Accredible'.
| 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 — terms like 'issue credentials', 'create certificates', 'manage badges' would be far more specific. | 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 useful for brand-specific queries, but lacks natural keywords users might say such as 'credentials', 'certificates', 'badges', 'digital credentials', or 'certification platform'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Manage data, records, and automate workflows' is extremely generic and could overlap with many integration skills. However, the explicit mention of 'Accredible' provides some distinctiveness for brand-specific queries. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
77%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 and clear workflow sequencing for the Membrane CLI connection process. Its main weaknesses are moderate verbosity (introductory explanation, empty-description action table) and a monolithic structure that could benefit from splitting reference material into separate files. The skill effectively guides Claude through the complete lifecycle of interacting with Accredible via Membrane.
Suggestions
Remove the introductory paragraph explaining what Accredible is — Claude already knows this, and the skill description covers it.
Either add meaningful descriptions to the popular actions table entries or remove the table entirely, since 'No description' repeated 20 times wastes tokens without adding value.
Consider extracting the proxy request reference table and popular actions into a separate REFERENCE.md file to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'Accredible is a platform for creating, issuing, and managing digital credentials...') and the popular actions table has 'No description' for every entry, adding bulk without value. The Membrane CLI setup and connection flow are reasonably efficient but could be tightened. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste-ready CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Parameters and flags are clearly documented with examples. | 3 / 3 |
Workflow Clarity | The connection workflow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, errors), polling instructions, and conditional branching. The overall flow from install → authenticate → connect → discover actions → run actions is well-structured with validation checkpoints at each state transition. | 3 / 3 |
Progressive Disclosure | The content is reasonably organized with clear sections, but it's somewhat monolithic for its length. The popular actions table with 20 rows of 'No description' could be trimmed or moved to a reference file. There are no bundle files or references to supplementary materials despite the content length warranting it. | 2 / 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 | |
- Repository
- membranedev/application-skills
- Commit
f484c82
- 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.