confirm-action
Ask the user to confirm before taking a significant action. Use before containment, remediation, or other impactful operations to ensure analyst approval. Presents options and waits for response.
63
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.
This is a solid description that clearly communicates both purpose and trigger conditions. The explicit 'Use before...' clause with specific operation types (containment, remediation) provides good guidance for skill selection. However, the description could benefit from more specific action examples and broader trigger term coverage.
Suggestions
Add more specific examples of 'significant actions' beyond containment/remediation (e.g., 'isolation', 'blocking', 'quarantine', 'deletion')
Include additional natural trigger terms users might say like 'verify', 'approve', 'dangerous', 'destructive', or 'irreversible action'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (security operations) and some actions ('containment, remediation, or other impactful operations'), but 'significant action' and 'impactful operations' remain somewhat vague. 'Presents options and waits for response' adds some concrete behavior. | 2 / 3 |
Completeness | Clearly answers both what ('Ask the user to confirm before taking a significant action', 'Presents options and waits for response') and when ('Use before containment, remediation, or other impactful operations to ensure analyst approval'). | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'confirm', 'containment', 'remediation', and 'analyst approval', but missing common variations users might say like 'verify', 'approve', 'dangerous action', 'destructive', or 'irreversible'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on confirmation workflows before impactful security operations. The specific context of 'analyst approval' and 'containment, remediation' makes it unlikely to conflict with general-purpose skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable conceptual framework for confirmation prompts with good examples of when to use them and sample question formats. However, it lacks any executable implementation - there's no code showing how to actually present confirmations, collect responses, or integrate with calling workflows. The skill reads more like a design document than actionable guidance.
Suggestions
Add executable code showing how to implement the confirmation prompt (e.g., a function that presents options and returns the user's selection)
Provide concrete integration examples showing how a calling workflow would use the confirmation response for decision branching
Include handling for edge cases like timeouts, invalid responses, or user cancellation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary structure like the formal Inputs/Outputs tables and workflow steps for what is essentially a simple confirmation prompt pattern. The 'When to Use' section adds value but could be more compact. | 2 / 3 |
Actionability | The skill describes a confirmation workflow abstractly but provides no executable code, API calls, or concrete implementation. The examples show question/options format but not how to actually implement the confirmation mechanism or integrate it with any system. | 1 / 3 |
Workflow Clarity | The three-step workflow (Present, Wait, Return) is clear but extremely high-level. There's no guidance on error handling, timeout behavior, or what happens if the user provides unexpected input. For a simple confirmation skill, this is adequate but lacks implementation detail. | 2 / 3 |
Progressive Disclosure | For a skill of this size and scope, the organization is appropriate. Content is well-structured with clear sections, and there's no need for external file references. The 'When to Use' and 'Example Confirmations' sections are appropriately placed. | 3 / 3 |
Total | 8 / 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.