agentic-jujutsu
Quantum-resistant, self-learning version control for AI agents with ReasoningBank intelligence and multi-agent coordination
49
28%
Does it follow best practices?
Impact
81%
1.26xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/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 is dominated by buzzwords and marketing-style language ('quantum-resistant', 'self-learning', 'ReasoningBank intelligence') that provide no actionable information about what the skill does or when to use it. It fails to list concrete actions, lacks natural trigger terms users would say, and has no 'Use when...' clause. The description would be nearly useless for Claude trying to select the right skill from a list.
Suggestions
Replace buzzwords with concrete actions: describe what the skill actually does (e.g., 'Tracks file changes, manages branches, resolves merge conflicts for AI agent workflows').
Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks about version control, tracking changes, branching, or coordinating multiple agents on shared code').
Remove or minimize marketing language like 'quantum-resistant' and 'self-learning' that adds no selection value, and instead focus on the specific problem domain and user scenarios this skill addresses.
| 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 capabilities listed—no verbs describing what the skill actually does. | 1 / 3 |
Completeness | The description vaguely hints at 'what' (version control) but provides no 'when' clause or explicit trigger guidance. Both dimensions are extremely weak, with no actionable information about when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The terms used ('quantum-resistant', 'ReasoningBank intelligence', 'multi-agent coordination') are technical jargon that no user would naturally say when requesting help. 'Version control' is somewhat relevant but buried among meaningless buzzwords. | 1 / 3 |
Distinctiveness Conflict Risk | The highly specific jargon ('quantum-resistant', 'ReasoningBank intelligence') ironically makes it unlikely to conflict with other skills, but only because the terms are so unusual. However, the 'version control' aspect could overlap with standard git/VCS skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable, executable code examples with a comprehensive API reference, which is its main strength. However, it is severely bloated with marketing claims, redundant examples that repeat the same trajectory pattern, and promotional content (performance benchmarks, version history, status badges) that waste tokens. The content reads more like a product README than a focused skill instruction file.
Suggestions
Reduce content by 60-70%: remove marketing language ('quantum-ready', '23x faster'), performance comparison tables, version history, and status badges. Keep only the Quick Start, one representative advanced example, and the API reference.
Move the four advanced use cases and the detailed examples section to a separate EXAMPLES.md file, referencing it from the main skill with a one-line link.
Eliminate redundant demonstrations of the same trajectory pattern (start → add → finalize appears in at least 8 separate code blocks); show it once in Quick Start and reference it thereafter.
Add explicit validation checkpoints to the core workflow, e.g., checking that startTrajectory returned a valid ID before proceeding, or verifying operations were recorded before finalizing.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines. Includes marketing language ('23x faster than Git', 'quantum-ready'), redundant examples showing the same patterns repeatedly, performance comparison tables, version history, and extensive use case examples that largely repeat the same trajectory start/add/finalize pattern. Much of this content is promotional rather than instructional. | 1 / 3 |
Actionability | The skill provides fully executable JavaScript code examples throughout, with concrete API calls, specific method signatures, and copy-paste ready snippets. The API reference tables are complete with return types, and examples cover real workflows. | 3 / 3 |
Workflow Clarity | The trajectory workflow (start → operations → 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 sequences as mandatory verification steps. | 2 / 3 |
Progressive Disclosure | References to external docs exist (VALIDATION_FIXES, AGENTDB_GUIDE, README.md) but the skill itself is monolithic with massive inline content that should be split out. The API reference tables, all advanced use cases, and the extensive examples section could be in separate files, with the SKILL.md serving as a concise overview. | 2 / 3 |
Total | 8 / 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 (646 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/claude-flow
- Commit
01070ed
- 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.