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.

2.08x

Quality

65%

Does it follow best practices?

Impact

98%

2.08x

Average score across 3 eval scenarios

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./data/skills-md/0xbigboss/claude-code/canton-network-repos/SKILL.md

Quality

Content

61%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A technically rich, actionable reference with concrete build commands and a well-organized structure. Its main weaknesses are duplicated LF 2.2 build instructions, inline time-sensitive version detail, and the absence of explicit validation checkpoints in the batch build workflows.

Suggestions

Merge the two LF 2.2 build sections ('Building with LF 2.2' and 'Fully Open-Source LF 2.2 Build') into a single canonical procedure to remove redundancy.

Add an explicit validation checkpoint to the build workflow, e.g. 'Verify: run `daml damlc --help` to confirm 2.2 is supported, then rebuild and check that the produced DAR reports LF 2.2' before declaring success.

Move volatile version-specific snapshots and dates into a dedicated, clearly-marked version-mapping/deprecated section so the stable guidance stays lean.

Dimension	Reasoning	Score
Conciseness	The body is a dense, mostly-earning technical reference, but the two near-duplicate LF 2.2 build sections and inline time-sensitive version snapshots/dates (e.g. '3.3.0-snapshot.20250502', 'October 3, 2025') not isolated in a deprecated section add padding.	3 / 5
Actionability	Concrete, mostly copy-paste-ready commands are provided (sbt assembly, nix-shell daml build, perl -pi edits) with exact file paths and config snippets, covering the common build/upgrade cases with only minor gaps.	4 / 5
Workflow Clarity	The 'Building with LF 2.2' section has a clear numbered sequence, but batch operations (perl -pi across **/daml.yaml) and destructive edits lack an explicit verify/validate checkpoint, capping it at 3 per the batch-operations guideline.	3 / 5
Progressive Disclosure	No bundle files exist; the ~300-line doc is well-sectioned with clear headers and an External References block, though the detailed repo listings and build steps are inline content that could be split into reference files.	4 / 5
	Total	14 / 20 Passed

Description

68%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-targeted description with explicit trigger guidance and a distinct niche, weakened mainly by an abstract 'what' clause ('repository knowledge') that lists no concrete actions. Trigger-term coverage is good but could add a few more synonyms.

Suggestions

Replace the abstract 'repository knowledge' phrasing with concrete actions, e.g. 'Build, debug, and trace version compatibility across Canton, DAML, and Splice repositories.'

Add a few more natural trigger synonyms users might say, such as 'DAML-LF', 'Amulet', or 'Canton Coin'.

Tighten the redundant trigger list — 'Triggers on Canton, DAML, Splice...' largely restates the preceding 'Use when working with...' clause.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Canton Network, DAML, and Splice repository knowledge') but the only 'action' is the abstract noun 'knowledge' — no concrete verbs like build, debug, or extract, matching the 'names domain but actions minimal/generic' anchor.	2 / 5
Completeness	Both 'what' (repository knowledge — somewhat vague) and an explicit, specific 'when' ('Use when working with... Triggers on...') are present; the strong trigger guidance lifts it above 3, but the vague 'what' keeps it below 5.	4 / 5
Trigger Term Quality	Strong natural keywords users would say (Canton, DAML, Splice, LF version, package ID mismatches, decentralized-canton-sync) with some synonyms, but missing a few variants (e.g., DAML-LF, Amulet, Canton Coin) and file extensions.	4 / 5
Distinctiveness Conflict Risk	Canton, DAML, Splice, and decentralized-canton-sync form a clear, specialized niche with distinct triggers and minimal overlap risk against generic skills.	5 / 5
	Total	15 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: NeverSight/skills_feed
Path: data/skills-md/0xbigboss/claude-code/canton-network-repos/SKILL.md
Commit: 2f57aec

Reviewed: about 22 hours ago

Table of Contents

Discovery Implementation Validation

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.