CtrlK
BlogDocsLog inGet started
Tessl Logo

commit-history

List recent git commits linked to agent sessions, optionally filtered by branch or repo. Use when the user asks "show agent commits", "what has the agent shipped", "list linked commits", or wants commits with their session context.

65

Quality

79%

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 ./plugin/skills/commit-history/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 compact, well-structured read-only skill with concrete tooling examples, a clear sequenced workflow, and a useful anti-pattern. Small gains possible by tightening the rationale prose and converting See-also entries to real links.

Suggestions

Trim the "Why" section to a single line or fold its empty-result note into the Workflow step to improve token efficiency.

Convert the "See also" entries (commit-context, recall) into markdown links so cross-skill navigation is explicit.

Optionally show the full memory_commits argument object in Quick start (branch/repo/limit) so the example mirrors the parsed-filter contract.

DimensionReasoningScore

Conciseness

The body is lean with well-scoped sections and a concrete quick-start example; the short "Why" block is the only mild over-explanation that could be trimmed, keeping it just below the leanest anchor.

4 / 5

Actionability

Gives a concrete memory_commits invocation, expected output, a precise rendering spec, and an executable WRONG/RIGHT URL-encoding correction, with only minor gaps in full copy-paste completeness.

4 / 5

Workflow Clarity

A clear four-step sequence with defaults/caps, a checklist, and empty-result handling; this read-only skill needs no validation loop, so it sits at clear-sequence rather than the explicit-validation anchor.

4 / 5

Progressive Disclosure

Well-organized sections with a clearly signaled one-level reference (../_shared/TROUBLESHOOTING.md); the See-also entries are plain backtick names rather than links, a minor organization gap.

4 / 5

Total

16

/

20

Passed

Description

83%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, concrete description with explicit what/when guidance and natural trigger phrases. Minor room to broaden trigger synonyms and tighten distinctiveness from generic git-log requests.

DimensionReasoningScore

Specificity

"List recent git commits linked to agent sessions, optionally filtered by branch or repo" names the domain plus several concrete capabilities (list, branch/repo filtering, session linkage), landing above the 1-2-action midpoint but short of comprehensive multi-action coverage.

4 / 5

Completeness

Explicitly answers both what ("List recent git commits linked to agent sessions, optionally filtered by branch or repo") and when ("Use when the user asks...") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Provides several natural phrases users would say ("show agent commits", "what has the agent shipped", "list linked commits"), but a few common synonyms like "recent commits" or "git log" are absent.

4 / 5

Distinctiveness Conflict Risk

The agent-session-linked commit niche plus distinct triggers ("what has the agent shipped") make it mostly distinct, with minor overlap risk against general git-log skills.

4 / 5

Total

17

/

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.

Validation15 / 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
rohitg00/agentmemory
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.