Agent skill
Urdu
Write Urdu that sounds human. Not formal, not robotic, not AI-generated.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/urdu
SKILL.md
The Real Problem
AI Urdu is technically correct but sounds off. Too formal. Too ادبی (literary). Natives write more casually, with warmth and natural flow. Match that.
Formality Default
Default register is too high. Casual Urdu is warm and expressive. Unless explicitly formal: lean casual.
تم vs آپ vs تو
Three levels:
- آپ: formal, elders, respect
- تم: standard casual, peers
- تو: very intimate, close friends
- Online mostly uses تم or آپ depending on context
Urdu vs Hindi
Similar spoken, different written:
- Urdu: Nastaliq script (اردو)
- More Persian/Arabic vocabulary
- Different cultural expressions
- Don't mix scripts
Particles & Softeners
These make Urdu natural:
- نا: question tag, softening ("ٹھیک ہے نا؟")
- تو: emphasis ("یہ تو بہت اچھا ہے")
- ہی: emphasis ("یہی چاہیے")
- بھی: "also", "even"
Fillers & Flow
Real Urdu has fillers:
- یعنی، اچھا، تو
- ویسے، اصل میں
- سنو، دیکھو
- کیا بتائیں
Expressiveness
Don't pick the safe word:
- اچھا → بہترین، زبردست، کمال
- برا → بیکار، بکواس، گھٹیا
- بہت → انتہائی، کافی
Common Expressions
Natural expressions:
- ٹھیک ہے، اوکے، ہاں جی
- کوئی بات نہیں، کوئی مسئلہ نہیں
- سچی?، واقعی?، کیا بات ہے!
- واہ!، کیا خوب!
Reactions
React naturally:
- سچی?، واقعی?، کیا?
- واہ!، اللہ!، توبہ!
- زبردست!، کمال!، بہت خوب!
- ہاہاہا in text
Romanized Urdu
Common online:
- Roman script often used in texting
- "Kya haal hai", "Theek hai"
- Natural in casual digital contexts
The "Native Test"
Before sending: would an Urdu speaker screenshot this as "AI-generated"? If yes—too formal, too ادبی. Add casual warmth.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?