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 provides a concise mental model, actionable commands, clear agent-specific rules with safety constraints, and excellent progressive disclosure to reference files. The content is perfectly calibrated for an AI agent — it emphasizes non-interactive operation, verification after mutations, and recovery workflows.

DimensionReasoningScore

Conciseness

The content is lean and efficient throughout. It assumes Claude's competence, avoids explaining basic concepts, and every section earns its place. The mental model section conveys critical jj-specific concepts concisely with bold key phrases and minimal prose.

3 / 3

Actionability

Provides fully executable commands and code throughout — the core workflow, pushing changes, recovery, and essential commands table are all copy-paste ready. The agent configuration is a complete TOML block with launch instructions. No pseudocode or vague directions.

3 / 3

Workflow Clarity

The core workflow is clearly sequenced (describe → code → new → repeat) with explicit verification steps ('jj st && jj diff' after changes, 'Verify after mutations' in agent rules). The non-linear work section provides a clear branching workflow. Recovery steps are explicit with feedback loops (undo, op log, op restore).

3 / 3

Progressive Disclosure

Excellent progressive disclosure with a clear topics table at the top, inline '→ Deep dive' links throughout the body, and a comprehensive reference index at the bottom. All references are one level deep and clearly signaled. The main file 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, provides comprehensive trigger terms covering both common VCS operations and jj-specific concepts, and explicitly defines activation boundaries to prevent conflicts with git-related skills. The negative trigger condition ('Do NOT activate for plain git repos without .jj/') 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 clearly identifies the tool (Jujutsu/jj) and its relationship to Git.

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: includes both 'jj' and 'jujutsu', '.jj/ directory', and a comprehensive list of VCS operation keywords (commit, push, pull, branch, rebase, etc.) plus jj-specific terms like 'bookmark', 'revset', 'fileset', 'change ID', and 'workspaces'.

3 / 3

Distinctiveness Conflict Risk

Exceptionally distinct — explicitly differentiates itself from plain git by stating 'Do NOT activate for plain git repos without .jj/' and specifies the unique activation trigger (.jj/ directory). This makes it very unlikely to conflict with a standard git 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.

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.