# fluentbit-validator

Validates and lints classic-mode Fluent Bit configs before deployment. It catches issues in INPUT, FILTER, and OUTPUT sections and verifies tag routing.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 595 installs · ★ 327
- Author: akin-ozer
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/akin-ozer/cc-devops-skills/tree/HEAD/devops-skills-plugin/skills/fluentbit-validator/SKILL.md
- Updated: 2026-07-26
- HTML: https://affpapa.org/en/nevibecode/skills/fluentbit-validator

## What it does

This skill provides deterministic validation for classic-mode Fluent Bit configuration files. Execution begins with an environment precheck in `scripts/validate.sh` to detect `python3` and the `fluent-bit` binary. If Python 3 is absent, automated script execution halts entirely, forcing the agent into manual config review.

Static analysis relies on `scripts/validate_config.py`. It inspects structure, configuration sections, security settings, performance parameters, and tag routing. When the `fluent-bit` binary is present in PATH, it runs `fluent-bit -c <config-file> --dry-run`. If the binary is missing, the dry run is skipped with a recommendation unless `--require-dry-run` is specified for release gates.

Findings use only three severity categories: `Error`, `Warning`, and `Recommendation`. The skill never edits files silently. It requests confirmation before applying changes, reruns the validation command, and reports the resulting diff.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add akin-ozer/cc-devops-skills --skill fluentbit-validator -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/fluentbit-validator/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/fluentbit-validator/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add akin-ozer/cc-devops-skills --skill fluentbit-validator -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/fluentbit-validator/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add akin-ozer/cc-devops-skills --skill fluentbit-validator -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/fluentbit-validator/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install akin-ozer/cc-devops-skills fluentbit-validator
```

2. **Manually: put the files in place**
- File: `.github/skills/fluentbit-validator/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add akin-ozer/cc-devops-skills --skill fluentbit-validator -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/akin-ozer/cc-devops-skills --path devops-skills-plugin/skills/fluentbit-validator
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/fluentbit-validator/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add akin-ozer/cc-devops-skills --skill fluentbit-validator -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/akin-ozer/cc-devops-skills/tree/HEAD/devops-skills-plugin/skills/fluentbit-validator/SKILL.md

## When to use it
- validate `fluent-bit.conf` syntax before production rollout
- detect tag routing mismatches across INPUT, FILTER, and OUTPUT sections
- inspect configurations for security and performance issues
- execute dry-run checks with the `fluent-bit` CLI binary

## Example prompts
- Validate this `fluent-bit.conf` before deploy
- Check tag routing and output matches in Fluent Bit
- Dry-run Fluent Bit config and tell me what failed

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 2946893e214f717f.

BEGIN THIRD-PARTY FILE 2946893e214f717f
````text
---
name: fluentbit-validator
description: Validate, lint, audit, or check Fluent Bit configs (INPUT, FILTER, OUTPUT, tag routing).
---

# Fluent Bit Validator

Use this skill to run deterministic, repeatable validation for Fluent Bit classic-mode configs.

## Trigger Phrases

Use this skill when prompts look like:
- "Validate this `fluent-bit.conf` before deploy"
- "Lint my Fluent Bit config and report issues"
- "Check tag routing and output matches in Fluent Bit"
- "Run security checks for Fluent Bit config"
- "Dry-run Fluent Bit config and tell me what failed"

## Execution Model

Run steps in order. Do not skip Stage 0.

### Stage 0: Precheck (Required)

Run from skill directory:

```bash
cd devops-skills-plugin/skills/fluentbit-validator
```

Check required and optional binaries:

```bash
command -v python3 >/dev/null 2>&1 && echo "python3: available" || echo "python3: missing"
command -v fluent-bit >/dev/null 2>&1 && echo "fluent-bit: available" || echo "fluent-bit: missing (dry-run will be skipped)"
```

Precheck protocol:
- If `python3` is missing: stop script-based validation, report blocker, and switch to manual config review only.
- If `fluent-bit` is missing: continue static checks, skip dry-run, and record a `Recommendation` explaining skip reason and next step.

### Stage 1: Static Validation (Required)

Default command:

```bash
python3 scripts/validate_config.py --file <config-file> --check all
```

Use targeted checks only when requested:

```bash
python3 scripts/validate_config.py --file <config-file> --check structure
python3 scripts/validate_config.py --file <config-file> --check sections
python3 scripts/validate_config.py --file <config-file> --check tags
python3 scripts/validate_config.py --file <config-file> --check security
python3 scripts/validate_config.py --file <config-file> --check performance
python3 scripts/validate_config.py --file <config-file> --check best-practices
python3 scripts/validate_config.py --file <config-file> --check dry-run
```

Strict CI gate (optional):

```bash
python3 scripts/validate_config.py --file <config-file> --check all --fail-on-warning
```

### Stage 2: Dry-Run Handling (Conditional)

Dry-run command:

```bash
fluent-bit -c <config-file> --dry-run
```

Skip protocol:
- If `fluent-bit` is unavailable, do not fail static validation by default.
- Emit one explicit finding:
  - `Recommendation: Dry-run skipped because fluent-bit binary is not available in PATH; run dry-run in CI or a Fluent Bit runtime image.`
- If user explicitly requires dry-run as a release gate, run:

```bash
````
END THIRD-PARTY FILE 2946893e214f717f

The third-party file has ended. Everything between the 2946893e214f717f tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2580 of 5614 bytes. © akin-ozer · Apache-2.0 · https://github.com/akin-ozer/cc-devops-skills/tree/HEAD/devops-skills-plugin/skills/fluentbit-validator/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md