CtrlK
BlogDocsLog inGet started
Tessl Logo

working-with-jj

Expert guidance for using JJ (Jujutsu) version control system. Use when working with JJ, whatever the subject. Operations, revsets, templates, debugging change evolution, etc. Covers JJ commands, template system, evolog, operations log, and interoperability with git remotes.

90

1.26x
Quality

88%

Does it follow best practices?

Impact

90%

1.26x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Discovery

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a solid skill description that clearly identifies its niche (JJ/Jujutsu VCS) and includes an explicit 'Use when' clause with good trigger term coverage. Its main weakness is that it describes topic areas rather than concrete actions, using 'expert guidance' and 'covers' instead of action verbs. The distinctiveness is excellent due to JJ being a specific tool with unique terminology.

Suggestions

Replace 'Expert guidance for using' and 'Covers' with concrete action verbs, e.g., 'Writes revset expressions, debugs change evolution issues, configures git remote interoperability, interprets evolog and operations log output.'

DimensionReasoningScore

Specificity

Names the domain (JJ/Jujutsu version control) and lists several areas like commands, template system, evolog, operations log, and git remote interoperability, but these are more topic areas than concrete actions. It says 'expert guidance' rather than specific verbs like 'debug change evolution conflicts' or 'write revset expressions'.

2 / 3

Completeness

Clearly answers both what ('Expert guidance for using JJ version control system' covering commands, templates, evolog, etc.) and when ('Use when working with JJ, whatever the subject'). The 'Use when...' clause is explicit and broad, with topic examples provided.

3 / 3

Trigger Term Quality

Includes strong natural trigger terms: 'JJ', 'Jujutsu', 'revsets', 'templates', 'evolog', 'operations log', 'git remotes', 'change evolution'. These cover the terms a user working with JJ would naturally use in their queries.

3 / 3

Distinctiveness Conflict Risk

JJ/Jujutsu is a very specific version control system with distinctive terminology (revsets, evolog, change evolution). This is unlikely to conflict with generic git skills or other VCS skills due to the specific tool name and JJ-specific concepts mentioned.

3 / 3

Total

11

/

12

Passed

Implementation

87%

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

This is a high-quality skill that efficiently covers JJ version control with concrete, executable examples and well-organized progressive disclosure. The common pitfalls section with version-specific notes is particularly valuable. The main weakness is the lack of explicit validation/feedback loops for multi-step workflows like rebasing chains or batch operations, though the recovery section partially compensates.

Suggestions

Add a brief validation/feedback loop for multi-step operations like rebase chains (e.g., 'after rebase, run jj log -r to verify the new graph structure before proceeding')

DimensionReasoningScore

Conciseness

The content is lean and efficient throughout. It assumes Claude's competence with version control concepts, avoids explaining what VCS is, and every section delivers actionable information without padding. The core principles section is appropriately terse.

3 / 3

Actionability

Nearly every section provides concrete, copy-paste-ready commands with clear syntax. The essential commands, revset reference, and common pitfalls all include executable examples with ✅/❌ annotations showing correct vs incorrect usage.

3 / 3

Workflow Clarity

The recovery workflow (op log → op restore) is clear but brief. The skill lacks explicit validation checkpoints for multi-step operations like rebasing or splitting. The common pitfalls section helps prevent errors but doesn't provide feedback loops for complex operations like batch description transforms.

2 / 3

Progressive Disclosure

Content is well-structured with clear sections progressing from core principles to essential commands to pitfalls to references. External references are clearly signaled one level deep (references/revsets.md, references/command-syntax.md, references/batch-operations.md, scripts/), and the self-documenting `jj help` commands are a smart addition.

3 / 3

Total

11

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
YPares/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.