| name | thai-renewal-expiry-triage |
| description | Extract expiring subscriptions, credentials, and contracts from messy Thai LINE, email, invoice, or note text, then turn them into a short action list with urgency and next steps. |
Renewal / Expiry Triage from Thai Messages
Use this skill when a Thai business operator needs to read a messy renewal notice, vendor message, or internal note and quickly decide what is expiring, how urgent it is, and what to do next.
When to use
- A LINE message mentions renewal, due dates, expiry, or suspension risk
- An email or invoice contains support / license / domain / SSL / contract dates
- An admin note is too messy to scan manually
- A team member needs a quick expiry summary before handing it to the owner
What this skill should produce
Return a concise Thai triage summary with:
- the expiry item
- category
- due date or timing
- urgency level
- business impact
- next action
Categories to look for
Prefer these buckets when relevant:
- SSL / certificate
- domain
- subscription
- support contract
- software license
- credential / password rotation
- vendor agreement
- other renewal item
Core workflow
- Read the full text once.
- Extract every item that looks like it can expire, renew, or lapse.
- Identify any exact dates, durations, or deadlines.
- Rank urgency:
- critical = outage, lockout, service stop, or immediate loss risk
- soon = needs action within days / this week
- later = still relevant but not urgent yet
- Write the next action in plain Thai.
- If the text is unclear, say what is missing instead of guessing.
Output format
Use this structure:
- āļŠāļĢāļļāļāđāļĢāđāļ§: one short Thai sentence
- āļĢāļēāļĒāļāļēāļĢāļāļĩāđāļāđāļāļāļāļģ: bullet list of expiry items
- āļāļĢāļ°āđāļ āļ:
- āļāļģāļŦāļāļ:
- āļāļ§āļēāļĄāđāļĢāđāļāļāđāļ§āļ:
- āļāļĨāļāļĢāļ°āļāļ:
- next action:
Quality rules
- Do not turn this into a generic summary.
- Do not invent dates.
- Do not over-explain.
- Keep the wording useful for a Thai owner or admin who must act fast.
- If there are no expiry items, say that clearly.
Good examples of source text
- "āđāļāđāļāļāđāļāļāļēāļĒāļļ SSL āļŦāļĄāļāļāļēāļĒāļļ 14 āđāļĄ.āļĒ. āļāđāļēāđāļĄāđāļāđāļāđāļ§āđāļāļāļ°āđāļāđāļēāđāļĄāđāđāļāđ"
- "Support contract āļĨāļđāļāļāđāļē A āļŦāļĄāļāļāļēāļĒāļļāļŠāļīāđāļāđāļāļ·āļāļāļāļĩāđ āļĢāļāļāļ§āļ confirm renew"
- "Google Workspace 10 users āļāļ°āļāļĢāļāļāļģāļŦāļāļāļŠāļąāļāļāļēāļŦāđāļŦāļāđāļē"
- "āļĢāļāļāļ§āļāđāļāļĨāļĩāđāļĒāļāļĢāļŦāļąāļŠāļāđāļēāļ admin āļ āļēāļĒāđāļāļ§āļąāļāļāļĩāđ"
Example output
- āļŠāļĢāļļāļāđāļĢāđāļ§: āļāļ 2 āļĢāļēāļĒāļāļēāļĢāļāļĩāđāļāđāļāļāļāđāļāļāļēāļĒāļļāļ āļēāļĒāđāļāļŠāļąāļāļāļēāļŦāđāļāļĩāđ
- āļĢāļēāļĒāļāļēāļĢāļāļĩāđāļāđāļāļāļāļģ:
- āļāļĢāļ°āđāļ āļ: SSL certificate
- āļāļģāļŦāļāļ: 14 āđāļĄ.āļĒ. 2026
- āļāļ§āļēāļĄāđāļĢāđāļāļāđāļ§āļ: critical
- āļāļĨāļāļĢāļ°āļāļ: āđāļ§āđāļāļāļēāļāđāļāđāļēāđāļĄāđāđāļāđ
- next action: āļāđāļāļāļēāļĒāļļāļāļąāļāļāļĩāđāļĨāļ°āđāļāđāļ owner
- āļāļĢāļ°āđāļ āļ: Subscription
- āļāļģāļŦāļāļ: āļŠāļąāļāļāļēāļŦāđāļŦāļāđāļē
- āļāļ§āļēāļĄāđāļĢāđāļāļāđāļ§āļ: soon
- āļāļĨāļāļĢāļ°āļāļ: āļāļđāđāđāļāđāļāļēāļāļāļđāļāļāļąāļāļŠāļīāļāļāļīāđ
- next action: āļĒāļ·āļāļĒāļąāļāļāļģāļāļ§āļ user āđāļĨāļ°āļāđāļāļāļēāļĒāļļ
Anti-patterns
Avoid outputs that:
- sound like a long report
- focus on marketing language
- ignore the deadline
- merge unrelated notes into one vague paragraph