CtrlK
BlogDocsLog inGet started
Tessl Logo

git-history-analyzer

Performs archaeological analysis of git history to trace code evolution, identify contributors, and understand why code patterns exist. Use when you need historical context for code changes.

64

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/git-history-analyzer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

Highly actionable content built around concrete git commands, with clean section organization. The main gaps are mild verbosity from the examples/role framing and the absence of an explicitly sequenced analysis workflow.

Suggestions

Tighten the <examples> block or trim the role preamble; the concrete git commands already make the skill's purpose clear.

Express the methodology as an explicit ordered workflow (e.g., 1. broad file history, 2. blame origin tracing, 3. pattern/contributor analysis, 4. synthesize deliverables) rather than parallel responsibilities.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands and no over-explanation of git basics, but the <examples> block and "You are a Git History Analyzer" role framing add tokens that don't each earn their place.

2 / 3

Actionability

Provides specific, copy-paste-ready git commands with meaningful flags (e.g., "git blame -w -C -C -C <file>", "git log --follow --oneline -20 <file>").

3 / 3

Workflow Clarity

Core responsibilities are listed as parallel items with a methodology that gives loose ordering, but there is no explicit sequence or checkpoint structure for the end-to-end analysis.

2 / 3

Progressive Disclosure

Single-file skill with no bundle files, organized into clearly headed sections; per the simple-skills note this is well-organized enough to score 3.

3 / 3

Total

10

/

12

Passed

Description

85%

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: third-person, specific, with an explicit Use-when trigger. Its only weakness is trigger-term naturalness — the phrasing is somewhat jargon-heavy and omits everyday phrasings a user might actually say.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "trace code evolution, identify contributors, and understand why code patterns exist" — rather than vague language.

3 / 3

Completeness

Explicitly answers what ("Performs archaeological analysis...") and when ("Use when you need historical context for code changes").

3 / 3

Trigger Term Quality

Includes relevant terms ("git history", "historical context", "code changes") but leans technical and misses common natural variations like "git log" or "who wrote this code".

2 / 3

Distinctiveness Conflict Risk

Occupies a clear git-history niche with distinct triggers unlikely to collide with other skills.

3 / 3

Total

11

/

12

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository
udecode/plate
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.