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
88%
Does it follow best practices?
Impact
90%
1.26xAverage score across 3 eval scenarios
Passed
No known issues
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 provides good trigger term coverage with domain-specific terminology. The main weakness is that it leans toward listing topic areas rather than concrete actions, using 'expert guidance' as a catch-all rather than specifying what operations it performs. The 'Use when' clause is present and broad, which is appropriate for a specialized tool skill.
Suggestions
Replace 'Expert guidance for using' with specific action verbs like 'Writes revset expressions, debugs change evolution, configures templates, manages operations log, and handles git remote interoperability for the JJ (Jujutsu) version control system.'
| Dimension | Reasoning | Score |
|---|---|---|
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 with distinct terminology (revsets, evolog, change evolution). This is unlikely to conflict with generic git skills or other VCS skills due to the highly specific trigger terms. | 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 excellent actionability and organization. The content is concise, assumes Claude's intelligence, and provides concrete executable examples throughout. The main weakness is the lack of explicit multi-step workflows with validation checkpoints for potentially destructive operations like rebase or batch description transforms.
Suggestions
Add an explicit workflow with validation steps for common multi-step operations (e.g., rebase workflow: checkpoint → rebase → verify with jj log → undo if wrong)
Integrate the jj-checkpoint script into a concrete workflow pattern showing how to use it before risky operations and how to recover if things go wrong
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It assumes Claude's competence with version control concepts, never explains 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 common pitfalls section is especially strong, showing both correct and incorrect patterns with specific version annotations. The revset reference, essential commands, and recovery sections are all immediately executable. | 3 / 3 |
Workflow Clarity | While individual commands are clear, there are no explicit multi-step workflows with validation checkpoints. The recovery section shows op log + op restore but doesn't frame it as a validation/feedback loop. The checkpoint script is mentioned but not integrated into a workflow. For operations like rebase or split that can go wrong, there's no explicit 'verify then proceed' pattern. | 2 / 3 |
Progressive Disclosure | The skill is well-structured with clear sections progressing from core principles to essential commands to pitfalls to recovery. References to deeper content (references/revsets.md, references/command-syntax.md, references/batch-operations.md, scripts/) are clearly signaled and one level deep. The self-documenting `jj help` references 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- YPares/agent-skills
- Commit
d2b7dff
- 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.