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
Quality
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 severely underdeveloped, consisting primarily of boilerplate metadata rather than actionable content. It fails to explain what SIEM rules the skill generates, which platforms it supports, or what user requests should trigger it. The redundant trigger terms provide no value for skill selection.
Suggestions
Add specific capabilities: 'Generates SIEM detection rules for platforms like Splunk, Microsoft Sentinel, and Elastic Security. Creates correlation rules, alert thresholds, and threat detection logic.'
Include a proper 'Use when...' clause with natural trigger terms: 'Use when the user asks about detection rules, security alerts, threat hunting queries, log correlation, or mentions specific SIEM platforms.'
Remove the redundant trigger term repetition and replace with varied natural language users would actually say when needing this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Siem Rule Generator') without describing any concrete actions. There are no specific capabilities listed like 'generates detection rules', 'creates correlation logic', or 'formats for Splunk/Sentinel'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is just a redundant repetition of the skill name rather than meaningful trigger guidance. Both components are essentially missing. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated ('siem rule generator, siem rule generator'). Missing natural user phrases like 'detection rule', 'security alert', 'Splunk query', 'Sentinel rule', 'threat detection', or 'log correlation'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'SIEM' provides some domain specificity that distinguishes it from generic security skills, but without concrete actions or specific SIEM platforms mentioned, it could still overlap with other security-related skills. | 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 content is essentially a placeholder with no actionable information. It describes the concept of SIEM rule generation without providing any actual guidance, rule syntax, examples, or workflows. A SIEM rule generator skill should include specific rule formats (Splunk SPL, Elastic Query DSL, Sigma rules), detection logic patterns, and validation steps.
Suggestions
Add concrete SIEM rule examples in at least one format (e.g., Sigma, Splunk SPL, or Elastic Query DSL) with copy-paste ready syntax
Include a workflow for rule creation: define detection logic → write rule → validate syntax → test against sample logs → deploy
Provide specific detection patterns for common threats (e.g., brute force, lateral movement, data exfiltration) with example rules
Remove generic boilerplate sections ('Capabilities', 'Example Triggers') and replace with actionable content like rule templates and field mappings
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no SIEM rule syntax, no specific commands or formats. The skill describes what it does rather than instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps for generating SIEM rules, no validation checkpoints, and no process for testing or deploying rules. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic statements with no references to detailed materials, examples, or rule templates that would be essential for SIEM rule generation. | 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
994edc4
- 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.