siem-rule-generator
Siem Rule Generator - Auto-activating skill for Security Advanced. Triggers on: siem rule generator, siem rule generator Part of the Security Advanced skill category.
36
3%
Does it follow best practices?
Impact
99%
1.01xAverage 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/siem-rule-generator/SKILL.mdQuality
Discovery
7%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 extremely weak across all dimensions. It reads as an auto-generated placeholder with no meaningful content—just the skill name repeated as trigger terms and a category label. It provides no concrete actions, no natural user keywords, and no guidance on when Claude should select this skill.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates SIEM detection rules, correlation queries, and alert configurations for platforms like Splunk, Elastic SIEM, Microsoft Sentinel, and QRadar.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create detection rules, write SIEM queries, build Sigma rules, set up security alerts, or generate threat detection logic.'
Include natural keywords users would actually say, such as 'detection rule', 'Sigma rule', 'Splunk query', 'security alert', 'correlation rule', 'threat detection', 'log analysis rule', and specific SIEM platform names.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. It only states 'Siem Rule Generator' as a name but does not describe what specific actions it performs (e.g., creating detection rules, writing SIEM queries, generating Sigma rules). The language is entirely abstract. | 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. The 'Triggers on' line is just the skill name repeated, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'siem rule generator' repeated twice. It lacks natural keywords users would say such as 'detection rule', 'Sigma', 'Splunk query', 'alert rule', 'correlation rule', 'YARA', 'threat detection', or specific SIEM platform names. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'SIEM rule' is somewhat specific to a security domain niche, which provides some distinctiveness. However, the description is so vague that it could overlap with any security-related skill, and the lack of specificity about what types of SIEM rules or platforms reduces its distinctiveness. | 2 / 3 |
Total | 5 / 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 placeholder that provides absolutely no actionable content about SIEM rule generation. It contains only generic boilerplate text that repeats the skill name without any actual rules, syntax examples, detection patterns, or platform-specific guidance. It would be entirely useless for helping Claude generate SIEM rules.
Suggestions
Add concrete SIEM rule examples in at least one common format (e.g., Sigma, Splunk SPL, Elastic KQL, or Suricata rules) with executable, copy-paste-ready syntax.
Define a clear workflow for rule creation: identify threat/use case → select log sources → write detection logic → validate rule syntax → test against sample data → tune for false positives.
Include specific detection pattern templates for common threats (e.g., brute force, lateral movement, data exfiltration) with field mappings and threshold values.
Remove all generic boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actual technical content about SIEM rule structure, common pitfalls, and validation approaches.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It repeats 'siem rule generator' numerous times without providing any actual guidance, techniques, or content that Claude doesn't already know. Every section is generic boilerplate. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No code examples, no rule syntax, no specific commands, no detection logic patterns, no SIEM platform references. The skill describes what it claims to do rather than actually instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequencing, no validation checkpoints. The 'Capabilities' section vaguely mentions 'step-by-step guidance' and 'validates outputs' but provides neither. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic placeholder with no meaningful structure. There are no references to detailed files, no navigation to related resources, and the sections that exist contain no real content worth organizing. | 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
3076d78
- 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.