document-in-case
Add a comment to a case to document findings, actions, or recommendations. Use to maintain audit trail during investigations. Requires CASE_ID and comment text.
Install with Tessl CLI
npx tessl i github:dandye/ai-runbooks --skill document-in-case81
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
85%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 well-crafted skill description that clearly communicates its purpose and usage context. It excels at specificity and completeness with explicit 'Use to...' guidance. The main weakness is trigger term coverage, which could benefit from additional natural language variations users might employ.
Suggestions
Add natural trigger term variations like 'add note to case', 'log case activity', 'case notes', or 'document in case' to improve discoverability
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Add a comment to a case to document findings, actions, or recommendations' and specifies required inputs (CASE_ID and comment text). Clear, actionable capability. | 3 / 3 |
Completeness | Clearly answers both what ('Add a comment to a case to document findings, actions, or recommendations') and when ('Use to maintain audit trail during investigations'). Includes explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'case', 'comment', 'audit trail', 'investigations', but missing common variations users might say like 'add note', 'case notes', 'log activity', or 'document case'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche: case management comments with explicit CASE_ID requirement. Unlikely to conflict with general commenting or documentation skills due to the investigation/audit trail context. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-structured and concise, providing useful comment templates that add real value. However, the workflow lacks executable code (pseudocode instead of real Python) and the verification step is too vague for a write operation that should confirm success before proceeding.
Suggestions
Convert the pseudocode API call to fully executable Python with proper syntax and error handling
Expand Step 2 to show how to check the API response, e.g., `if response.status == 'success': ...` with explicit success/failure handling
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient with no unnecessary explanations. Every section serves a purpose - inputs, workflow, outputs, and templates are all directly actionable without padding. | 3 / 3 |
Actionability | Provides a concrete API call pattern and useful comment templates, but the code is pseudocode-style (not fully executable Python) and Step 2 'Verify Status' is vague without showing how to actually check the response. | 2 / 3 |
Workflow Clarity | Two-step workflow is listed but Step 2 lacks specifics on what constitutes success/failure or how to handle errors. No explicit validation checkpoint or error recovery guidance for a write operation. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized with clear sections (Inputs, Workflow, Outputs, Templates). No need for external references given the scope. | 3 / 3 |
Total | 10 / 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.