CtrlK
BlogDocsLog inGet started
Tessl Logo

bian-que-six-incurable-conditions

Use when screening patients before committing treatment resources. Applies Bian Que's 六不治 framework to identify six incurable conditions (arrogance, greed, poor self-care, yin-yang chaos, extreme weakness, trust in shamans over physicians).

60

Quality

69%

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_186/SKILL.md
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 content is well-structured and concise, with a usable screening workflow and explicit verification steps. The primary weakness is actionability: the decision logic is abstract pseudocode and lacks a concrete screening procedure or worked example.

Suggestions

Add a brief concrete screening procedure or worked example showing how to assess one condition against observed signs, lifting the decision framework from abstract pseudocode to executable guidance.

Add an explicit feedback/validation loop (e.g., 'if signs are ambiguous, gather collateral history before classifying as incurable') to support the screening decision.

Trim the 'Used by the legendary physician Bian Que' line from the Overview to fully eliminate over-explanation Claude already knows.

DimensionReasoningScore

Conciseness

The body is lean with one-line translations, signs, and prognoses per condition and no padding about what the framework is; only the single line 'Used by the legendary physician Bian Que' is marginally trimmable over-explanation.

4 / 5

Actionability

Each condition lists concrete observable signs to look for and the decision framework gives a clear IF/THEN rule, but the framework is presented as abstract pseudocode with no concrete screening procedure or example case, leaving key execution detail implicit.

3 / 5

Workflow Clarity

A clear sequence is present (assess all six conditions -> decline/document or proceed) and the Verification section provides three explicit checkpoints including documenting observed signs and setting expectations; minor gap is the lack of an explicit error-recovery or feedback loop.

4 / 5

Progressive Disclosure

This is a compact single-purpose skill (~57 lines) with well-organized sections and no need for external references; per the simple-skills note, the clean section structure earns full marks.

5 / 5

Total

16

/

20

Passed

Description

67%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 clearly states both purpose and trigger, and enumerates the six conditions concretely, making it distinctive. The main weakness is trigger-term naturalness — the phrasing is somewhat clinical rather than mirroring how a user would phrase a request.

Suggestions

Add more natural user-facing trigger phrases (e.g., 'when deciding whether to accept a patient for treatment' or 'when a patient case looks untreatable') alongside the clinical phrasing.

Tighten the 'when' clause to a more explicit, scenario-based trigger rather than the abstract 'before committing treatment resources'.

Consider stating the concrete screening action (e.g., 'checks the patient against six criteria') to lift specificity from listing categories to describing the action performed.

DimensionReasoningScore

Specificity

Names the domain and enumerates the six concrete conditions to identify (arrogance, greed, poor self-care, yin-yang chaos, extreme weakness, trust in shamans over physicians), but does not describe how identification is performed beyond listing the categories, leaving a minor coverage gap.

4 / 5

Completeness

Explicitly answers both 'what' (applies the 六不治 framework to identify six incurable conditions) and 'when' ('Use when screening patients before committing treatment resources'), but the 'when' trigger phrasing could be more specific to natural user requests.

4 / 5

Trigger Term Quality

Includes some relevant natural phrases ('screening patients', 'committing treatment resources') and lists the six conditions as synonyms, but misses common lay variations users would naturally say and has no file-extension-style keyword equivalent.

3 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Bian Que's 六不治 screening framework) with distinct triggers unlikely to fire for unrelated skills, with only minor overlap risk against general clinical-screening skills.

4 / 5

Total

15

/

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.