agentic-jujutsu

Quantum-resistant, self-learning version control for AI agents with ReasoningBank intelligence and multi-agent coordination

1.15x

Quality

17%

Does it follow best practices?

Impact

88%

1.15x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/agentic-jujutsu/SKILL.md

Quality

Discovery

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 description is dominated by marketing buzzwords and abstract jargon without describing any concrete actions or providing trigger guidance. It fails to tell Claude what specific tasks this skill performs or when to select it. A user asking for help with version control, commits, or branching would have no clear signal to match against this description.

Suggestions

Replace buzzwords with concrete actions the skill performs (e.g., 'Manages branches, commits changes, resolves merge conflicts, tracks file history').

Add an explicit 'Use when...' clause with natural trigger terms users would actually say (e.g., 'Use when the user asks about git, commits, branching, merging, or version history').

Remove or demote marketing language like 'quantum-resistant' and 'self-learning' — focus on what the skill actually does in practical terms.

Dimension	Reasoning	Score
Specificity	The description uses abstract buzzwords like 'quantum-resistant', 'self-learning', and 'ReasoningBank intelligence' without describing any concrete actions. There are no specific operations listed (e.g., commit, branch, merge, diff).	1 / 3
Completeness	The description vaguely gestures at 'what' (version control) but provides no explicit 'when' clause or trigger guidance. Both the what and when are very weak — there's no 'Use when...' or equivalent.	1 / 3
Trigger Term Quality	The keywords are highly technical jargon ('quantum-resistant', 'ReasoningBank intelligence', 'multi-agent coordination') that no user would naturally say when needing version control help. 'Version control' is the only somewhat natural term, but it's buried among buzzwords.	1 / 3
Distinctiveness Conflict Risk	The heavy use of niche buzzwords like 'quantum-resistant' and 'ReasoningBank intelligence' ironically makes it somewhat distinctive, as few other skills would use these terms. However, the core concept of 'version control' is generic enough to overlap with standard git/VCS skills.	2 / 3
	Total	5 / 12 Passed

Implementation

27%

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

This skill reads more like a comprehensive product README/marketing document than a focused skill for Claude. It is extremely verbose with repeated patterns, marketing claims, and extensive inline content that should be split across multiple files. While the code examples are reasonably concrete, the sheer volume of redundant demonstrations and the lack of progressive disclosure significantly reduce its effectiveness as a skill.

Suggestions

Reduce the document to ~100 lines: keep Quick Start, one Core Capabilities section with the trajectory pattern, the API reference tables, and move Advanced Use Cases, Best Practices, Troubleshooting, and Examples into separate bundle files with clear references.

Remove marketing language and performance comparison tables — Claude doesn't need to be sold on the tool, it needs to know how to use it.

Consolidate the 8+ repetitions of the startTrajectory/addToTrajectory/finalizeTrajectory pattern into a single canonical example with a brief note that this pattern applies across all use cases.

Add explicit validation checkpoints to the workflow (e.g., verify trajectory ID is valid before adding operations, check suggestion confidence before executing recommended operations).

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~400+ lines. Contains extensive marketing language ('23x faster than Git', 'quantum-resistant'), redundant examples (4 advanced use cases that repeat the same trajectory pattern), performance comparison tables, version history, and explanations of concepts Claude doesn't need. The same startTrajectory/addToTrajectory/finalizeTrajectory pattern is demonstrated at least 8 times across the document.	1 / 3
Actionability	Code examples are concrete and appear executable with specific API calls and realistic patterns. However, many examples include undefined helper functions (executeOperation, verifyDeployment, executeTask, agent.analyze) making them not truly copy-paste ready, and some use cases are more illustrative than actionable.	2 / 3
Workflow Clarity	The trajectory workflow (start → operate → add → finalize) is clear and repeated many times. However, there are no explicit validation checkpoints between steps, no verification that operations succeeded before finalizing, and the error handling section shows catch blocks but doesn't integrate validation into the core workflow sequence.	2 / 3
Progressive Disclosure	The document is a monolithic wall of text with no bundle files to support it. References to external docs (VALIDATION_FIXES_v2.3.1.md, AGENTDB_GUIDE.md) exist but no bundle files are provided. The API reference tables, 4 advanced use cases, best practices, troubleshooting, and multiple examples could all be split into separate files, but instead everything is inlined into one massive document.	1 / 3
	Total	6 / 12 Passed

Validation

81%

Warnings & errors only

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

Validation — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (649 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: ruvnet/agentic-flow
Commit: 6a06854

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

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.