ancient-chinese-calendar-determination

Use when establishing an agricultural calendar or determining equinoxes and solstices. Guides celestial observation at four cardinal stations to fix seasonal timing using star positions and daylight measurement.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

87%

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

A concise, well-organized procedural skill with highly specific actionable guidance and clean structure. Its main gap is workflow_clarity: validation lives in a separate end section rather than as inline checkpoints with an error-recovery loop.

Suggestions

Embed a validation checkpoint inside each determination step (e.g., 'Confirm the identified mid-heaven star matches the expected station before marking the season') rather than only summarizing checks at the end.

Add a brief fix/retry loop for the calendar-adjustment step: if leap-month alignment drifts, re-measure the equinox and re-apply the correction.

Dimension	Reasoning	Score
Conciseness	The body is lean and procedural with no padding and no explanation of concepts Claude already knows; every line earns its place.	3 / 3
Actionability	Although code-free, the instruction-only guidance is concrete and specific — named officials, locations, mid-heaven stars (Niao/Huo/Xu/Mao), day-length criteria, 366 days, and leap months — which the rubric rewards for actionable instruction skills.	3 / 3
Workflow Clarity	A clear numbered 6-step sequence exists with a dedicated Validation section, but validation is detached from the steps and there is no validate→fix→retry feedback loop, which the 3 anchor requires.	2 / 3
Progressive Disclosure	No bundle files exist and the skill is under 50 lines with well-organized sections (Overview, Steps, Expected Outcomes, Validation) and no nested references, satisfying the simple-skill exception.	3 / 3
	Total	11 / 12 Passed

Description

75%

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-structured description with an explicit 'Use when...' trigger and clear what/when coverage, occupying a distinct niche. It is held back from top marks only by a somewhat narrow keyword set and a modest number of distinct concrete actions.

Suggestions

Broaden trigger-term coverage with common user phrasings and variations (e.g., 'seasonal timing', 'planting calendar', 'fixing the seasons', 'cardinal-direction star observation').

List a few more concrete actions explicitly (e.g., 'appoint observers, identify mid-heaven stars, measure day length, apply leap-month corrections') to lift specificity to 3.

Dimension	Reasoning	Score
Specificity	Names the domain ('agricultural calendar', 'equinoxes and solstices') and several actions ('establishing', 'determining', 'fix seasonal timing', 'star positions and daylight measurement'), but does not enumerate as many distinct concrete actions as the score-3 anchor.	2 / 3
Completeness	Explicitly answers both what ('Guides celestial observation at four cardinal stations to fix seasonal timing...') and when ('Use when establishing an agricultural calendar or determining equinoxes and solstices').	3 / 3
Trigger Term Quality	Opens with natural trigger phrasing ('Use when establishing an agricultural calendar or determining equinoxes and solstices') but the keyword set is narrow and lacks common variations, so it does not reach the broad coverage of a 3.	2 / 3
Distinctiveness Conflict Risk	The niche is highly specific — ancient agricultural calendar via four cardinal-station star observations — with distinct triggers unlikely to collide with other skills.	3 / 3
	Total	10 / 12 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: baojie/shiji-kb
Path: kg/ontology/ontology-v1/skus/procedural/skill_001/SKILL.md
Commit: 79c272f

Reviewed: 4 days 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.