agentic-jujutsu
Quantum-resistant, self-learning version control for AI agents with ReasoningBank intelligence and multi-agent coordination
44
21%
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 almost entirely composed of buzzwords and marketing-style language with no concrete actions, no trigger guidance, and no practical information about what the skill does or when to use it. It fails to communicate any actionable capability that Claude could use to select this skill appropriately. The only slightly positive aspect is that its unusual terminology makes accidental conflicts with other skills unlikely.
Suggestions
Replace buzzwords with concrete actions: describe what the skill actually does (e.g., 'Tracks file changes, creates branches, merges code, resolves conflicts').
Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks about version control, git operations, branching, or tracking changes').
Remove marketing language like 'quantum-resistant' and 'self-learning' that provides no useful selection signal, and instead describe the specific domain and operations supported.
| 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 buzzwords. | 1 / 3 |
Distinctiveness Conflict Risk | The highly specific jargon ('quantum-resistant', 'ReasoningBank intelligence') makes it unlikely to conflict with other skills, but this distinctiveness comes from meaningless buzzwords rather than clear, useful niche definition. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
35%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 product README/marketing document than an efficient skill file for Claude. It is extremely verbose with repeated patterns (the trajectory workflow is demonstrated 8+ times), includes promotional claims and performance benchmarks that don't help Claude execute tasks, and bundles everything into one massive file. The actionable content is buried under marketing language and redundancy.
Suggestions
Reduce content by 60-70%: show the trajectory workflow once in Quick Start, move API reference to a separate REFERENCE.md, and remove marketing claims (performance tables, '23x faster', 'quantum-resistant' branding).
Make code examples fully executable by removing dependencies on undefined helper functions (executeOperation, verifyDeployment, etc.) or explicitly noting they are placeholders.
Split into SKILL.md (quick start + core workflow + best practices summary ≤80 lines) with references to API_REFERENCE.md, ADVANCED_EXAMPLES.md, and TROUBLESHOOTING.md.
Add explicit validation checkpoints to the core workflow, e.g., verify trajectory was started before calling addToTrajectory, check that getSuggestion returns valid JSON before proceeding.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines. Contains extensive marketing language ('23x faster than Git', 'quantum-resistant'), redundant examples that repeat the same patterns (trajectory start/add/finalize shown 8+ times), performance comparison tables, version history, and badge-like status indicators. Much of this is promotional rather than instructional. | 1 / 3 |
Actionability | Provides concrete JavaScript code examples with executable-looking syntax, but many examples rely on undefined helper functions (executeOperation, verifyDeployment, executeTask, agent.analyze) making them not truly copy-paste ready. The API reference tables are useful but the code examples are more illustrative than fully executable. | 2 / 3 |
Workflow Clarity | The trajectory workflow (start → operations → addToTrajectory → finalize) is shown repeatedly and is clear, but there are no explicit validation checkpoints between steps. Error handling is shown in best practices but not integrated into the core workflow sequences. The troubleshooting section helps but doesn't constitute proper validation gates. | 2 / 3 |
Progressive Disclosure | References external docs (VALIDATION_FIXES_v2.3.1.md, AGENTDB_GUIDE.md, package README) which is good, but the main file itself is a monolithic wall containing everything from quick start to advanced use cases to full API reference to troubleshooting. The API reference tables and advanced use cases should be in separate files, with the SKILL.md serving as a concise overview. | 2 / 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 (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/ruflo
- Commit
398f7c2
- 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.