21risk
21RISK integration. Manage data, records, and automate workflows. Use when the user wants to interact with 21RISK 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/21risk/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 the distinctive '21RISK' product name and includes an explicit 'Use when' clause, but it is severely lacking in specificity about what concrete actions the skill can perform. The vague terms 'data', 'records', and 'workflows' provide almost no information about the actual capabilities, making it hard for Claude to distinguish this from other integration skills when the user doesn't explicitly mention 21RISK.
Suggestions
Replace vague terms like 'manage data, records, and automate workflows' with specific actions the skill performs, e.g., 'create risk assessments, manage audit findings, track compliance tasks, generate risk reports'.
Add domain-specific trigger terms to the 'Use when' clause, such as 'risk assessment', 'compliance', 'audit', 'safety inspection', or whatever 21RISK-specific concepts users would mention.
Include file types or specific 21RISK entities (e.g., 'risk registers', 'action items', 'control measures') to improve both specificity and trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Manage data, records, and automate workflows' which are extremely vague actions. There are no concrete, specific capabilities listed — 'data', 'records', and 'workflows' could apply to virtually any system. | 1 / 3 |
Completeness | The description answers both 'what' (manage data, records, automate workflows) and 'when' ('Use when the user wants to interact with 21RISK data'). While the what is vague, the explicit 'Use when...' clause is present and provides clear trigger guidance. | 3 / 3 |
Trigger Term Quality | The term '21RISK' is a strong, distinctive trigger keyword that users would naturally say. However, beyond the product name, the other terms ('data', 'records', 'workflows') are generic and don't include domain-specific terms users might use (e.g., risk assessments, audits, compliance, inspections). | 2 / 3 |
Distinctiveness Conflict Risk | The '21RISK' product name provides good distinctiveness and is unlikely to conflict with other skills. However, the generic terms 'manage data, records, and automate workflows' could overlap with other integration or data management skills if the user doesn't explicitly mention 21RISK. | 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 solid integration skill with strong actionability — every operation has a concrete, executable CLI command. The main weaknesses are some unnecessary introductory content (explaining what 21RISK is), a somewhat bare entity overview section that doesn't add value, and missing explicit validation/error-recovery steps in the workflow beyond the action creation polling loop.
Suggestions
Remove or drastically shorten the opening paragraph explaining what 21RISK is — Claude doesn't need this context, and the skill description already covers it.
Either flesh out the 'Overview' entity list with actionable details (e.g., which actions map to which entities) or remove it entirely since it currently adds no instructional value.
Add error handling guidance for key steps: what to do if `membrane connect` fails, if `action run` returns an error, or if authentication times out.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary filler. The opening paragraph explaining what 21RISK is (SaaS platform for risk and compliance) is information Claude doesn't need. The 'Overview' section listing entities without context adds little value. Some best practices are slightly verbose but generally useful. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste-ready CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, running actions with parameters. Each command includes concrete flags and placeholders that are clear and actionable. | 3 / 3 |
Workflow Clarity | The steps are presented in a logical sequence (install → authenticate → connect → search → create/run), but there are validation gaps. The action creation workflow includes polling with state checking (BUILDING → READY/error), which is good, but the overall flow lacks explicit validation checkpoints and error recovery guidance for other steps (e.g., what if connection fails, what if action run fails). | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but it's somewhat monolithic — all content is inline in a single file. The 'Overview' section listing entities could link to detailed docs. The skill references official docs but doesn't split advanced content (like action creation details or error handling) into separate files, though for this skill's length it's borderline acceptable. | 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.