log-analysis-security
Log Analysis Security - Auto-activating skill for Security Advanced. Triggers on: log analysis security, log analysis security Part of the Security Advanced skill category.
33
0%
Does it follow best practices?
Impact
93%
0.98xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/04-security-advanced/log-analysis-security/SKILL.mdQuality
Discovery
0%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 essentially a placeholder with no substantive content. It names a broad domain ('Log Analysis Security') but provides zero concrete actions, no natural trigger terms beyond the skill name repeated, and no guidance on when to use it. It would be nearly impossible for Claude to correctly select this skill from a pool of similar options.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Parses server and application logs to detect security anomalies, identify unauthorized access attempts, correlate suspicious events, and generate threat summaries.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about analyzing security logs, detecting intrusions, reviewing audit trails, investigating suspicious log entries, or parsing syslog/auth.log/access.log files.'
Remove the redundant duplicate trigger term and instead include diverse natural keywords users might say, such as 'security logs', 'audit logs', 'threat detection', 'log forensics', 'suspicious activity', 'access logs'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. It merely states 'Log Analysis Security' without describing what the skill actually does—no mention of parsing logs, detecting threats, identifying anomalies, correlating events, or any other specific capability. | 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 'log analysis security' repeated twice. There are no natural variations a user might say such as 'security logs', 'audit logs', 'suspicious activity', 'intrusion detection', 'SIEM', 'log parsing', or 'threat detection'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic—'log analysis security' could overlap with general security skills, log parsing skills, monitoring skills, or any security-related skill. There is nothing to distinguish it from other security or log-related skills. | 1 / 3 |
Total | 4 / 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 actual content. It consists entirely of meta-descriptions about what the skill supposedly does without providing any actionable guidance on log analysis security—no specific log formats, analysis techniques, tools, commands, detection patterns, or security frameworks. It would provide zero value to Claude when loaded into context.
Suggestions
Replace the entire body with concrete log analysis techniques: specific log formats (syslog, Windows Event Logs, CloudTrail), common attack patterns to detect (brute force, lateral movement, privilege escalation), and executable code/commands for parsing and analyzing logs.
Add actionable examples with real log entries showing suspicious patterns and the specific grep/jq/SIEM queries to detect them.
Include a clear workflow for log analysis: collection → normalization → baseline → anomaly detection → investigation → reporting, with validation steps at each stage.
Add references to specific tools (Splunk queries, ELK stack configurations, YARA rules) with copy-paste ready configurations rather than abstract capability claims.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains what the skill does in abstract terms without providing any actual knowledge or instructions that Claude doesn't already know. Every section is padded boilerplate. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No code, no commands, no specific techniques, no log formats, no analysis methods, no tool references. The content only describes what it claims to do without actually doing it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or sequences of any kind. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no links to related files, and no structured navigation to deeper content. | 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
c8a915c
- 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.