taiwan-md-knowledge-base — Claude Code skill: Taiwan knowledge base
A skill for maintaining an open knowledge base about Taiwan built on Astro v5, with Chinese and English articles and a D3.js graph. Useful if you write or translate content for that project.
npx skills add reason-machines/trending-skills --skill taiwan-md-knowledge-base -a claude-codeWhat taiwan-md-knowledge-base does
The skill documents how the taiwan-md project is put together and how to add to it. All content sits in the knowledge/ directory as Markdown — that is the single source of truth, and the site is a build-time projection of it. There are twelve categories, from history and geography to food and technology. Each one has a _Hub.md overview page plus individual articles.
English versions live in knowledge/en/ and mirror the Chinese folder layout. Every article carries frontmatter with required title, description, category and date fields, plus a list of sources with clickable URLs. Images come only from Wikimedia Commons under verified CC licenses and are cached locally in public/images/wiki/. Tags from the frontmatter become edges in the graph at /graph.
One rule matters more than the rest: never edit files in src/content/ by hand. Change knowledge/ first, then run bash scripts/sync.sh, or the build will serve stale pages. Running it locally needs Node.js 18+ and npm or pnpm.
What it helps with
- add a new Taiwan article to the right category
- translate a Chinese article into English and keep the folder structure
- set up a new category with its hub page
- find and cache a Wikimedia Commons image for an article
- debug why edits never show up on the site
Example prompts for the agent
- add an article about Taiwan night markets to the Food category
- translate knowledge/Food/bubble-tea.md into English under knowledge/en/Food/
- create a new category with a _Hub.md for both zh-TW and en
How to install taiwan-md-knowledge-base
1Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill taiwan-md-knowledge-base -a claude-code2Manually: put the files in place
~/.claude/skills/taiwan-md-knowledge-base/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/taiwan-md-knowledge-base/
1Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill taiwan-md-knowledge-base -a codex2Manually: put the files in place
.agents/skills/taiwan-md-knowledge-base/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill taiwan-md-knowledge-base -a cursor2Manually: put the files in place
.cursor/skills/taiwan-md-knowledge-base/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install reason-machines/trending-skills taiwan-md-knowledge-base2Manually: put the files in place
.github/skills/taiwan-md-knowledge-base/SKILL.md1Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill taiwan-md-knowledge-base -a gemini-cli2Platform CLI
gemini skills install https://github.com/reason-machines/trending-skills --path skills/taiwan-md-knowledge-baseManually: put the files in place
.devin/skills/taiwan-md-knowledge-base/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill taiwan-md-knowledge-base -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about taiwan-md-knowledge-base
How do I install taiwan-md-knowledge-base in Claude?
Run npx skills add reason-machines/trending-skills --skill taiwan-md-knowledge-base -a claude-code. The skill lands at ~/.claude/skills/taiwan-md-knowledge-base/SKILL.md.
What does taiwan-md-knowledge-base do?
It guides you through adding and translating articles in the open Taiwan knowledge base: folder layout, frontmatter templates and the content sync step.
Why don't my edits show up on the site?
src/content/ is generated from knowledge/ by scripts/sync.sh. Edit only knowledge/ and run the sync afterwards, otherwise the build picks up the old files.
