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

Content

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 excellent organization. Its main weakness is the lack of explicit multi-step workflows with validation checkpoints for complex operations like rebasing or splitting. The pitfalls section is particularly strong, providing clear do/don't patterns that prevent common mistakes.

Suggestions

Add a multi-step workflow example for a common complex operation (e.g., rebasing a branch) that includes a checkpoint, validation, and recovery steps if something goes wrong.

Integrate the jj-checkpoint script into a concrete workflow pattern showing: checkpoint → risky operation → verify → rollback if needed.

DimensionReasoningScore

Conciseness

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

3 / 3

Actionability

Commands are concrete, copy-paste ready bash examples with flags explained inline. The pitfalls section provides both correct (✅) and incorrect (❌) examples side-by-side, making guidance immediately executable. Revset patterns, recovery commands, and script references are all specific and actionable.

3 / 3

Workflow Clarity

Individual commands and pitfalls are clearly documented, but there are no explicit multi-step workflows with validation checkpoints. The recovery section shows op log → op restore but lacks a feedback loop. For operations like rebase or split that can go wrong, there's no 'validate then proceed' pattern. The checkpoint script is mentioned but not integrated into a workflow.

2 / 3

Progressive Disclosure

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

3 / 3

Total

11

/

12

Passed

Description

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 provides explicit 'when to use' guidance. Its main weakness is that the capabilities are described more as topic areas than concrete actions, using 'expert guidance' and 'covers' rather than action verbs. The strong domain-specific trigger terms and clear distinctiveness compensate well.

Suggestions

Replace 'Expert guidance for' and 'Covers' with concrete action verbs, e.g., 'Writes revset expressions, debugs change evolution issues, configures git remote interop, 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 JJ version control covering commands, templates, evolog, operations log, git interop) and 'when' ('Use when working with JJ, whatever the subject') with explicit trigger guidance.

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, making this highly distinctive. The terms 'revsets', 'evolog', 'change evolution' are unique to JJ and unlikely to conflict with generic git skills or other tools.

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.