CtrlK
BlogDocsLog inGet started
Tessl Logo

jj

Jujutsu (jj) — the Git-compatible version control system. Activate ONLY when a .jj/ directory is present in the project or when jj/jujutsu is explicitly mentioned. Do NOT activate for plain git repos without .jj/. Use for any VCS operations in jj-managed projects: commit, push, pull, branch, bookmark, rebase, squash, merge, diff, log, status, working copy, change ID, revset, fileset, template, configuration, workspaces.

95

1.23x
Quality

92%

Does it follow best practices?

Impact

100%

1.23x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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 well-structured, highly actionable overview: tight mental model, executable commands, explicit agent safety rules with validation, and clean progressive disclosure to a verified reference bundle. The only weakness is a time-sensitive version pin and minor redundancy between the Agent Rules and Common Mistakes tables.

Suggestions

Move the "Target version: jj 0.36+" pin into a dedicated compatibility/version section or remove it, since time-sensitive version numbers penalize conciseness when placed outside a deprecated/old-patterns section.

Consolidate the Agent Rules and Common Mistakes tables — they overlap (e.g., missing -m, unquoted revsets, un-set bookmarks) — to remove redundancy and tighten the token budget.

Consider pulling the most critical single recovery command (jj undo) into the Core Workflow so the daily loop visibly includes an escape hatch for failed mutations.

DimensionReasoningScore

Conciseness

The body is mostly lean and avoids explaining concepts Claude already knows, but pins a time-sensitive version ("Target version: jj 0.36+") outside any deprecated section, and the Common Mistakes table overlaps somewhat with the Agent Rules, so it could be tightened.

2 / 3

Actionability

Concrete, copy-paste-ready commands throughout (jj describe -m, jj new -m, jj squash, jj bookmark set feat -r @, jj git push -b feat) plus an executable TOML config block provide fully executable guidance.

3 / 3

Workflow Clarity

The Core Workflow gives a clear describe -> code -> new -> repeat loop, and Agent Rule 3 ("Verify after mutations. Run jj st after squash, abandon, rebase...") plus the Recovery section provide explicit validation checkpoints and undo feedback loops for destructive ops.

3 / 3

Progressive Disclosure

A Topics table maps needs to one-level-deep deep-dive references, and a Reference Index organizes them by category; all referenced files (bookmarks.md, revsets.md, conflicts.md, etc.) exist in references/, so navigation is clear and well-signaled.

3 / 3

Total

11

/

12

Passed

Description

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.

The description is specific, trigger-rich, and self-disambiguating: it names concrete capabilities, gives explicit activation conditions, and actively prevents conflict with plain-git skills. It is written in third-person/imperative voice with no over-claims.

DimensionReasoningScore

Specificity

Lists many concrete actions explicitly — "commit, push, pull, branch, bookmark, rebase, squash, merge, diff, log, status, working copy, change ID, revset, fileset, template, configuration, workspaces" — matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers what (the listed VCS operations) and when ("Activate ONLY when a .jj/ directory is present... or when jj/jujutsu is explicitly mentioned", "Use for any VCS operations in jj-managed projects"), with an explicit Use-when trigger clause.

3 / 3

Trigger Term Quality

Natural VCS terms a user would actually say (commit, push, pull, rebase, squash, merge, diff, log, status) plus "jj/jujutsu" give good coverage of common phrasings.

3 / 3

Distinctiveness Conflict Risk

Clear niche (jj-managed repos with .jj/) reinforced by "Do NOT activate for plain git repos without .jj/", making it unlikely to trigger for the wrong skill.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
joshuadavidthomas/agent-skills
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.