CtrlK
BlogDocsLog inGet started
Tessl Logo

gitops-repo-audit

Audit and validate Flux CD GitOps repositories by scanning local repo files (not live clusters) — runs Kubernetes schema validation, detects deprecated Flux APIs, reviews RBAC/multi-tenancy/secrets management, and produces a prioritized GitOps report. Use when users ask to audit, analyze, validate, review, or security-check a GitOps repo.

75

Quality

92%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a high-quality skill with an exceptionally clear multi-phase workflow, concrete executable commands, and well-organized progressive disclosure to reference files. The actionability is excellent with specific scripts, file paths, and conditional logic. The main weakness is moderate verbosity — the inline CRD reference table and extensive edge cases section could potentially be offloaded to reference files to save tokens.

DimensionReasoningScore

Conciseness

The skill is generally efficient and avoids explaining basic concepts Claude already knows, but the CRD reference table is quite large and could be offloaded to a reference file. The edge cases section, while useful, adds significant length that could be more tightly written.

2 / 3

Actionability

Provides concrete, executable bash commands for each phase (discover.sh, validate.sh, check-deprecated.sh), specific file paths to check, exact field names to look for (e.g., `reconcile.fluxcd.io/watch: "Enabled"`), and a clear report structure with section templates. The guidance is specific and directly usable.

3 / 3

Workflow Clarity

The six-phase workflow is clearly sequenced with explicit dependencies (discovery before validation, validation before best practices assessment). Phase 2 validates manifests before deeper analysis, Phase 3 has a clear conditional branch (if deprecated APIs found → read migration guide), and the skill explicitly instructs to verify YAML against OpenAPI schemas before recommending changes — a strong validation checkpoint.

3 / 3

Progressive Disclosure

Excellent progressive disclosure with a clear overview in SKILL.md and well-signaled one-level-deep references to repo-patterns.md, best-practices.md, security-audit.md, api-migration.md, flux-api-summary.md, and flux-operator-api-summary.md. The 'Loading References' section explicitly tells when to load each file, and schema assets are clearly organized with a naming convention.

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an excellent skill description that clearly defines its scope (Flux CD GitOps repo auditing on local files), lists multiple concrete capabilities, and provides explicit trigger guidance. The scoping clarification ('not live clusters') is a nice touch that further reduces ambiguity. The description is concise yet comprehensive, hitting all the marks for an effective skill selector.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: Kubernetes schema validation, detecting deprecated Flux APIs, reviewing RBAC/multi-tenancy/secrets management, and producing a prioritized GitOps report. Also clarifies scope (local repo files, not live clusters).

3 / 3

Completeness

Clearly answers both 'what' (audit/validate Flux CD repos with schema validation, deprecated API detection, RBAC review, report generation) and 'when' (explicit 'Use when users ask to audit, analyze, validate, review, or security-check a GitOps repo').

3 / 3

Trigger Term Quality

Includes strong natural trigger terms users would say: 'audit', 'validate', 'analyze', 'review', 'security-check', 'GitOps repo', 'Flux CD'. Also includes domain-specific terms like 'RBAC', 'multi-tenancy', 'secrets management', 'Kubernetes schema' that users in this domain would naturally use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive — targets a very specific niche (Flux CD GitOps repositories, local repo scanning). The combination of Flux CD, GitOps, Kubernetes schema validation, and the explicit 'not live clusters' scoping makes it very unlikely to conflict with other skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
fluxcd/agent-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.