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 strong skill description for a niche domain. It excels at trigger term coverage and completeness with explicit 'Use when' and 'Triggers on' clauses, and occupies a very distinct niche. The main weakness is that it describes knowledge areas rather than concrete actions the skill performs, making it read more like a topic reference than an actionable capability.
Suggestions
Replace 'repository knowledge' with specific concrete actions, e.g., 'Resolves package ID mismatches, configures Canton participants, debugs LF version compatibility issues, and develops DAML smart contracts.'
| 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, LF version compatibility, package ID mismatches) and 'when' (explicit 'Use when...' clause and 'Triggers on...' clause specifying exact 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 | Highly distinctive niche covering Canton Network, DAML, and Splice — these are very specific technologies unlikely to overlap with other skills. The explicit trigger terms like 'decentralized-canton-sync' and 'LF version' further reduce conflict risk. | 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 is highly actionable with concrete, executable guidance for building Canton Network components, but suffers significantly from verbosity and poor progressive disclosure. It packs extensive reference material (directory trees, source code snippets, version tables, feature comparisons) into a single monolithic file that would consume substantial context window. The content would benefit greatly from being split into a concise overview SKILL.md with detailed references in separate bundle files.
Suggestions
Split the detailed directory trees, version mapping tables, and source code snippets into separate reference files (e.g., DIRECTORY_STRUCTURE.md, VERSION_MATRIX.md, LF_VERSIONS.md) and reference them from a concise SKILL.md overview.
Remove explanatory content Claude can infer, such as the enterprise vs community comparison table, the package ID derivation explanation, and the repeated 'verified' annotations—keep only the actionable build steps and troubleshooting.
Add explicit validation checkpoints in the LF 2.2 build workflow, e.g., 'After step 3, verify with: daml damlc --help | grep 2.2' before proceeding to build.
Condense the troubleshooting section into the relevant workflow steps rather than a separate section, so validation and error recovery are inline with the process.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~250+ lines, including extensive directory trees, Scala/Haskell source snippets, version tables with historical context, and detailed explanations of LF version internals. Much of this (e.g., explaining package ID derivation, enterprise vs community feature tables, full directory listings) is reference material that Claude could infer or that should be in separate files. The 'Verified Results (2025-12-24)' section and repeated emphasis on 'verified working' adds unnecessary padding. | 1 / 3 |
Actionability | The skill provides fully executable commands for building Canton and Splice, specific file paths to edit, exact configuration values to change, concrete bash/perl commands, and precise troubleshooting steps with causes and fixes. The LF 2.2 build instructions are copy-paste ready with specific file edits and build commands. | 3 / 3 |
Workflow Clarity | The 'Building with LF 2.2' section has a clear numbered sequence of steps, 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 gates. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no bundle files to offload detailed content. The version mapping tables, full directory trees, Scala source code snippets, and enterprise vs community comparison tables should all be in separate reference files. The External References section links to external sites but doesn't organize the skill's own content across files for progressive discovery. | 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
83d60e9
- 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.