Skip to content
Skills Library
DevOps & cloud · Building & coding

create-parser

/create-parser

Design an SC4S syslog-ng parser from raw log samples, optionally deploy it through the SC4S MCP server. Use when onboarding a new vendor or product, adding a custom log source, or creating parser logic for unsupported logs.

Licence
Apache-2.0
Last repository change
23.10.2026

Assessment and security

95/ 100Class: good
Format20 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 23.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Design an SC4S syslog-ng parser from raw log samples, optionally deploy it through the SC4S MCP server. Use when onboarding a new vendor or product, adding a custom log source, or creating parser logic for unsupported logs.

Original author description

Design an SC4S syslog-ng parser from raw log samples, optionally deploy it through the SC4S MCP server. Use when onboarding a new vendor or product, adding a custom log source, or creating parser logic for unsupported logs.

How it works

  1. 1. Collect requirements and samples
  2. 2. Gather parser knowledge
  3. 3. Design the parser
  4. 4. Optionally deploy
  5. 5. Verify event routing
Original SKILL.md headings · 82 lines, 883 words
SKILL.md preview
---
name: create-parser
description: Design an SC4S syslog-ng parser from raw log samples, optionally deploy it through the SC4S MCP server. Use when onboarding a new vendor or product, adding a custom log source, or creating parser logic for unsupported logs.
---

# Create SC4S Parser

Guide the operator through collecting representative logs, designing an SC4S parser, optionally deploying it, and verifying the resulting event routing.

## 1. Collect requirements and samples

Ask once for all missing information:

- Full positive log lines. Prefer at least three examples covering different event types or layouts; require at least one.
- Vendor, product, and device or software version. Offer inferred values for confirmation when unknown.
- Desired Splunk index and sourcetype. Offer a conventional value for confirmation when unknown.
- Whether the parser should only route events or also extract named values, which values matter, and the exact expected value for each supplied sample.
- How the final event should appear in Splunk: preserve only the message body, preserve a reconstructed header plus the message, preserve RFC5424 structured data, replace the body with normalized key/value text, or replace it with JSON. Explain that this choice controls the SC4S template, may not reproduce the original wire bytes, and is separate from Splunk search-time field definitions.
- When the original message must be preserved, whether extracted values should remain internal to SC4S or be sent as indexed HEC fields.

Do not proceed until at least one complete positive log, vendor, product, index, sourcetype, and desired final event format are known or explicitly confirmed. If only one positive example is available, continue but state that filter confidence is limited and request additional examples before production rollout.

## 2. Gather parser knowledge

Read `parser-guide.md` next to this file before designing the parser. It is the bundled baseline for SC4S parser structure, filters, rewrites, templates, and deployment layout.

When the SC4S repository lookup tools are available:

1. Read the current `sc4s://docs/creating_parsers` resource when the client exposes it. Otherwise call `search_docs(query)` for the relevant format, topic, parser method, or rewrite question.
2. Call `list_vendors` to check for existing vendor support.
3. When the vendor exists, call `list_vendor_parsers(vendor)`, then `get_parser(parser_name)` for the closest parser. Reuse conventions, not product-specific assumptions.

Use these lookups to supplement the bundled guide, not replace it.

## 3. Design the parser

Analyze every supplied sample and create a complete `.conf` file:

1. Identify RFC3164, RFC5424, CEF, LEEF, JSON, or a supported almost-syslog variant described by the guide.
2. Select the narrowest reliable application topic and filter. Prefer structured identity or program values over message-text matching. Account for the positive samples and avoid the supplied negative examples.
3. Select parser stages, namespaces, and an output template together. Keep intermediate fragments in `.tmp.*`; put only intentionally serialized values in `.values.*`; use `fields.*` only when the operator requested indexed HEC fields. Follow the bundled guide's template, namespace, and quoting rules.
4. Set the confirmed index, sourcetype, vendor, product, and template through SC4S rewrite conventions.
5. Set `<filename>` to `app-<type>-<vendor>_<product>.conf`. Normalize it to lowercase, use underscores within vendor/product identifiers, retain the `.conf` suffix, and reject path separators, traversal components, or an empty name.
6. Use only documented options for each function. Before previewing or deploying, check the parser's syntax and ensure it ends with `;`.

Show the exact `<filename>` and complete parser. Explain:

- The detected format, application topic, and filter.
- Why each positive sample should match and why negative examples should not.
- The selected index, sourcetype, `vendor_product`, template, resulting event-body format, and extracted-field delivery method.
- A compact table of every requested field and its expected value for each supplied sample.
- Any assumptions caused by missing samples or product information.

If an external metadata override is needed, recommend `$manage-sc4s-splunk-metadata`; do not refer to an undefined `sc4s:configure` command.

Ask whether the parser needs adjustments. Revise and repeat the explanation until the operator approves the content. Treat this as authoring approval only, not permission to mutate SC4S.

## 4. Optionally deploy

Ask whether to deploy the approved parser.

If `$manage-sc4s-parsers` is available, hand off the exact approved `<filename>` and parser content to that skill. Follow its read-before-write, overwrite warning, fresh confirmation, asynchronous job polling, read-back, health verification, conflict handling, and rollback-preservation workflow. Do not call `add_parser` directly from this skill, and do not reuse authoring approval as deployment confirmation.

If the management skill is unavailable or the operator prefers manual deployment:

1. Save the file as `/opt/sc4s/local/config/app_parsers/<filename>`.
2. Restart the SC4S runtime using the operator's deployment method.
3. Inspect runtime logs for syslog-ng configuration or restart errors.

Always provide the complete parser content for manual copy and preserve the approved filename exactly.

## 5. Verify event routing

After either deployment path:

1. Send a positive sample through the same transport and source path used by the device.
2. Verify in Splunk that it arrives in the confirmed index and sourcetype with the intended vendor, product, template output, and requested extracted fields.
3. When a negative example exists, send or search for it and verify that the new parser did not route it into the new sourcetype.
4. If verification fails, report the observed mismatch and return to parser design. Do not redeploy a revision without a new preview and confirmation through `$manage-sc4s-parsers`.

Use precise completion language:

- Job success, exact read-back, and healthy SC4S means **deployed and runtime-verified**.
- A correctly routed positive sample with expected metadata and fields means **end-to-end verified**.
- If the operator cannot perform the Splunk check, report deployment status and state explicitly that end-to-end verification remains outstanding.
Files in this package (3)
  • SKILL.md 6 KB
  • parser-guide.md 15 KB
  • agents/openai.yaml 1 KB

Versions

The database has no other skills named create-parser.

Database snapshot: 13.11.2026 · package version 8be35ee0f741 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90sc4s-send-syslog
    Send raw-text test syslog events to the SC4S host through its MCP tool. Use when a user wants to inject sample syslog lines for parser, routing, or ingestion testing; not for PCAP replay or arbitrary hosts.
  • 90manage-sc4s-parsers
    Safely list, inspect, deploy, update, or delete custom parsers on a running SC4S instance through MCP. Use for custom parser inventory, parser content review, parser replacement, removal, and post-change verification.
  • 100log-analysis
    Use this skill when the user asks to analyze, investigate, debug, or review a log file — or when given a path to a .log, syslog, journalctl output, or similar file. Prescribes using logzip MCP tools instead of reading the file directly.
  • 100linux-log-analysis-journalctl-syslog
    Use this skill when investigating system failures, filtering systemd-journalctl logs by service/priority, and auditing syslog.
  • 100log-diagnostic
    分析日志文件的错误模式,支持JSON、syslog、Nginx等常见格式,自动检测并输出错误聚类、频率统计和时间分布报告,用于排查问题、定位高发时段。当用户上传.log文件并要求排查错误、分析错误分布、定位高发时段,或提及错误统计、日志分析等关键词时触发。
  • 100sdl-log-parser
    Use whenever the user wants to author, edit, debug, validate, or explain a SentinelOne Singularity Data Lake (SDL) log parser, the augmented-JSON files at /logParsers/ that extract fields from raw log text before ingestion. Trigger on "SDL parser", "Skylight parser", "log…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.