canton-network-repos
Canton Network, DAML, and Splice repository knowledge. Use when working with Canton participants, DAML smart contracts, Splice applications, LF version compatibility, or package ID mismatches. Triggers on Canton, DAML, Splice, decentralized-canton-sync, or LF version queries.
78
66%
Does it follow best practices?
Impact
98%
2.08xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/0xbigboss/claude-code/canton-network-repos/SKILL.mdQuality
Discovery
89%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 a solid skill description with excellent trigger terms and completeness, clearly targeting a very specific technical domain. Its main weakness is that it describes knowledge areas rather than concrete actions the skill performs, making it read more like a topic list than a capability description. The explicit 'Use when' and 'Triggers on' clauses are well-structured and effective.
Suggestions
Replace 'repository knowledge' with specific actions like 'Diagnoses LF version compatibility issues, resolves package ID mismatches, guides Canton participant configuration, and assists with DAML smart contract development.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Canton Network, DAML, Splice) and mentions some specific areas like 'LF version compatibility' and 'package ID mismatches', but it primarily describes knowledge areas rather than listing concrete actions the skill performs (e.g., 'resolve package ID mismatches', 'configure Canton participants'). | 2 / 3 |
Completeness | Clearly answers both 'what' (Canton Network, DAML, and Splice repository knowledge) and 'when' with an explicit 'Use when...' clause and a 'Triggers on...' clause listing specific trigger conditions. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'Canton', 'DAML', 'Splice', 'decentralized-canton-sync', 'LF version', 'package ID mismatches', 'Canton participants', 'DAML smart contracts'. These are terms users working in this domain would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Canton Network, DAML, Splice, and decentralized-canton-sync are highly specific domain terms that are very unlikely to conflict with other skills. This occupies a clear, narrow niche. | 3 / 3 |
Total | 11 / 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 contains highly actionable and well-researched content about the Canton/DAML/Splice ecosystem with verified build instructions and concrete troubleshooting guidance. However, it is severely over-long for a SKILL.md, inlining extensive reference material (directory trees, source code excerpts, version tables) that should be split into separate files. The workflow sections would benefit from explicit validation checkpoints between steps.
Suggestions
Split reference material (directory trees, version tables, Scala/Haskell code excerpts, enterprise vs community comparison) into separate files like REFERENCE.md, VERSION-MATRIX.md, and link to them from a concise SKILL.md overview.
Add explicit validation checkpoints in the LF 2.2 build workflow, e.g., 'Verify damlc supports 2.2: `daml damlc --help | grep 2.2`' between config changes and build steps.
Remove or drastically condense the LanguageVersion.scala and Options.hs excerpts — Claude doesn't need the source code inlined; a one-line summary of what each controls with the file path is sufficient.
Trim the Repository Details section to essential paths only, moving full directory trees to a separate STRUCTURE.md reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines, including extensive inline details like Scala source code snippets, Haskell parser definitions, directory trees, and version tables that could be in separate reference files. It explains repository structures and version histories in exhaustive detail rather than providing concise, actionable guidance. Much of this (e.g., the full LanguageVersion.scala excerpt, directory trees) is reference material that bloats the main skill file. | 1 / 3 |
Actionability | The skill provides highly concrete, executable guidance: specific bash commands for building, exact file paths to edit, precise code changes (e.g., editing CantonDependencies.scala, daml.yaml), and specific troubleshooting steps with causes and fixes. The build instructions are copy-paste ready with verified results. | 3 / 3 |
Workflow Clarity | The 'Building with LF 2.2' section has a clear numbered sequence (steps 1-5), but lacks explicit validation checkpoints between steps. There's no 'verify this worked before proceeding' between editing config files and building. The troubleshooting section helps but is separate from the workflow rather than integrated as validation steps. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no bundle files to offload detailed reference material. The directory trees, version mapping tables, Scala/Haskell code excerpts, and enterprise vs community comparison tables should be in separate reference files. Everything is inlined in a single massive SKILL.md with no layered navigation structure. | 1 / 3 |
Total | 7 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
aa009ea
- 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.