CtrlK
BlogDocsLog inGet started
Tessl Logo

guv

enforces engineering-governance checks before code changes that may be unnecessary, risky, architectural, or scope-widening. use when the user asks whether to refactor, clean up, redesign, choose a next development step, review a proposed implementation, evaluate architectural consistency, review a pull request, or prevent development drift. do not use as the primary implementation skill for routine debugging, bug fixes, feature coding, or language-specific coding unless a no-op, minimal-diff, or architecture-conflict judgment is needed.

74

Quality

91%

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

96%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.

The body is a tight, highly actionable governance playbook with concrete templates, a validated decision workflow, and real one-level-deep reference files. It only dips from full marks on progressive disclosure because reference navigation could be more explicit and the inline/reference split is slightly less clean.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding or explanation of concepts Claude already knows; punchy directives like "Act as a senior engineering partner, not an obedient patch generator" and tightly scoped sections mean every token earns its place.

5 / 5

Actionability

Provides copy-paste-ready guidance: a 7-item governance checklist, an A/B/C/D classification scheme, a literal option-framing template ("Recommended: ... Why: ... Acceptance test: ..."), and two fully worked examples covering the common cases.

5 / 5

Workflow Clarity

The mandatory governance check is a clear 7-step sequence with an explicit stop condition ("If no material defect, risk, or benefit exists, stop and recommend no change") and an acceptance-test checkpoint, giving genuine validation feedback loops for risky decisions.

5 / 5

Progressive Disclosure

Well-organized sections with a dedicated References list pointing to 5 real, one-level-deep reference files, but the references are listed without per-file guidance on when to consult each, and some detailed rules (option framing, classification) are inlined that could live in those reference files — minor organization gaps.

4 / 5

Total

19

/

20

Passed

Description

87%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.

The description clearly defines a governance/decision-gate skill with explicit trigger guidance and a strong non-use boundary, making it highly distinctive. It is held just below full marks on specificity and trigger-term quality only because the central verb is slightly abstract and a few natural synonyms are absent.

DimensionReasoningScore

Specificity

Enumerates many concrete scenarios ("refactor, clean up, redesign, choose a next development step, review a proposed implementation, evaluate architectural consistency, review a pull request, or prevent development drift"), but the core action "enforces engineering-governance checks" is somewhat abstract, leaving minor gaps versus fully concrete verbs.

4 / 5

Completeness

Explicitly answers both what ("enforces engineering-governance checks before code changes") and when ("use when the user asks whether to refactor, clean up, redesign...") with concrete trigger phrases, plus a "do not use" boundary clause.

5 / 5

Trigger Term Quality

Strong natural phrases users would say ("refactor", "clean up", "redesign", "review a pull request", "next development step"), but a few common synonyms/variants (e.g. "should I refactor", "tech debt", "code review") are missing, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Clear niche as a pre-change governance gate with distinct triggers, and the explicit "do not use as the primary implementation skill for routine debugging, bug fixes, feature coding" carve-out minimizes conflict with implementation skills.

5 / 5

Total

18

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
benJephunneh/guv
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.