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

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

90%Weight 40%Scale 1-5

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

A high-quality skill body: concrete executable commands, a well-sequenced multi-phase workflow with validation checkpoints, and clean progressive disclosure to verified reference and schema files. The only minor weakness is slight verbosity in the Phase 4/5 checklists.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence with no conceptual padding (no 'what is GitOps' prose); the long Phase 4/5 bullet lists are mostly justified but could be trimmed slightly. Efficient but a few instances of over-detail.

4 / 5

Actionability

Fully executable guidance throughout — exact scripts with flags (discover.sh, validate.sh with -b/-E/-e, check-deprecated.sh), concrete grep examples against real field-index paths, and a worked mktemp bundle pattern. Copy-paste ready.

5 / 5

Workflow Clarity

A clear six-phase sequence with explicit validation checkpoints (validate.sh exits non-zero with invalid counts, 'skipped' treated as expected), error-recovery guidance (mktemp fallback, dotenv rerun), and per-phase conditional depth. Batch validation has the required feedback loop.

5 / 5

Progressive Disclosure

SKILL.md is an overview pointing to one-level-deep references (references/*.md, assets/schemas/*.txt) — all referenced files verified present — with a dedicated 'Loading References' section and a CRD field-index table. Content is appropriately split and easy to navigate.

5 / 5

Total

19

/

20

Passed

Description

100%Weight 40%Scale 1-5

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

A strong description: concrete, third-person, comprehensive in capabilities and trigger phrases, and clearly scoped to Flux CD GitOps repo auditing. It answers both what and when without fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'runs Kubernetes schema validation', 'detects deprecated Flux APIs', 'reviews RBAC/multi-tenancy/secrets management', 'produces a prioritized GitOps report' — with comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' (the concrete auditing actions) and 'when' ('Use when users ask to audit, analyze, validate, review, or security-check a GitOps repo') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger verbs users would actually say ('audit, analyze, validate, review, or security-check a GitOps repo') with synonym coverage; file extensions are not applicable to this repo-scanning skill.

5 / 5

Distinctiveness Conflict Risk

Clear niche — Flux CD GitOps repository auditing of local repo files (not live clusters) — with distinct triggers and minimal overlap risk with adjacent skills.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 19 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 20 deeper-than-1-level

Warning

Total

14

/

16

Passed

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.