thai
Skill4 starsChanged 2 months agoMITView on GitHub
Route and manage Thai-locale domain-knowledge skills — Thai tax documents, government letters, PDPA notices, national ID/PromptPay validation, BE/CE date conversion, addresses, social captions, customer-service replies, resumes, and translation. Use when the user asks for Thai-specific documents, formats, or validations that a general-purpose agent tends to get wrong, such as VAT/WHT math, พ.ศ./ค.ศ. date conversion, national ID checksum, or register-aware EN-TH translation.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- thititongumpun/skillstheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- thititongumpun/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository58 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/project-docs-prep/templates/AGENTS.mdAGENTS.md
- skills/project-docs-prep/templates/CLAUDE.mdCLAUDE.md
- deep-planningSkill
- deep-planningSkill
- deprecatedSkill
- architecture-reviewSkill
- code-reviewSkill
- diagnoseSkill
- tddSkill
- ui-design-engineeringSkill
- ux-ui-design-assessmentSkill
- in-progressSkill
- mcp-tool-managementSkill
- skill-managementSkill
- obsidian-canvasSkill
- obsidian-markdownSkill
- obsidian-notion-bridgeSkill
- obsidian-vault-workflowSkill
- boomz-preferencesSkill
- personal-agent-workflowSkill
- personalSkill
- automation-designSkill
- grill-with-docsSkill
- handoffSkill
- inbox-meeting-triageSkill
- markdown-reportSkill
- prompt-improvementSkill
- project-docs-prepSkill
- claim-citation-checkSkill
- daily-news-reportSkill
- github-skill-researchSkill
- project-discoverySkill
- repo-tourSkill
- research-methodologySkill
- seo-website-evaluatorSkill
- thai-addressSkill
- thai-customer-serviceSkill
- thai-date-formatSkill
- thai-festival-cardSkill
- thai-government-formSkill
- thai-id-validateSkill
- thai-invoiceSkill
- thai-pdpaSkill
- thai-resumeSkill
- thai-social-captionSkill
- thai-text-processingSkill
- thai-translateSkill
- backtest-expertSkill
- dividend-value-screenerSkill
- drawdown-circuit-breakerSkill
- exposure-coachSkill
- market-breadth-analyzerSkill
- portfolio-managerSkill
- position-sizerSkill
- tradingSkill
- trader-memory-coreSkill
- uptrend-analyzerSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 4 are distinctive, and 5 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.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill to find or scaffold a Thai-specific domain-knowledge skill under skills/thai/.
- Distinctive: line 37
Never carry over a legal or tax figure (VAT rate, WHT rate, PDPA clause number) from a source without checking it is current — cite the …
- Distinctive: line 38
Every skill that touches legal, tax, or compliance content must carry a "not legal/tax advice" disclaimer.
- Very specific: line 39
Write bilingual, Thai-first trigger phrases in the description frontmatter.
- Very specific: line 74
Create skills/thai/<name>/SKILL.md from the template.
- Distinctive: line 75
Verify any numeric or legal fact against a current official source.
- Very specific: line 76
If the skill ships code (validator, calculator), place it beside SKILL.md with a self-test that exits non-zero on failure.
- Very specific: line 77
Run scripts/validate-skills.ps1 and flip the roadmap row to built.
- Distinctive: line 78
Add the new skill to README.md's Skill Categories section.
≈ “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
Thai Locale Skills
Use this skill to find or scaffold a Thai-specific domain-knowledge skill under skills/thai/.
Purpose
skills/thai/ holds content-domain skills for Thai-specific facts, formats, and documents — the kind of task where a general-purpose agent silently guesses wrong (date era, honorific register, legal document structure, checksum validation). This category is content, not workflow. It complements engineering/, productivity/, and the other buckets, which describe how to work, by supplying Thai-specific what.
Pattern inspired by Boom-Vitt/claude-thai-skills (MIT) — see NOTICE.md for attribution. Skills here are written fresh and checked against current sources rather than copied verbatim, because legal and tax figures drift over time and that repo is a single-maintainer side project (its own README flags 8 of 12 skills as unverified v0.1 prose).
Candidate skills (roadmap)
| Skill | Purpose | Status | Tier |
| thai-date-format | พ.ศ./ค.ศ. era conversion, Thai numerals, formal/business date formats | built | validator (convert.py, self-test) |
| thai-id-validate | Thai national ID checksum, phone normalization, PromptPay QR payload | built | validator (validate.py, self-test incl. CRC-16 reference vector) |
| thai-address | Thai address parsing, postal code to province lookup (77 provinces) | built | validator (parse.py + provinces.json, self-test) |
| thai-invoice | Tax invoice / receipt / quotation / WHT certificate per Revenue Code §86/4 | built | validator (calc.py, self-test) + templates |
| thai-government-form | Official letters, leave requests, power of attorney per PM Office regulations on งานสารบรรณ | built | prose + template |
| thai-pdpa | PDPA-compliant privacy notices and consent banners | built | prose + templates |
| thai-translate | EN⇄TH translation preserving register and pronoun choice | built | prose |
| thai-social-caption | Thai social captions for FB / TikTok / IG / Threads / X / Pantip | built | prose |
| thai-customer-service | LINE OA / Shopee / Lazada reply scripts with an apology ladder | built | prose |
| thai-resume | Thai and bilingual resume conventions | built | prose + template |
| thai-festival-card | Festival greetings and taboo avoidance | built | prose |
| thai-text-processing | Thai word segmentation, NFC normalization, RTGS romanization | built | prose + examples (normalize.py self-tests standalone; segmentation.py self-tests the naive-split failure and optionally PyThaiNLP if installed) |
All 12 built as of this pass. "Prose" tier means the content is a drafting aid based on generally stable conventions rather than code-verified math — see each skill's "Known limitations" section for what still needs a human/current-source check before real use (tax rates, legal clause numbers, PDPC guidance, etc.).
Rules
- Never carry over a legal or tax figure (VAT rate, WHT rate, PDPA clause number) from a source without checking it is current — cite the source and the date it was checked in the skill's "Known limitations" section.
- Every skill that touches legal, tax, or compliance content must carry a "not legal/tax advice" disclaimer. Treat it as load-bearing — do not remove it during later edits.
- Write bilingual, Thai-first trigger phrases in the
descriptionfrontmatter. Claude pattern-matches literally, so list the actual Thai phrases a user would type, not just an English paraphrase. - Give each skill in this folder one job. If a request spans two rows in the roadmap (e.g. an invoice that also needs a PDPA notice), let the router load both skills rather than merging them.
Skill template for this folder
---
name: thai-skill-name
description: Use this skill for <domain>. Trigger on "<Thai phrase 1>", "<Thai phrase 2>", "<English phrase>". If the task is <out-of-scope case>, use <other skill> instead.
---
# Title (ไทย + English subtitle)
## Overview
สั้น ๆ ว่าทำอะไร และทำไม agent ที่ไม่มีสกิลนี้มักพลาด
## When to use
- ...
## When NOT to use
- ถ้าเป็นกรณี X ให้ใช้ <skill อื่น> แทน
## Core knowledge
ตาราง/สูตร/ระเบียบที่ต้องรู้ — อ้างอิงแหล่งที่มาและวันที่ตรวจสอบล่าสุด
## Common mistakes
1. ...
## Known limitations
- ข้อมูลอิงจากประกาศ/อัตรา ณ วันที่ตรวจสอบ — ถ้ามีการเปลี่ยนแปลงต้องอัปเดตWorkflow to add a new skill here
- Pick one row from the roadmap table above (or a new one the user asks for).
- Create
skills/thai/<name>/SKILL.mdfrom the template. - Verify any numeric or legal fact against a current official source; note the check date under "Known limitations".
- If the skill ships code (validator, calculator), place it beside
SKILL.mdwith a self-test that exits non-zero on failure. - Run
scripts/validate-skills.ps1and flip the roadmap row tobuilt. - Add the new skill to README.md's Skill Categories section.
Output Format
End with:
- Which roadmap skill was built or updated
- Sources checked for any legal/tax/date figure, with the check date
- Whether the disclaimer (if applicable) is present
- What remains in the roadmap
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.

