sigma-rule-search

Search the SigmaHQ rule repository and convert detection rules to SIEM query languages.

1|Updated Aug 6, 2026
One-click install
npx skills add https://github.com/agtktID/indagis-agent --skill sigma-rule-search-agtktid
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sigma-rule-search
Source: https://github.com/agtktID/indagis-agent/tree/main/skills/security/sigma-rule-search
Command: npx skills add https://github.com/agtktID/indagis-agent --skill sigma-rule-search-agtktid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing detection rules from scratch is slow and error-prone, and analysts often don't know whether existing Sigma coverage exists for a technique, tool, or log source before investing effort. This Skill searches the SigmaHQ/sigma repository by keyword, MITRE ATT&CK technique, or log source, then converts matched rules into a target SIEM's native query syntax. ## Core Features & Use Cases - Repository-wide rule search: Query SigmaHQ/sigma via the GitHub CLI by keyword, ATT&CK technique tag (e.g. attack.t1055), or logsource fields, with a local-clone grep fallback when gh is unavailable. - Rule inspection: Fetch full rule content to review title, logsource, detection logic, false positives, and severity level before recommending it. - SIEM conversion: Convert matched rules to Splunk SPL, Elasticsearch/Lucene, KQL, and other backends using sigma-cli with the appropriate pipeline. - Use Case: A threat hunter asks whether a Sigma rule exists for Mimikatz LSASS access; the Skill finds the stable rule, confirms it requires Sysmon Event ID 10, and converts it to a Splunk SPL query ready for deployment review. ## Quick Start Search SigmaHQ for a Sigma rule covering Mimikatz LSASS access and convert the best stable match to a Splunk query.

Frequently Asked Questions about sigma-rule-search

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I search Sigma rules by MITRE ATT&CK technique?▼

Search SigmaHQ/sigma with the GitHub CLI using the technique tag, for example: gh search code --repo SigmaHQ/sigma "attack.t1055". Sigma rules declare ATT&CK mappings in their tags field, so the attack.tNNNN string matches directly.

How to convert a Sigma rule to Splunk SPL?▼

Install sigma-cli and the Splunk backend plugin, then run sigma convert -t splunk -p sysmon <rule.yml>. Choose the pipeline matching your log normalization, since a wrong pipeline produces queries with field names that don't exist in your index.

Does GitHub code search work without authentication?▼

No, GitHub's code search API rejects unauthenticated requests, so gh must be authenticated via gh auth login. As a fallback, clone the SigmaHQ/sigma repo locally and search with grep or ripgrep.

Why does sigma convert produce an empty or wrong query?▼

A mismatched backend or pipeline combination can silently emit an empty query or one with incorrect field names, since sigma convert does not error on wrong pipelines. Verify the output field names against your actual index schema and confirm the command exited 0 with non-empty output.

Should I use deprecated or unsupported Sigma rules?▼

No, rules under deprecated/ and unsupported/ paths are kept only for reference and backward compatibility, not active detection use. Filter them out of search results and recommend stable rules/ or rules-emerging-threats/ content instead.