CtrlK
BlogDocsLog inGet started
Tessl Logo

flood-control-water-management

Use when managing large-scale water control projects, river dredging, or land drainage. Follows Yu the Great's methodology for surveying terrain, selecting transportation, developing waterways, reclaiming flooded land, and coordinating regional labor.

75

Quality

92%

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

85%

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

The body is concise, well-sequenced, and includes explicit validation checkpoints, making the workflow clear. The main weakness is actionability: steps describe what to do rather than giving concrete, executable procedures or measurable criteria.

Suggestions

Add concrete, executable detail to each step — e.g. specific survey tools/measurements, dredging depth/channel-width targets, or crop-soil matching rules — so guidance is actionable rather than declarative.

Tighten the Validation section into explicit pass/fail criteria with measurable thresholds (e.g. 'channel depth ≥ X', 'food surplus/deficit within Y%') rather than confirmations.

Consider bundling the per-terrain transportation and crop-selection tables into a reference file if the skill grows, to preserve the lean overview.

DimensionReasoningScore

Conciseness

The body is lean and well-organized with no padding or explanations of concepts Claude already knows; every section earns its place. Not below 3 because there is no redundant context to trim.

3 / 3

Actionability

Steps are listed but the guidance is declarative rather than executable — e.g. 'Conduct land surveys using measuring tools', 'Dredge rivers to create proper channels', 'Adjust supplies based on surplus and deficit areas' describe outcomes without specific procedures, thresholds, or tools. Not 3 because there are no concrete, copy-ready instructions; not 1 because the actions are named and domain-specific.

2 / 3

Workflow Clarity

A clear five-step sequence (Survey → Transportation → Waterway Development → Land Reclamation → Resource Management) is followed by an explicit Validation section with checkpoints confirming each prior phase. Not below 3 because validation steps are present and the order is unambiguous.

3 / 3

Progressive Disclosure

The skill is a single self-contained file under 50 lines with well-organized sections and no bundle files (references/scripts/assets absent), so the simple-skill allowance applies. Not below 3 because the content is appropriately organized for a skill of this size.

3 / 3

Total

11

/

12

Passed

Description

100%

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 strong description: it states concrete capabilities, provides an explicit 'Use when' trigger with natural project terms, and occupies a distinct niche. Both the 'what' and 'when' are clearly answered.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'surveying terrain, selecting transportation, developing waterways, reclaiming flooded land, and coordinating regional labor' plus 'river dredging' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

It explicitly answers both 'what' (the listed methodology tasks) and 'when' via an explicit 'Use when managing large-scale water control projects...' clause, matching the highest anchor.

3 / 3

Trigger Term Quality

'water control projects, river dredging, or land drainage' are natural terms a user would say when they need this skill, giving good coverage of common phrasings. Not below 3 because the trigger terms are realistic and varied; the 'Yu the Great's methodology' framing is unusual but the operational terms carry it.

3 / 3

Distinctiveness Conflict Risk

Flood control / water management is a clear niche with distinct triggers unlikely to overlap with other skills, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

12

/

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.

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.