CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

git-ai-archaeology

Git-history archaeology of a repository's AI coding harness (Copilot, Claude Code, Codex, Cursor, MCP, skills, agents, hooks). Use to date when each AI config appeared, trace how it spread, churned or was abandoned across modules, measure AI-assisted commits over time, or derive maturity phases. Not for auditing the current config or generic git stats.

Quality

96%

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

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

An exceptionally well-constructed operational skill: executable verified commands, per-step completion checkpoints, a classification-correction feedback loop, and a closing checklist, with the interpretive detail correctly offloaded to a single real reference file. The only weakness is minor overlap between step 5 and the reading grid on the trailer caveat, which keeps conciseness just off the top anchor.

DimensionReasoningScore

Conciseness

The body is dense and operational — script-specific semantics like "files older than the window take their first commit in the window as creation date" and "exits non-zero without writing" earn their tokens — but step 5's trailer-as-lower-bound caveat restates reading-grid rows, a minor instance that could be trimmed rather than the every-token-earns-its-place top anchor.

4 / 5

Actionability

Every command is copy-paste ready and verified against the actual bundle — "python3 -I ${CLAUDE_SKILL_DIR}/scripts/harness_archaeology.py --repo {repo_path} --out {out} --ref {ref} [...]", the ls-files/grep pipeline for missed files, and the correction flags --extra-glob/--exclude-glob all exist in the script's argparse, and common cases are covered.

5 / 5

Workflow Clarity

Six sequenced steps each end in an explicit "Done when" checkpoint, step 3 is a full validate-then-fix-then-rerun feedback loop for classification errors ("Rerun with --extra-glob ... or --exclude-glob"), and the closing six-item validation checklist covers the whole run; the workflow is read-only, so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

The ~55-line body stays an overview-plus-workflow with one clearly signaled, one-level-deep reference — "[the reading grid](references/reading-grid.md)", verified to exist and holding the 12-indicator interpretation table — while the script is properly invoked via ${CLAUDE_SKILL_DIR}/scripts/, making content 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.

The description is a model example of the form: concrete actions, an explicit 'Use to' trigger clause with a negative boundary, and the exact tool names a user would mention. Every dimension sits at the top anchor with no padding or over-claiming.

DimensionReasoningScore

Specificity

Four distinct concrete actions — "date when each AI config appeared", "trace how it spread, churned or was abandoned across modules", "measure AI-assisted commits over time", "derive maturity phases" — with no vague filler, matching the comprehensive-coverage anchor rather than the minor-gaps anchor below it.

5 / 5

Completeness

The what is explicit ("Git-history archaeology of a repository's AI coding harness") and the when is an explicit "Use to..." clause enumerating concrete triggers, capped by a negative boundary ("Not for auditing the current config or generic git stats") — both questions answered with concrete trigger phrases.

5 / 5

Trigger Term Quality

Names the exact vocabulary a user would say — "Copilot, Claude Code, Codex, Cursor, MCP, skills, agents, hooks" — alongside natural phrases like "git-history" and "AI-assisted commits"; this is comprehensive natural-term coverage including tool synonyms, not jargon.

5 / 5

Distinctiveness Conflict Risk

"Not for auditing the current config or generic git stats" explicitly disambiguates from config-audit and generic git-stats skills, and the named-tool harness-history niche is distinct, so conflict risk is minimal.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

FlorianBruniaux/claude-code-ultimate-guide

Path

examples/skills/git-ai-archaeology/SKILL.md

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.