21RISK integration. Manage data, records, and automate workflows. Use when the user wants to interact with 21RISK data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill 21risk75
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
75%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 adequately identifies the integration target (21RISK) and provides explicit 'Use when' guidance, making it complete and distinctive. However, it lacks specific concrete actions beyond generic terms like 'manage data' and 'automate workflows', and could benefit from more natural trigger terms related to risk management domain vocabulary.
Suggestions
Add specific concrete actions like 'create risk assessments', 'track incidents', 'generate compliance reports', or 'manage audit trails' to improve specificity.
Include domain-related trigger terms users might naturally say such as 'risk management', 'compliance', 'safety records', 'audits', or 'incident tracking'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (21RISK) and mentions general actions ('Manage data, records, and automate workflows'), but lacks specific concrete actions like 'create risk assessments', 'generate compliance reports', or 'update audit records'. | 2 / 3 |
Completeness | Answers both 'what' (manage data, records, automate workflows) and 'when' with explicit trigger guidance ('Use when the user wants to interact with 21RISK data'). | 3 / 3 |
Trigger Term Quality | Includes the product name '21RISK' which users would say, but lacks natural variations or related terms users might use like 'risk management', 'compliance', 'audit', or 'safety records'. | 2 / 3 |
Distinctiveness Conflict Risk | The specific product name '21RISK' creates a clear niche that is unlikely to conflict with other skills; it's a distinct integration for a named platform. | 3 / 3 |
Total | 10 / 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 21RISK integration via Membrane with good coverage of common operations. However, it includes some unnecessary content (the entity overview list, platform description) and lacks validation checkpoints for multi-step workflows like connection setup and action execution.
Suggestions
Remove the '21RISK Overview' bullet list and platform description - they don't provide actionable guidance
Add validation steps after key operations (e.g., 'Verify connection succeeded by running membrane connection list' after connecting)
Include error handling guidance for common failure scenarios like failed authentication or invalid action IDs
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary explanation (e.g., 'SaaS platform for managing risk and compliance' description, the overview section listing entities without actionable context). The Membrane explanation could be tighter. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout with concrete examples for installation, login, connection creation, action discovery, and proxy requests. Commands are copy-paste ready with clear parameter placeholders. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection flows, but validation checkpoints are missing. No guidance on verifying successful connection, handling failed authentication, or confirming action execution succeeded before proceeding. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the '21RISK Overview' bullet list adds no value and could be removed. No references to external detailed documentation for advanced use cases despite linking to official docs without context. | 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 | |
Table of Contents
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.