create-explanation
Skill5 starsChanged 5 months agoMITView on GitHub
Generate scholarly bilingual (English + Traditional Chinese) explanations for classical Chinese verses. Use when explaining Yilin, I Ching, or Tang poetry lines.
In this repository28 other files it gives its agents.
- AGENTS.mdAGENTS.md
- analyze-variationSkill
- arxiv-searchSkill
- blakean-sceneSkill
- codex-reviewSkill
- critic-loopSkill
- deepen-taskSkill
- deliver-changeSkill
- design-dnaSkill
- gloss-drift-auditSkill
- image-to-sceneSkill
- marketing-claritySkill
- market-pulseSkill
- media-kitSkill
- motion-craftSkill
- nextjs-i18n-seoSkill
- oss-licence-auditSkill
- plan-review-loopSkill
- shaughnessy-ichingSkill
- swapping-pptx-templatesSkill
- ui-ux-architectSkill
- unslopSkill
- upgrade-siteSkill
- vercel-build-speedSkill
- verify-changeSkill
- verse-to-promptSkill
- video-to-shortsSkill
- voice-calibrationSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Verify the reference before explaining — do not hallucinate historical facts
- Distinctive: line 43
Keep scholarly but accessible — no academic jargon
- Distinctive: line 52
Avoid: "This verse is about...", "The poem describes..."
- Distinctive: line 53
Prefer: Direct description → explanation → insight
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Create Verse Explanation
Generate scholarly bilingual explanations for classical Chinese oracular verses. These explanations make abstract ancient poetry accessible by explaining historical allusions and connecting imagery to meaning.
Your Task
Given a classical Chinese verse, produce:
- An English explanation (100-150 words)
- A Traditional Chinese explanation (150-200 characters)
- A references list of historical figures, places, or allusions used
Critical Requirements
Research Before Writing
For ANY historical reference:
- Verify the reference before explaining — do not hallucinate historical facts
- Common references needing verification:
- Figures: 大禹 (Da Yu), 蚩尤 (Chiyou), 彭祖 (Pengzu), 夏桀 (Xia Jie), etc.
- Places: 龍門 (Dragon Gate), 夏臺 (Xia Terrace), 羑里 (Youli), etc.
- Allusions: Classical idioms, historical events, mythological references
Writing Guidelines
English Explanation (100-150 words)
Structure:
- Open with the literal scene (1-2 sentences)
- What's happening in the verse visually/narratively?
- Ground the reader in the imagery before explaining
- Explain historical allusions (2-3 sentences)
- Clarify references with brief context
- Keep scholarly but accessible — no academic jargon
- Connect to transformation meaning (1-2 sentences)
- What quality of change does the verse capture?
Tone:
- Scholarly but conversational
- Explain without talking down
- Active voice preferred
- Avoid: "This verse is about...", "The poem describes..."
- Prefer: Direct description → explanation → insight
Example opening patterns:
- "Great Yu inspects the roads while Chiyou clears the way ahead..."
- "The verse depicts a parched horse climbing a mountain..."
- NOT "This verse is about Great Yu and Chiyou working together..."
- NOT "The poet uses the image of drought to symbolize..."
Traditional Chinese Explanation (150-200 chars)
Structure:
- 場景描述 (1 sentence)
- 典故解釋 (1-2 sentences)
- 變化意涵 (1 sentence)
Tone:
- 文白相間 (literary but accessible)
- 不說教,點到為止
Output Format
Present the result conversationally:
English Great Yu inspects the roads while Chiyou clears the way ahead, covering ten thousand miles without danger...
繁體中文 大禹巡視道路,蚩尤開闢通途,行遍萬里不遇危險...
References: 大禹, 蚩尤
Example: Strong Explanation
Verse: 大禹式路,蚩尤除道。周匝萬里,不危不殆,見其所使,無所不在。
English (138 words): Great Yu inspects the roads while Chiyou clears the way ahead, covering ten thousand miles without danger. Yu, the legendary flood-tamer who founded the Xia dynasty, represents methodical governance; Chiyou, the mythical warrior deity, embodies raw martial force. Together they symbolize the pairing of strategy and execution — authority that both plans and acts. The verse connects to the transformation from Creative (乾) pure yang to Splitting Apart (剝): as yang lines erode from below, power must expand its reach to compensate for shrinking foundation. "Seeing their agents everywhere" suggests surveillance born of weakness, not strength. The journey is safe not because of dominance but because authority has learned to delegate, to work through envoys rather than direct force.
繁體中文 (198 chars): 大禹巡視道路,蚩尤開闢通途,行遍萬里不遇危險。大禹為治水聖王,建夏朝;蚩尤為戰神,象徵武力。二者合象謀略與執行之配——既謀劃又行動的權威。詩呼應乾卦純陽至剝卦剝蝕之變:陽爻自下而蝕,權力須擴展觸角以補基礎之削弱。「見其所使,無所不在」暗示監視源於虛弱而非強大。旅途安全非因壓制,乃因權威學會委派,藉使者而非直接施力。
References: 大禹, 蚩尤
Quality Checks
Before finalizing output:
- All historical references verified (not hallucinated)
- EN explanation 100-150 words
- ZH explanation 150-200 chars
- All references listed
- Tone is scholarly but accessible
- Explanations connect imagery to verse meaning
- Both EN and ZH stand alone — not literal translations of each other
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

