القائمة
Email subject line encoding rules for gmail_send. Use when sending emails, composing subjects, or any gmail_send call.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
استنادا إلى تصنيف SOC المهني
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/htekdev/copilot-home-assistant --skill email-encodingيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
Execute pending agent-surface tasks by dispatching dedicated agents for each task. Quality-first approach — each task gets a focused agent, batched 3-4 in parallel. Use when user says "execute agent tasks", "run agent queue", "process agent-surface tasks", "agent task execution", or during the agent-task-executor cron cycle.
Hookflow governance philosophy and creation patterns — every behavioral correction becomes a deterministic hookflow rule. Use when: "create hook", "hookflow rule", "enforce behavior", "block pattern", "governance hook", "prevent mistake", "deterministic enforcement", "preToolUse deny", "postToolUse advisory", "hookflow audit", "new YAML hookflow", "behavioral correction", "hookflow-js"
{{PERSONAL_DOMAIN}} blog article creation — frontmatter schema, tag conventions, research standards, quality checklist, git worktree PR workflow, and video-companion article mode. Use when creating articles on {{PERSONAL_DOMAIN}}, writing blog posts, creating PRs on htek-dev-site, checking article quality, or any agent says "write article", "blog post", "{{PERSONAL_DOMAIN}} article", "create PR for article", "frontmatter schema", "article quality check".
| name | email-encoding |
| description | Email subject line encoding rules for gmail_send. Use when sending emails, composing subjects, or any gmail_send call. |
"send email", "gmail_send", "email subject", "compose email", "write email", "draft email"
NEVER use emojis, arrows (→), or special Unicode characters in gmail_send subject lines.
The Gmail API's subject line encoding double-encodes UTF-8, producing garbled text (mojibake). Email body text is unaffected.
| Location | Emojis/Unicode | Result |
|---|---|---|
| Subject line | 🔬 | Garbled: ðŸÂ"¬ |
| Subject line | → | Garbled: â†Â' |
| Email body | 🔬 → ✅ | Works fine |
gmail_send(subject="🔬 Weekly Research Update", ...)
gmail_send(subject="Budget → Reviewed ✅", ...)
gmail_send(subject="📋 Family Tasks for May 9", ...)
gmail_send(subject="Weekly Research Update", ...)
gmail_send(subject="Budget Reviewed", ...)
gmail_send(subject="Family Tasks for May 9", ...)
gmail_send(subject="[Action Required] NICU Follow-Up Appointment", ...)
gmail_sendThe gmail_send tool passes the subject through an encoding layer that double-encodes UTF-8 characters. Standard ASCII (letters, numbers, punctuation like []()-:!?) works perfectly. Anything outside ASCII (emojis, arrows, accented characters, Unicode symbols) gets corrupted in transit.
[URGENT], [Action Required], ---