AI Agent Skills by Confluent is a collection of skills for building Kafka producers, Flink applications, and real-time data-streaming pipelines. Developers use it with coding assistants when creating applications and pipelines on Confluent. The catalogue entries are its skills, plugin, and instruction.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add confluentinc/agent-skills --skill confluent-skill-reviewergit clone --depth 1 https://github.com/confluentinc/agent-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/confluentinc/agent-skills/confluent-skill-reviewer)<a href="https://agentmods.dev/skills/confluentinc/agent-skills/confluent-skill-reviewer"><img src="https://agentmods.dev/badge/skills/confluentinc/agent-skills/confluent-skill-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/confluentinc/agent-skills/confluent-skill-reviewer"><img src="https://agentmods.dev/badge/skills/confluentinc/agent-skills/confluent-skill-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 150 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00191 | $0.03255 |
| Opus 5 | $0.00096 | $0.01628 |
| Sonnet 5 | $0.00038 | $0.00651 |
| Haiku 4.5 | $0.00019 | $0.00326 |
Grade A, and why
confluent-skill-reviewer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
confluent-skill-reviewer — audit a Confluent agent skill
Three bars every skill in this repo must clear:
- Agent Skills spec — frontmatter shape, naming rules, directory layout, token budgets (https://agentskills.io/specification).
- Confluent conventions — lazy-loaded references, anti-trigger clauses, mode-table branching, ≥90% evals, SME + DTX/DevRel sign-off (
CLAUDE.md,.github/pull_request_template.md). - Evals-as-contract —
evals/evals.jsonwith specific, verifiable expectations; fixtures kept in sync.
This skill walks an agent through a structured audit and returns a single Markdown report. It is read-only by default — never modifies the skill under review.
Pre-flight gates
Before producing any findings, confirm all three out loud (briefly):
- Scope: which mode are you in? See Mode Detection. If unclear, ask the user once.
- Target paths exist: list the
skills/<name>/directories you will audit. Stop if none. - Tool availability: run
bash skills/confluent-skill-reviewer/scripts/run_skill_validator.sh --probe(from the repo root) to check whether the externalskill-validatorbinary is installed. If absent, note it in the report and continue with native checks — do not block.
Skipping these gates is the most common source of bad reviews. The point is to be explicit about scope so the user can redirect early.
Mode detection
| User intent / signal | Mode | What to do |
|---|---|---|
"review this PR", "audit my branch", branch has uncommitted changes under skills/, a PR number is named |
PR-diff | git diff main...HEAD -- skills/ or gh pr diff <N>; review only changed skills; run all five phases, including Phase E |
"review skills/<name>", a single skill path is named, or you're invoked from inside a single skill dir |
Single-skill | Audit one skill end-to-end; run phases A–D |
| "review all skills", no scope given | Repo-wide | Iterate skills/*/, run phases A–D per skill, aggregate findings by severity |
What ships with it
24 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- evals/evals.json 7.9 KB
- evals/mock-skills/bad-frontmatter/evals/evals.json 230 B
- evals/mock-skills/bad-frontmatter/SKILL.md 220 B
- evals/mock-skills/good-skill/evals/evals.json 639 B
- evals/mock-skills/good-skill/references/auth.md 169 B
- evals/mock-skills/good-skill/references/sizing.md 202 B
- evals/mock-skills/good-skill/SKILL.md 1.1 KB
- evals/mock-skills/inlined-refs/evals/evals.json 366 B
- evals/mock-skills/inlined-refs/references/exporters.md 571 B
- evals/mock-skills/inlined-refs/SKILL.md 1.3 KB
- evals/mock-skills/leaky-data/SKILL.md 1.3 KB
- evals/mock-skills/stale-expectations/evals/evals.json 938 B
- evals/mock-skills/stale-expectations/SKILL.md 739 B
- evals/mock-skills/trigger-overlap/evals/evals.json 416 B
- evals/mock-skills/trigger-overlap/SKILL.md 598 B
- references/confluent-conventions.md 9.5 KB
- references/evals-contract.md 4.8 KB
- references/skill-validator.md 4.1 KB
- references/spec-conformance.md 5.4 KB
- references/trigger-overlap.md 4.1 KB
- scripts/check_eval_schema.py 8.9 KB runs code
- scripts/check_trigger_overlap.py 7.0 KB runs code
- scripts/run_skill_validator.sh 1.3 KB runs code
- scripts/scan_pii.py 8.7 KB runs code
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 153 lines · 191 tokens per session scan A df174dd5daec
confluent-skill-reviewer is a skill published in the GitHub repository confluentinc/agent-skills (56 stars, last pushed 9d ago), licensed Apache-2.0. It adds 191 tokens to every session and 3,255 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
agent-watchdog
Use when asked to watch, babysit, audit, review, compare, or fix another agent's work from a Codex session ID, Claude Code session/transcript, chat/thread link, PR, branch, log, or pasted run summary. Monitor until the other agent is done or blocked, reconstruct what the user asked, independently investigate the same…
agent-design-best-practices
Best practices for designing Claude Code agent files (.claude/agents/.md). This skill should be used when writing or reviewing agent markdown files to ensure proper design with focused domains, correct tool access, reusable definitions, and separation of capabilities from lifecycle. Combines Anthropic's official…
graphify-dotnet
Use graphify-dotnet to generate codebase knowledge graphs, architecture snapshots, and exportable repository maps from .NET or polyglot source trees, with optional AI-enriched semantic relationships. USE FOR: graphify commands; graph JSON, HTML, SVG, Cypher, Markdown, and Obsidian exports; repository map and…
map-codebase
Deep architecture report that fans out parallel inspections across different aspects of the codebase (structure, tech stack, APIs, patterns, data flow, dependencies, testing) and synthesizes findings into a comprehensive document at .turbo/codebase-map.md and .turbo/codebase-map.html. Use when the user asks to "map…
sonarqube-mcp
Provides SonarQube and SonarCloud integration patterns via the Model Context Protocol (MCP) server. Enables quality gate monitoring, issue discovery and triaging, pre-push code analysis, and rule education directly in the agent workflow. Use when the user wants to check quality gates, search for Sonar issues, analyze…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…