New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Fluentbit Validator

by akin-ozer in akin-ozer/cc-devops-skills

Validate, lint, audit, or check Fluent Bit configs (INPUT, FILTER, OUTPUT, tag routing).

Apache-2.0Auto-check passedDevOps & Cloud

Install Fluentbit Validator

skills CLI
$ npx skills add akin-ozer/cc-devops-skills --skill fluentbit-validator -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install akin-ozer/cc-devops-skills fluentbit-validator --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/akin-ozer/cc-devops-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/devops-skills-plugin/skills/fluentbit-validator .claude/skills/fluentbit-validator && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
fluentbit-validator
GitHub stars
319
Token cost
~1.4k tokens
SKILL.md length
509 words
Files
12 (incl. scripts)
Skills in repo
30
Repo updated
First seen
Licence
Apache-2.0

At a glance

Validate, lint, audit, or check Fluent Bit configs (INPUT, FILTER, OUTPUT, tag routing).

  • Works in 5 steps: Precheck (Required) → Static Validation (Required) → Dry-Run Handling (Conditional) → …
  • Tasks that involve Linting and formatting
  • SKILL.md covers Trigger Phrases, Execution Model, Fallback Matrix and Canonical Flows, plus 2 more sections
  • Runs Python and Shell scripts from its folder; calls python3 and bash

What it does

Fluentbit Validator is an agent skill from akin-ozer/cc-devops-skills. Validate, lint, audit, or check Fluent Bit configs (INPUT, FILTER, OUTPUT, tag routing).

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 13 other files, including scripts (for example `scripts/validate.sh`, `scripts/validate_config.py` and `tests/test_validate_config.py`).

It sits in DevOps & Cloud, covering Linting and formatting. The repository describes itself as: DevOps skills for Claude Code and Codex. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Linting and formatting

Example prompts

  • “/fluentbit-validator”

Requirements

  • Python 3
  • A Bash shell

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Precheck (Required)
  2. Static Validation (Required)
  3. Dry-Run Handling (Conditional)
  4. Reference Lookup (Optional)
  5. Report and Remediation (Required)

What it can do on your machine

Read from SKILL.md and the folder at commit 276af75. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (Python and Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • python3
    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Fluentbit Validator loads about 1.4k tokens when it runs. Until then it costs about 27 tokens; SKILL.md has 509 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~27
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from akin-ozer/cc-devops-skills at commit 276af75, republished under its Apache-2.0 licence (© akin-ozer). 509 words, ~1,404 tokens.

Download SKILL.mdSave it as .claude/skills/fluentbit-validator/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.
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
python3 scripts/validate_config.py --file <config-file> --check dry-run --require-dry-run
  • In release-gate mode, missing fluent-bit must be reported as Error.
Stage 3: Reference Lookup (Optional)

Use only when plugin/parameter behavior is unclear after local checks.

Lookup order:

  1. Context7 Fluent Bit docs.
  2. Official docs at docs.fluentbit.io.
  3. Broader web search limited to official/plugin sources.

Capture only:

  • required fields,
  • allowed values and defaults,
  • version caveats relevant to the user config.
Stage 4: Report and Remediation (Required)

Use exactly these severity labels:

  • Error
  • Warning
  • Recommendation

Do not introduce alternate labels (Info, Best Practice, Critical, etc.).

Report format:

text
Validation Report: <config-file>

Error:
- <blocking issue>

Warning:
- <non-blocking risk>

Recommendation:
- <improvement or skipped-step guidance>

Remediation flow:

  1. Present findings with file/line context when available.
  2. Ask for approval before changing user files.
  3. Apply approved changes.
  4. Re-run the same validation command(s).
  5. Return delta: what changed, what remains, and final status.

No-issue fast path:

  • If no findings exist, return a short pass summary and note whether dry-run was executed or skipped.
Show full SKILL.md (169 more words)Show less

Fallback Matrix

ConstraintBehavior
python3 missingStop scripted validator, report blocker as Error, provide manual review-only output.
fluent-bit missingContinue static checks, skip dry-run, emit one Recommendation with next step.
No network/docs accessContinue local validation, report unknown plugin details as Warning with explicit "doc lookup deferred".
User requests report-onlyDo not edit files; return findings and rerun command suggestion.

Canonical Flows

Full validation flow
bash
bash scripts/validate.sh --precheck
python3 scripts/validate_config.py --file tests/valid-basic.conf --check all
Constrained environment flow (fluent-bit unavailable)
bash
bash scripts/validate.sh --precheck
python3 scripts/validate_config.py --file tests/invalid-security-issues.conf --check all --json

Expected outcome:

  • Static findings still produced.
  • Dry-run skipped and reported under Recommendation.

Done Criteria

Work is done only when all are true:

  • Precheck was executed and binary availability was stated explicitly.
  • Validation command(s) and scope are clear and reproducible.
  • All findings use only Error, Warning, Recommendation.
  • Dry-run path is explicit: executed or skipped with reason.
  • Fallback behavior for tool/runtime constraints is documented in output.
  • If fixes were applied, validation was re-run and post-fix status was reported.

Local Assets

  • scripts/validate_config.py: main validator.
  • scripts/validate.sh: wrapper and environment precheck helper.
  • tests/*.conf: sample valid/invalid configs.
  • tests/test_validate_config.py: regression coverage for parser and severity behavior.

© akin-ozer, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 11 other files (scripts) in devops-skills-plugin/skills/fluentbit-validator of akin-ozer/cc-devops-skills.

  • SKILL.md
  • .gitignore
  • scripts/validate.sh
  • scripts/validate_config.py
  • tests/invalid-missing-required.conf
  • tests/invalid-opentelemetry.conf
  • tests/invalid-security-issues.conf
  • tests/invalid-tag-mismatch.conf
  • tests/test_validate_config.py
  • tests/valid-basic.conf
  • tests/valid-multioutput.conf
  • tests/valid-opentelemetry.conf

Open the folder on GitHubat commit 276af75

Compare with similar skills

Fluentbit Validator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Fluentbit Validator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Fluentbit Validator this skillakin-ozer/cc-devops-skills319—~1.4kAutomated safety check: PassApache-2.0
GitHub Actions CreatorFNOSP/FlyNarwhal4951 repos~2.4kAutomated safety check: PassAGPL-3.0
Megalinter Checknvuillam/npm-groovy-lint2481 repos~3.9kAutomated safety check: NotesMIT
Rtk Skillsopaco/deepwiki-rs3.1k—~1.4kAutomated safety check: PassMIT
Azure Bicep Skilltimothywarner-org/claude-code224—~2.9kAutomated safety check: PassMIT
Okfserradura/okf176—~3.2kAutomated safety check: NotesApache-2.0

Similar skills

  • GitHub Actions Creator

    FNOSP/FlyNarwhal

    A skill your agent uses when the user wants to create, generate, or set up a GitHub Actions workflow.

    495 GitHub starsUsed in 1 repo~2.4k tokens
    DevOps & CloudAuto-check passed

  • Megalinter Check

    nvuillam/npm-groovy-lint

    Collect MegaLinter lint errors for the current repository. An agent skill from nvuillam/npm-groovy-lint.

    248 GitHub starsUsed in 1 repo~3.9k tokens
    DevOps & CloudAuto-check: notes

  • Rtk Skill

    sopaco/deepwiki-rs

    A skill your agent uses when running shell commands that produce verbose output (git, test, build, lint, package managers, docker).

    3.1k GitHub stars~1.4k tokensUpdated 23 days ago
    DevOps & CloudAuto-check passed

  • Azure Bicep Skill

    timothywarner-org/claude-code

    A skill your agent uses when authoring, reviewing, or refactoring Azure Bicep code.

    224 GitHub stars~2.9k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed

  • Okf

    serradura/okf

    Be the expert on Open Knowledge Format (OKF) — portable project knowledge as a directory of markdown files with YAML frontmatter that humans and agents read from one source.

    176 GitHub stars~3.2k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check: notes

  • Session Retro

    werf/werf

    Analyze the current session for harness-worthy lessons — repeated corrections, discovered conventions, skill bugs — and turn them into concrete repo changes: docs, skills, task targets, linter…

    4.7k GitHub stars~1.6k tokensUpdated today
    DevOps & CloudAuto-check passed

More from akin-ozer/cc-devops-skills

All 30 skills in this repo

  • GitHub Actions Generator

    akin-ozer/cc-devops-skills

    Create, generate, or scaffold GitHub Actions workflows, action.yml, or .github/workflows CI/CD pipelines.

    319 GitHub stars~3.1k tokensUpdated 2 mo ago
    Auto-check passed

  • Helm Generator

    akin-ozer/cc-devops-skills

    Create, scaffold, or generate Helm charts, Chart.yaml, values.yaml, templates, helpers.

    319 GitHub stars~2.9k tokensUpdated 2 mo ago
    Auto-check passed

  • Jenkinsfile Generator

    akin-ozer/cc-devops-skills

    Generate/create/scaffold Jenkinsfile — declarative, scripted, shared library, CI/CD pipelines.

    319 GitHub stars~3.7k tokensUpdated 2 mo ago
    Auto-check passed

  • Dockerfile Validator

    akin-ozer/cc-devops-skills

    Validate, lint, audit, or scan a Dockerfile for security and best practices.

    319 GitHub stars~2.3k tokensUpdated 2 mo ago
    Auto-check passed

  • GitHub Actions Validator

    akin-ozer/cc-devops-skills

    Validate, lint, audit, fix GitHub Actions workflows (.github/workflows).

    319 GitHub stars~4.7k tokensUpdated 2 mo ago
    Auto-check passed

  • Jenkinsfile Validator

    akin-ozer/cc-devops-skills

    Validate, lint, audit, or check Jenkinsfiles and shared libraries.

    319 GitHub stars~2.7k tokensUpdated 2 mo ago
    Auto-check passed

Categories

Questions about Fluentbit Validator

What does Fluentbit Validator do?

Validate, lint, audit, or check Fluent Bit configs (INPUT, FILTER, OUTPUT, tag routing). Fluentbit Validator is an agent skill from akin-ozer/cc-devops-skills. Validate, lint, audit, or check Fluent Bit configs (INPUT, FILTER, OUTPUT, tag routing).

When should I use Fluentbit Validator?

Fluentbit Validator fits situations like: tasks that involve Linting and formatting.

How do I install Fluentbit Validator in Claude Code?

Run `npx skills add akin-ozer/cc-devops-skills --skill fluentbit-validator -a claude-code`. Or copy the skill folder (devops-skills-plugin/skills/fluentbit-validator in akin-ozer/cc-devops-skills) into .claude/skills/fluentbit-validator in your project. Claude Code loads it when a task matches its description.

How do I install Fluentbit Validator in Codex?

Run `npx skills add akin-ozer/cc-devops-skills --skill fluentbit-validator -a codex`. Or copy the skill folder (devops-skills-plugin/skills/fluentbit-validator in akin-ozer/cc-devops-skills) into .agents/skills/fluentbit-validator in your project. Codex loads it when a task matches its description.

Can I use Fluentbit Validator in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add akin-ozer/cc-devops-skills --skill fluentbit-validator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fluentbit-validator, .gemini/skills/fluentbit-validator, .github/skills/fluentbit-validator and .opencode/skills/fluentbit-validator in your project.

What does Fluentbit Validator need to run?

Going by SKILL.md and its folder, Fluentbit Validator needs Python and a shell for the scripts in its folder and the command-line tools its instructions call (python3 and bash). Our summary lists: Python 3; A Bash shell.

Does Fluentbit Validator access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Fluentbit Validator safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Fluentbit Validator use?

Fluentbit Validator is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Fluentbit Validator use?

About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Fluentbit Validator?

Skills that share tags, products or a category with Fluentbit Validator: GitHub Actions Creator (FNOSP/FlyNarwhal, 495 stars), Megalinter Check (nvuillam/npm-groovy-lint, 248 stars), Rtk Skill (sopaco/deepwiki-rs, 3.1k stars) and Azure Bicep Skill (timothywarner-org/claude-code, 224 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fluentbit Validator?

akin-ozer (a GitHub user) maintains it in akin-ozer/cc-devops-skills, which has 319 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on July 26, 2026.

Source: akin-ozer/cc-devops-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.