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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill log-analysis-securityOverall
score
17%
Does it follow best practices?
Validation for skill structure
Activation
0%This description is essentially a placeholder with no substantive content. It fails on all dimensions by providing no concrete actions, no natural trigger terms, no explicit usage guidance, and nothing to distinguish it from other security-related skills. The repeated trigger term and boilerplate category reference provide zero value for skill selection.
Suggestions
Add specific capabilities: describe what the skill actually does (e.g., 'Parses server logs to identify security threats, detects anomalous access patterns, flags potential intrusions, and generates security incident reports').
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when analyzing access logs, investigating security incidents, checking for unauthorized access, or reviewing authentication failures').
Specify the types of logs or security scenarios covered (e.g., 'auth logs, web server logs, firewall logs, failed login attempts, privilege escalation') to distinguish from other security skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only states it's an 'auto-activating skill' without describing what it actually does - no verbs like 'analyze', 'detect', 'parse', or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no capabilities listed) and the 'when' is only a redundant trigger phrase. There's no explicit 'Use when...' clause or meaningful guidance for skill selection. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'log analysis security' repeated twice, which is overly generic and technical. Missing natural user phrases like 'check logs for threats', 'security audit', 'suspicious activity', 'intrusion detection', etc. | 1 / 3 |
Distinctiveness Conflict Risk | Extremely generic - 'Security Advanced' and 'log analysis security' could overlap with numerous security-related skills. No specific file types, attack patterns, log formats, or unique identifiers to distinguish it. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%This skill content is entirely meta-description with no substantive guidance. It describes what the skill claims to do without providing any actual instructions, code, techniques, or workflows for log analysis security. The content would be useless for helping Claude perform any real log analysis security task.
Suggestions
Add concrete, executable examples of log analysis techniques (e.g., parsing auth logs for failed login patterns, detecting privilege escalation in syslog)
Include specific commands or code for common log analysis tools (grep patterns, awk scripts, SIEM queries, Python log parsing)
Define a clear workflow for security log investigation: collection -> normalization -> pattern detection -> alerting -> validation
Replace generic capability claims with actual actionable guidance - show don't tell
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are vague filler that Claude doesn't need to be told. | 1 / 3 |
Actionability | There is zero concrete guidance, no code, no commands, no specific techniques for log analysis security. The entire content describes what the skill supposedly does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, sequences, or validation checkpoints for any log analysis security task. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no structure pointing to actual detailed materials. References to 'Related Skills' and tags provide no navigable links or useful organization. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.