Menu
Take a source SIEM rule and format its content for readability, then insert it into a YARA-L rule template.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | migration_helper_format |
| description | Take a source SIEM rule and format its content for readability, then insert it into a YARA-L rule template. |
Formats a source rule from a legacy SIEM and inserts it into a specified YARA-L template file.
SOURCE RULE metadata section of an initialized YARA-L template file./migration_helper_format <migrating_rule_path> <new_rule_name> (where <new_rule_name> points to the target YARA-L file, i.e., rules/<new_rule_name>/<new_rule_name>.yaral).Your task is to take the rule content provided in <migrating_rule_path> and insert it into the template structure of the target rule file <new_rule_name> (usually rules/<new_rule_name>/<new_rule_name>.yaral).
<original formated source rule> inside the target rule file and replace it with the newly formatted source rule content.Author rule notes, parameters, dependencies, tuning, and testing sections for a YARA-L rule.
Extract unstructured legacy rules from a raw text file and structure them into valid JSON.
Generate a raw sample log entry in the original source format that will trigger the migrated YARA-L rule.
Migrate a source rule section in a YARA-L file into YARA-L 2.0, adhering to precise Google SecOps schemas.
Initialize a new YARA-L rule directory structure and YARA-L rule file from the template.
Full orchestration workflow to migrate a custom SIEM rule to YARA-L, running all sub-steps sequentially.