by twhsi
AI Agent Skills for Chinese Knowledge Workers: iMandalArt, FIRE, planning, and publishing workflows for Claude Code, Codex, and LLM agents.
# Add to your Claude Code skills
git clone https://github.com/twhsi/skillsLast scanned: 7/9/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-07-09T07:46:51.665Z",
"npmAuditRan": true,
"pipAuditRan": true,
"promptInjectionRan": true
}skills is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by twhsi. AI Agent Skills for Chinese Knowledge Workers: iMandalArt, FIRE, planning, and publishing workflows for Claude Code, Codex, and LLM agents. It has 150 GitHub stars.
Yes. skills passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/twhsi/skills" and add it to your Claude Code skills directory (see the Installation section above).
skills is primarily written in Python. It is open-source under twhsi on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh skills against similar tools.
No comments yet. Be the first to share your thoughts!
iMandalArt, FIRE semantic analysis, planning, and publishing workflows for Claude Code, Codex, and mainstream LLM agents.
This repository is Yunghsi's public agent-skill system for Chinese knowledge workers. It turns repeatable writing, planning, note-making, and publishing workflows into skills that can be used by Claude Code, Codex, ChatGPT, Gemini, Hermes, and other LLM agents.
The source of truth lives in skills/*/SKILL.md; the website turns those files into generated LLM manifests, a searchable skill index, install commands, version labels, Git revisions, and update timestamps.
Live site: https://www.twhsi.com/
Agent manifest: https://www.twhsi.com/agent.json
Skill index: https://www.twhsi.com/skills.json
LLM context: https://www.twhsi.com/llms.txt
agent.json, skills.json, and llms.txt.Input: 200 days of daily plans, manuscript notes, or Markdown drafts
Skills: imandalart + fire-analysis-card + project-note-json-to-epub
Output: FIRE JSON + iMandalArt 2.01 card + Markdown / EPUB / booklet path
For an LLM or agent, start with:
curl -s https://www.twhsi.com/llms.txt
imandalart turns loose source material into one hard-line 3x3 Mandala index card.
iMandalArt 2.01 is designed around a strict text contract:
Ⓐ through Ⓗ.◎◎◎◎◎.Current status: iMandalArt 2.01 is optimized for CJK workflows. An English-native version is planned so the same 3x3 thinking rhythm can work naturally for English notes without forcing a Chinese character contract.
Example:
Ⓐ健康復節 Ⓑ書稿收束 Ⓒ財流降噪
羽球慢回身 書章拉中心 訂閱先盤點
跑走養節奏 青蛙先寫書 現流養書路
Ⓓ家人點火 ◎◎◎◎◎ Ⓔ人脈成路
問夢不說教 二九週計劃 約談留三卡
陪走百年路 ◎◎◎◎◎ 好友接技能
Ⓕ內在放下 Ⓖ日文沉澱 Ⓗ休閒充電
少說更點火 句子先編號 合唱鬆心身
不急證明我 接詞成路徑 吉他聽太陽
Use it for weekly planning, writing focus, knowledge capture, and CJK note workflows where visual stability matters as much as semantic compression.
| Skill | Role |
|---|---|
imandalart |
Compress source material into one CJK-friendly 3x3 Mandala card. |
fire-analysis-card |
Turn Chinese notes and manuscripts into FIRE semantic analysis cards. |
todays-daily-plan |
Convert spoken planning notes into an Obsidian day-plan Mandala grid. |
project-note-json-to-epub |
Turn structured project-note JSON into EPUB and publishing outputs. |
markdown-nine-grid-clipboard |
Convert grids and cards into Markdown table workflows. |
fire-analysis-card is now on FIRE 2.0:
F = Full-D: stable numbering for temporary, permanent, and project notes.I = Index: keyword webs and retrieval handles.R = Route: thinking paths through the material.E = Evolution: time-based card-box growth for semantic search.The live website generates freshness metadata from skill files and Git history on every deployment. Each skill entry includes:
version: the semantic skill version when declared, otherwise Unversionedrevision and revision_short: the latest Git commit for that skill pathupdated_at: the latest update timestamp for that skill pathOpen the live generated table:
Featured metadata check: imandalart declares v2.01, and fire-analysis-card declares v2.0.
| Route | Purpose | Representative skills |
|---|---|---|
| Time | Daily focus, planning rhythm, calendar actions, and long-range training loops. | todays-daily-plan, imandalart, personal-athlete-81-grid, fantastical-calendar |
| Cards | FIRE analysis, grid cards, Markdown tables, and graph views. | fire-analysis-card, markdown-nine-grid-clipboard, obsidian-graph-view |
| LLM | Repeatable LLM workflows, structured inputs, scripts, and metadata. | project-note-json-to-epub, epub-hypercard-obsidian |
| Desktop | Local Mac workflows, clipboard outputs, calendar bridges, and working-desk routines. | fantastical-calendar, markdown-nine-grid-clipboard |
| Publish | Booklets, EPUBs, HyperCard returns, and public GitHub publishing paths. | project-note-json-to-epub, epub-hypercard-obsidian |
assets/ public display assets
skills/ installable skills for mainstream LLM workflows
docs/ install notes, book links, and skill index
examples/ sample inputs and outputs
archive/ older drafts and retired skills
Hermes.md system map and command file
site/ static website source
dist/ generated website output, ignored by git
From the repository root:
cp -R skills/fire-analysis-card ~/.codex/skills/
cp -R skills/todays-daily-plan ~/.codex/skills/
cp -R skills/imandalart ~/.codex/skills/
Then validate a skill:
python3 ~/.codex/skills/.system/skill-creator/scripts/quick_validate.py skills/fire-analysis-card
npm run build
The build reads skills/*/SKILL.md, extracts frontmatter, detects declared versions, asks Git for latest per-skill revision timestamps, and writes:
dist/agent.jsondist/skills.jsondist/llms.txtVercel configuration lives in vercel.json: build command npm run build, output directory dist.
When a skill changes, update the skill file first, run validation, rebuild the website, and push to main. The live site should always show the latest skill version, revision, and update time.