agentleFS
Sign inStart free
MuvonMuvon/octomind-tap/skills/content-locale-humanize-th/SKILL.md

content-locale-humanize-th

Skill6 starsChanged 8 months agoApache-2.0View on GitHub

Calibration anchors for AI-slop and translationese in Thai (th) text. Use alongside content-locale-humanize when the target is Thai.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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
  1. Distinctive:

    No spaces between words; a space marks a clause or sentence break, full stops are not used in running text, and English-style comma density …

    line 38

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

Overview

Calibration anchors and current norms for Thai (th-TH), feeding content-locale-humanize's dimensions. A calibration aid, not the checklist; reason natively beyond it.

Rules

AI tells

Sourcing confidence: the weakest in this set. Searches found Thai AI-detection tools but no independently documented word- or phrase-level AI tells. Don't invent a plausible list to fill the gap; if a sourced list appears, add it here.

Translationese from English

Lean on the structural checks, which are unusually visible in Thai:

  • English sentence structure carried over: Thai has no articles or tense inflection and topicalizes differently.
  • ถูก-passives copied from English; native Thai reserves ถูก mostly for adverse events and otherwise prefers active or topic-first sentences.
  • Pronouns Thai would drop (คุณ, เขา, มัน) and stacked การ/ความ nominalizations mirroring English abstract nouns.
  • Rhythm is hard to judge by eye without word spaces; read for natural clause breaks rather than word counts.

Current norms

  • No spaces between words; a space marks a clause or sentence break, full stops are not used in running text, and English-style comma density reads as translated.
  • Polite particles (ครับ/ค่ะ) are gendered: in UI and documentation either avoid them or follow the brand voice, consistently.
  • Spelling and transliteration follow the Royal Society of Thailand; formal and government contexts use Buddhist Era years (CE + 543).

References

Reviewed 2026-10-12. No solid per-language AI-tell sourcing found. Norms: Royal Society of Thailand (ราชบัณฑิตยสภา) dictionary and transcription rules.

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.

Check your setup, free