accredible
Accredible integration. Manage data, records, and automate workflows. Use when the user wants to interact with Accredible data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill accredible55
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
25%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 be useful for skill selection. It fails to explain what Accredible actually is (a digital credentialing platform) or what specific actions can be performed. The generic phrasing 'manage data, records, and automate workflows' could apply to dozens of different integrations.
Suggestions
Add specific actions that explain Accredible's purpose: 'Issue digital credentials and certificates, create badge designs, verify credential authenticity, manage recipient groups'
Include natural trigger terms users would say: 'credentials', 'certificates', 'badges', 'digital badges', 'certification', 'credential verification'
Expand the 'Use when' clause with specific scenarios: 'Use when the user mentions issuing certificates, creating digital badges, verifying credentials, or managing certification programs'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Manage data, records, and automate workflows' without specifying concrete actions. It doesn't explain what Accredible is or what specific operations can be performed (e.g., issue credentials, create badges, verify certificates). | 1 / 3 |
Completeness | Has a 'Use when' clause but it's extremely vague ('interact with Accredible data'). The 'what' portion is generic and doesn't explain the actual capabilities. The trigger guidance provides no useful context for when to select this skill. | 2 / 3 |
Trigger Term Quality | Only includes 'Accredible' as a trigger term. Missing natural keywords users might say like 'credentials', 'certificates', 'badges', 'digital credentials', 'certification', or 'credential management'. | 1 / 3 |
Distinctiveness Conflict Risk | 'Accredible' as a proper noun provides some distinctiveness, but 'Manage data, records, and automate workflows' is generic enough to conflict with many integration skills. Without specific credential/certification terminology, it could be confused with other data management tools. | 2 / 3 |
Total | 6 / 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 skill provides solid, actionable CLI commands for Accredible integration via Membrane, with good coverage of common operations. However, it wastes tokens on platform explanations Claude doesn't need, lacks validation/error handling guidance, and the action table with empty descriptions adds bulk without value.
Suggestions
Remove the introductory paragraph explaining what Accredible is - Claude already knows this
Add validation steps after connection creation (e.g., 'Verify connection: membrane connection list --json | grep accredible')
Either populate the action descriptions in the table or remove entries without descriptions to reduce noise
Add error handling guidance for common failure scenarios (auth failures, rate limits, invalid inputs)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'Accredible is a platform for creating...' which Claude already knows) and the overview section with bullet points adds little value. The action table with 'No description' entries is verbose without being informative. | 2 / 3 |
Actionability | Provides fully executable CLI commands with clear syntax, including authentication flow, connection setup, action discovery, and proxy requests. Commands are copy-paste ready with proper flags and options documented. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection, but validation checkpoints are missing. No guidance on verifying successful connection, handling failed actions, or error recovery. The workflow assumes success without feedback loops. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. The action table could be a separate reference file, and there are no links to additional resources beyond the official docs URL. | 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 | |
- 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.