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.

100

1.23x
Quality

100%

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

100%

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

This is an exceptionally well-crafted skill file. It efficiently conveys jj's unique mental model and provides concrete, executable guidance while maintaining excellent structure through progressive disclosure to reference files. The Agent Rules section is particularly strong, providing non-negotiable safety constraints with clear rationale, and the Common Mistakes table proactively addresses failure modes.

DimensionReasoningScore

Conciseness

The content is lean and efficient throughout. It assumes Claude's competence, avoids explaining basic VCS concepts, and every section earns its place — the mental model section conveys genuinely novel jj-specific concepts (working copy as commit, change IDs vs commit IDs) rather than things Claude would already know.

3 / 3

Actionability

Provides fully executable commands throughout — core workflow, pushing, recovery, and essential commands table all contain copy-paste ready bash commands. The agent configuration section includes a complete TOML config file. No pseudocode; all examples are concrete and specific.

3 / 3

Workflow Clarity

The core workflow is clearly sequenced (describe → code → new → repeat) with explicit validation checkpoints ('jj st && jj diff' after changes, 'verify after mutations' rule). The Agent Rules section provides explicit constraints for destructive operations, and the Common Mistakes table serves as a pre-flight checklist. Recovery workflows are clearly documented with feedback loops (undo → op log → op restore).

3 / 3

Progressive Disclosure

Excellent progressive disclosure with a clear Topics table at the top for quick navigation, inline '→ Deep dive' links at contextually appropriate points, and a comprehensive Reference Index organized by category at the bottom. All references are one level deep and clearly signaled. The main SKILL.md stays concise while pointing to 13+ reference files for detailed content.

3 / 3

Total

12

/

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.

This is an excellent skill description that clearly identifies the tool (Jujutsu/jj), provides comprehensive trigger terms covering both general VCS operations and jj-specific concepts, and explicitly defines activation boundaries to prevent conflicts with git-related skills. The explicit negative condition ('Do NOT activate for plain git repos') is a particularly strong design choice for disambiguation.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions and concepts: commit, push, pull, branch, bookmark, rebase, squash, merge, diff, log, status, working copy, change ID, revset, fileset, template, configuration, workspaces. Also specifies the tool clearly as 'Jujutsu (jj) — the Git-compatible version control system.'

3 / 3

Completeness

Clearly answers both 'what' (VCS operations in jj-managed projects with a comprehensive list) and 'when' (explicit activation criteria: .jj/ directory present OR jj/jujutsu explicitly mentioned, with a clear negative condition for plain git repos).

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'jj', 'jujutsu', '.jj/', plus a comprehensive list of VCS operation keywords (commit, push, pull, branch, rebase, diff, log, status, etc.) that users would naturally use. Also includes jj-specific terms like 'bookmark', 'revset', 'fileset', 'change ID', and 'workspaces'.

3 / 3

Distinctiveness Conflict Risk

Exceptionally distinctive with explicit boundary conditions: 'Activate ONLY when a .jj/ directory is present' and 'Do NOT activate for plain git repos without .jj/'. This directly addresses the most likely conflict (with a git skill) and creates a clear, unambiguous niche.

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.

Validation11 / 11 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.