risk-assessment-creator
Risk Assessment Creator - Auto-activating skill for Enterprise Workflows. Triggers on: risk assessment creator, risk assessment creator Part of the Enterprise Workflows skill category.
35
3%
Does it follow best practices?
Impact
92%
0.94xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/20-enterprise-workflows/risk-assessment-creator/SKILL.mdQuality
Discovery
7%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 extremely weak, essentially serving as a label rather than a functional description. It provides no concrete actions, no meaningful trigger terms beyond the skill name repeated, and no guidance on when Claude should select this skill. It reads as auto-generated boilerplate with no substantive content.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Identifies potential risks, scores likelihood and impact, generates risk matrices, and produces mitigation plans for projects or business initiatives.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about risk analysis, risk matrices, threat assessment, risk registers, risk scoring, or evaluating project/business risks.'
Remove the duplicate trigger term and expand with natural language variations users would actually say, such as 'risk evaluation', 'risk report', 'assess risks', 'risk mitigation plan'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Risk Assessment Creator') without describing any concrete actions. There are no specific capabilities listed such as identifying risks, scoring likelihood, generating mitigation plans, or producing risk matrices. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause with meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('risk assessment creator, risk assessment creator'). There are no natural user-language variations like 'risk analysis', 'risk matrix', 'threat assessment', 'risk register', or 'evaluate risks'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'risk assessment' is somewhat specific to a domain niche, which provides some distinctiveness. However, the lack of concrete actions or clear scope means it could overlap with other enterprise or assessment-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no substantive content. It consists entirely of auto-generated boilerplate that describes what a risk assessment creator skill would do without actually providing any instructions, examples, templates, or actionable guidance. It fails on every dimension of the rubric.
Suggestions
Add a concrete risk assessment template or framework (e.g., a risk register table with columns for likelihood, impact, mitigation) that Claude can populate for users.
Include at least one worked example showing input (project description) and output (completed risk assessment) so the skill is actionable.
Define a clear multi-step workflow for creating a risk assessment, such as: 1) Identify risks, 2) Score likelihood/impact, 3) Define mitigations, 4) Validate completeness, with explicit validation checkpoints.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill rather than instruct, and replace them with actual risk assessment creation guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual instructions, code, or concrete guidance. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero actionable content—no concrete steps, no code, no commands, no examples of actual risk assessment creation. The 'capabilities' section lists abstract promises ('provides step-by-step guidance') without delivering any. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of placeholder text with no references to detailed materials, no links to supporting files, and no meaningful structural organization beyond boilerplate headings. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
dc559db
- 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.