agentleFS
ntaffziintaffzii/Skill-Agents/skills/thai/SKILL.md

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

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
  1. Very specific:

    Use this skill to find or scaffold a Thai-specific domain-knowledge skill under skills/thai/.

    line 8
  2. Distinctive:

    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 …

    line 37
  3. Distinctive:

    Every skill that touches legal, tax, or compliance content must carry a "not legal/tax advice" disclaimer.

    line 38
  4. Very specific:

    Write bilingual, Thai-first trigger phrases in the description frontmatter.

    line 39
  5. Very specific:

    Create skills/thai/<name>/SKILL.md from the template.

    line 74
  6. Distinctive:

    Verify any numeric or legal fact against a current official source.

    line 75
  7. Very specific:

    If the skill ships code (validator, calculator), place it beside SKILL.md with a self-test that exits non-zero on failure.

    line 76
  8. Very specific:

    Run scripts/validate-skills.ps1 and flip the roadmap row to built.

    line 77
  9. Distinctive:

    Add the new skill to README.md's Skill Categories section.

    line 78

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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)

SkillPurposeStatusTier
thai-date-formatพ.ศ./ค.ศ. era conversion, Thai numerals, formal/business date formatsbuiltvalidator (convert.py, self-test)
thai-id-validateThai national ID checksum, phone normalization, PromptPay QR payloadbuiltvalidator (validate.py, self-test incl. CRC-16 reference vector)
thai-addressThai address parsing, postal code to province lookup (77 provinces)builtvalidator (parse.py + provinces.json, self-test)
thai-invoiceTax invoice / receipt / quotation / WHT certificate per Revenue Code §86/4builtvalidator (calc.py, self-test) + templates
thai-government-formOfficial letters, leave requests, power of attorney per PM Office regulations on งานสารบรรณbuiltprose + template
thai-pdpaPDPA-compliant privacy notices and consent bannersbuiltprose + templates
thai-translateEN⇄TH translation preserving register and pronoun choicebuiltprose
thai-social-captionThai social captions for FB / TikTok / IG / Threads / X / Pantipbuiltprose
thai-customer-serviceLINE OA / Shopee / Lazada reply scripts with an apology ladderbuiltprose
thai-resumeThai and bilingual resume conventionsbuiltprose + template
thai-festival-cardFestival greetings and taboo avoidancebuiltprose
thai-text-processingThai word segmentation, NFC normalization, RTGS romanizationbuiltprose + 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 description frontmatter. 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

  1. Pick one row from the roadmap table above (or a new one the user asks for).
  2. Create skills/thai/<name>/SKILL.md from the template.
  3. Verify any numeric or legal fact against a current official source; note the check date under "Known limitations".
  4. If the skill ships code (validator, calculator), place it beside SKILL.md with a self-test that exits non-zero on failure.
  5. Run scripts/validate-skills.ps1 and flip the roadmap row to built.
  6. 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.