CtrlK
BlogDocsLog inGet started
Tessl Logo

water-management-method

Use when planning irrigation canals, flood control, or water resource management for agriculture. Applies Yu's principle of channeling over blocking (疏导优于堵塞) and includes the Zheng Guo Canal case study.

63

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./kg/ontology/ontology-v1/skus/procedural/skill_058/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 content is a well-structured, lean instruction skill with sequenced procedures and a validation section. Its main gaps are untranslated Chinese material terms and the absence of explicit feedback loops between steps.

Suggestions

Gloss or translate the Chinese-only material terms (薪柴→firewood, 竹木→bamboo/timber, 石块→stone) so the steps are executable without domain knowledge.

Insert an explicit validate→fix→retry checkpoint between steps (e.g., after surveying, confirm drainage patterns before moving to channel management).

DimensionReasoningScore

Conciseness

The body is mostly lean bullet points that assume competence (e.g., "禹抑洪水十三年,过家不入门" with no padding), with only minor generic content in "Expected Outcomes" that could be trimmed.

4 / 5

Actionability

Steps are concrete and ordered with specifics ("Map the river course from source to sea", "Calculate gradient for gravity flow", material lists), but several materials appear only in untranslated Chinese (薪柴, 竹木, 石块), a minor executability gap.

4 / 5

Workflow Clarity

Both flood-control and irrigation procedures are clearly sequenced (Step 1–3) and a dedicated Validation checklist closes the process, but there is no explicit validate→fix→retry feedback loop between steps.

4 / 5

Progressive Disclosure

It is a single well-organized file with clear section headers and no nested references; at ~70 lines it slightly exceeds the under-50-lines simple-skill threshold, keeping it just below a 5.

4 / 5

Total

16

/

20

Passed

Description

73%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 well-targeted with an explicit trigger clause and a clear, distinctive niche. Its main weakness is that the "what" is framed around historical principles rather than concrete, verb-driven capabilities.

Suggestions

Lead with concrete action verbs (e.g., "Design, plan, and sequence irrigation and flood-control projects") before the historical framing so the capability is unambiguous.

Add natural synonyms users might say (drainage, levee/dike building, canal design) to broaden trigger coverage.

DimensionReasoningScore

Specificity

"planning irrigation canals, flood control, or water resource management" names the domain and several tasks but uses a single generic verb ("planning") rather than listing concrete operations, so it is not comprehensive.

3 / 5

Completeness

It has an explicit "Use when planning irrigation canals, flood control, or water resource management" trigger and states what it does ("Applies Yu's principle... includes the Zheng Guo Canal case study"), but the "what" leans on framing rather than crisp action verbs, keeping it below a 5.

4 / 5

Trigger Term Quality

"irrigation canals, flood control, water resource management, agriculture" are natural terms a user would say, with good coverage; a few synonyms (drainage, levee/dike, canal design) are missing, so it stops short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

The niche domain (irrigation canals, flood control, Yu's principle, Zheng Guo Canal) has distinct triggers with minimal overlap risk against other skills.

5 / 5

Total

16

/

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.