Detect patterns, anomalies, and trends in code and data. Use when identifying code smells, finding security vulnerabilities, or discovering recurring patterns. Handles regex patterns, AST analysis, and statistical anomaly detection.
84
78%
Does it follow best practices?
Impact
94%
1.38xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent-skills/pattern-detection/SKILL.mdQuality
Discovery
92%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 articulates specific capabilities and includes an explicit 'Use when...' clause with natural trigger terms. The description uses proper third-person voice and covers both code and data analysis domains. Minor weakness is potential overlap with security or code review skills, though the technical specificity (AST analysis, statistical anomaly detection) helps differentiate it.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Detect patterns, anomalies, and trends', 'identifying code smells', 'finding security vulnerabilities', 'discovering recurring patterns', 'regex patterns, AST analysis, and statistical anomaly detection'. | 3 / 3 |
Completeness | Clearly answers both what ('Detect patterns, anomalies, and trends in code and data') and when ('Use when identifying code smells, finding security vulnerabilities, or discovering recurring patterns'). Includes explicit 'Use when...' clause with trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'patterns', 'anomalies', 'trends', 'code smells', 'security vulnerabilities', 'regex', 'AST analysis'. These cover common variations of how users might request pattern detection. | 3 / 3 |
Distinctiveness Conflict Risk | While it specifies pattern detection and analysis, terms like 'code' and 'security vulnerabilities' could overlap with general code review or security-focused skills. The combination of AST analysis and statistical anomaly detection helps distinguish it, but some conflict risk remains. | 2 / 3 |
Total | 11 / 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 strong actionable content with executable code examples for pattern detection across multiple domains (security, code smells, data anomalies). However, it suffers from incomplete sections (empty examples), some verbosity in structure, and could benefit from clearer validation guidance for interpreting results and handling false positives.
Suggestions
Complete the empty Example sections with concrete input/output demonstrations showing actual pattern detection results
Add explicit validation steps explaining how to verify pattern detection results and distinguish true positives from false positives
Consider moving the detailed regex patterns and statistical functions to separate reference files to improve progressive disclosure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary structure (empty example sections, verbose markdown formatting). Some patterns like the 'Best practices' section state obvious guidance Claude would already know. | 2 / 3 |
Actionability | Provides fully executable bash commands and Python code throughout. The grep patterns, Python functions for anomaly detection, and regex patterns are all copy-paste ready with specific, concrete examples. | 3 / 3 |
Workflow Clarity | Steps are numbered and sequenced, but the workflow lacks explicit validation checkpoints. For a read-only analysis skill, this is less critical, but the 'Perform result verification' constraint is mentioned without explaining how to verify results. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is inline in one file. The external references at the end are appropriate, but the Examples section is empty placeholders, and some detailed patterns could be split into separate reference files. | 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 |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
c033769
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.