Menú
Validate a YARA-L rule's syntax against the Google SecOps MCP server and self-correct any errors.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
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.
Take a source SIEM rule and format its content for readability, then insert it into a YARA-L rule template.
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.
| name | migration_helper_validate |
| description | Validate a YARA-L rule's syntax against the Google SecOps MCP server and self-correct any errors. |
Uses the Google SecOps MCP server integration to validate the syntax of a migrated YARA-L 2.0 rule, iteratively fixing errors.
/migration_helper_validate <rule_name> (where <rule_name> is the name of the rule directory, i.e., rules/<rule_name>/<rule_name>.yaral).Your task is to use the <rule_name>.yaral file to validate the YARA-L 2.0 Google SecOps syntax using the MCP SecOps server tool validate_rule.
rules/<rule_name>/<rule_name>.yaral.validate_rule tool in the MCP SecOps server to validate the YARA-L 2.0 Google SecOps syntax. Do not consider .tf files or config files.