CtrlK
BlogDocsLog inGet started
Tessl Logo

river-channel-development

Use when planning river navigation routes or developing drainage channels. Maps nine major river systems from source to terminus, guides dredging, embankment construction, and integration into tribute transportation networks.

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

The body is well-structured and appropriately concise with a validation section covering the batch river-mapping operation. The main weakness is actionability: the development steps are high-level directives without the concrete specifics needed to execute them.

Suggestions

Add concrete specifics to the Channel Improvement and Navigation Setup steps, e.g., minimum navigable depth values, dredging technique selection criteria, and embankment specifications.

Convert the Validation section into an explicit feedback loop (verify -> identify failure -> fix -> re-verify) so it is clear what to do when a checkpoint fails.

Tighten the Overview to avoid restating the title; let the section headings carry the structure.

DimensionReasoningScore

Conciseness

The body is lean and avoids explaining concepts Claude already knows, but the Overview section restates the title's purpose with mild redundancy that could be trimmed.

4 / 5

Actionability

Steps name concrete actions ("Dredge obstructed sections," "Build embankments") but lack specific executable detail such as target depths, dredging methods, or criteria for bypass channels, leaving guidance incomplete.

3 / 5

Workflow Clarity

A clear five-step sequence is present and a Validation section provides checkpoints for the batch operation, but there is no explicit error-recovery feedback loop describing what to do when validation fails.

4 / 5

Progressive Disclosure

For a single-purpose skill near the 50-line mark, the content is well-organized into clearly labeled sections with no need for external references, satisfying the simple-skill exception.

5 / 5

Total

16

/

20

Passed

Description

92%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.

The description is strong: it concisely states both the trigger conditions and the concrete capabilities in third person, with a distinctive niche. Keyword synonyms are the only minor gap.

DimensionReasoningScore

Specificity

Lists multiple concrete actions—"Maps nine major river systems from source to terminus," "guides dredging, embankment construction, and integration into tribute transportation networks"—giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both what (maps nine river systems, guides dredging/embankment/integration) and when ("Use when planning river navigation routes or developing drainage channels") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases like "planning river navigation routes" and "developing drainage channels" match what a user would say, but synonyms and broader variations (e.g., waterways, canal construction) are limited.

4 / 5

Distinctiveness Conflict Risk

River channel development is a clear, narrow niche with distinct triggers; minimal overlap risk with other skills.

5 / 5

Total

19

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
baojie/shiji-kb
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.