gitops-repo-audit
Audit Flux CD GitOps repositories for structure, security, API compliance, and best practices. Use this skill whenever the user asks to audit, analyze, review, validate, or check a GitOps repository. Also use it when users mention Flux repo structure, GitOps best practices, manifest validation, deprecated APIs, security review, or repository organization — even if they don't explicitly say "audit".
Install with Tessl CLI
npx tessl i github:fluxcd/agent-skills --skill gitops-repo-audit100
Does it follow best practices?
Validation for skill structure
Discovery
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 hits all the key criteria. It provides specific audit dimensions, comprehensive trigger terms covering both explicit and implicit user requests, clear 'what' and 'when' guidance, and targets a distinct technical niche (Flux CD GitOps) that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'audit...for structure, security, API compliance, and best practices' - these are distinct, concrete audit dimensions rather than vague language. | 3 / 3 |
Completeness | Clearly answers both what ('Audit Flux CD GitOps repositories for structure, security, API compliance, and best practices') AND when ('Use this skill whenever...') with explicit trigger guidance including the helpful note about implicit triggers. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'audit, analyze, review, validate, check', 'Flux repo structure', 'GitOps best practices', 'manifest validation', 'deprecated APIs', 'security review', 'repository organization'. Includes both explicit and implicit trigger scenarios. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Flux CD GitOps repositories specifically. The combination of 'Flux CD', 'GitOps', and audit-specific terminology creates a clear, distinct domain unlikely to conflict with general code review or other repository skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exceptionally well-crafted skill that demonstrates best practices across all dimensions. It provides a clear multi-phase workflow with executable scripts, explicit validation checkpoints, and well-organized progressive disclosure to reference materials. The edge cases section shows thoughtful consideration of real-world scenarios without being verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, assuming Claude's competence with Kubernetes and GitOps concepts. It provides direct instructions without explaining what Flux CD, GitOps, or YAML are. Every section serves a clear purpose. | 3 / 3 |
Actionability | Provides fully executable bash commands for each phase (discover.sh, validate.sh, check-deprecated.sh), specific file paths to check, and concrete guidance like checking for the `reconcile.fluxcd.io/watch: "Enabled"` label. The CRD reference table with exact apiVersions and schema paths is highly actionable. | 3 / 3 |
Workflow Clarity | The six-phase workflow is clearly sequenced with explicit validation steps (Phase 2 manifest validation, Phase 3 API compliance checks). Each phase has numbered steps, and the skill includes feedback loops like 'If deprecated APIs are found, read api-migration.md' and conditional depth based on user request scope. | 3 / 3 |
Progressive Disclosure | Excellent structure with a clear overview workflow and well-signaled one-level-deep references to detailed materials (repo-patterns.md, best-practices.md, security-audit.md, api-migration.md). The 'Loading References' section explicitly tells when to load each file. Content is appropriately split between the main skill and reference files. | 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.