agentic-jujutsu
Quantum-resistant, self-learning version control for AI agents with ReasoningBank intelligence and multi-agent coordination
47
24%
Does it follow best practices?
Impact
84%
2.62xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/agentic-jujutsu/SKILL.mdQuality
Discovery
7%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 reads like marketing copy rather than a functional skill description. It is packed with buzzwords ('quantum-resistant', 'self-learning', 'ReasoningBank intelligence') but fails to describe any concrete actions, lacks trigger terms users would naturally use, and provides no guidance on when Claude should select this skill.
Suggestions
Replace buzzwords with concrete actions the skill performs, e.g., 'Tracks file changes, manages branches, resolves merge conflicts for AI agent workflows.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about version control, git operations, branching, or tracking changes in multi-agent projects.'
Remove or minimize jargon like 'quantum-resistant' and 'ReasoningBank intelligence' unless they map to specific, user-facing capabilities that can be described concretely.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses abstract buzzwords like 'quantum-resistant', 'self-learning', and 'ReasoningBank intelligence' without listing any concrete actions. There are no specific operations described—just vague, marketing-style language. | 1 / 3 |
Completeness | There is no 'Use when...' clause or any explicit trigger guidance. The 'what' is extremely vague (no concrete actions listed), and the 'when' is entirely missing. | 1 / 3 |
Trigger Term Quality | The terms used ('quantum-resistant', 'ReasoningBank intelligence', 'multi-agent coordination') are highly technical jargon that no user would naturally say when needing version control help. 'Version control' is somewhat relevant but buried among buzzwords. | 1 / 3 |
Distinctiveness Conflict Risk | The highly specific jargon ('quantum-resistant', 'ReasoningBank intelligence') ironically makes it unlikely to conflict with other skills, but the description is so vague about actual capabilities that it's unclear what niche it truly occupies beyond generic version control. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill content is highly actionable with executable code examples but suffers severely from verbosity and poor progressive disclosure. It reads more like a comprehensive package README/marketing document than a focused skill file — it includes performance benchmarks, version history, marketing claims, and repetitive code patterns that inflate token usage without adding proportional value. The content would benefit enormously from being split into a concise overview with references to separate detail files.
Suggestions
Reduce the SKILL.md to a concise overview (~50-80 lines) covering Quick Start and the core trajectory workflow, moving API reference tables, advanced use cases, troubleshooting, and examples into separate referenced files.
Remove marketing language and performance comparison tables (e.g., '23x faster than Git', '87% auto conflict resolution') — these don't help Claude execute tasks.
Consolidate the 4 advanced use cases into a single referenced ADVANCED.md file, as they all repeat the same start→add→finalize pattern with minor variations.
Add explicit validation checkpoints to the core workflow (e.g., verify trajectory was started before adding operations, check suggestion confidence before proceeding).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines. Includes marketing language ('23x faster than Git'), redundant examples (4 advanced use cases that repeat the same trajectory pattern), performance comparison tables, version history, and extensive API reference tables that should be in separate files. Many concepts are over-explained with repetitive code patterns. | 1 / 3 |
Actionability | The skill provides fully executable JavaScript code examples throughout, with concrete method calls, specific parameters, and copy-paste ready snippets. The API reference tables clearly document method signatures and return types. | 3 / 3 |
Workflow Clarity | The trajectory workflow (start → operate → add → finalize) is consistently demonstrated across examples, but there are no explicit validation checkpoints between steps. Error handling is shown in best practices but not integrated into the core workflow as mandatory verification steps. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content with everything inlined — API reference tables, 4 advanced use cases, best practices, troubleshooting, validation rules, and multiple full examples all in one file. References to external docs exist at the bottom but the bulk content that should be in separate files (API reference, advanced use cases, examples) is all inline. No bundle files are provided to support any referenced paths. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
81%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 (663 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/ruvector
- Commit
c2089c4
- 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.