القائمة
Translate multiple services or guides to another locale in parallel. Use when asked to "translate all", "bulk translate", "localize everything to Dutch", or translate many items at once.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | bulk-translate |
| description | Translate multiple services or guides to another locale in parallel. Use when asked to "translate all", "bulk translate", "localize everything to Dutch", or translate many items at once. |
| argument-hint | 'service all <locale>' or 'guide all <locale>' or 'service <name1>, <name2> <locale>' or 'untranslated <locale>' |
Translate multiple items to a target locale in parallel by dispatching one subagent per item.
The last word is always the target locale (e.g. nl).
| Argument | Meaning |
|---|---|
service ProtonMail, Tutanota nl | Translate these services to Dutch |
service all nl | Translate all services to Dutch |
guide all nl | Translate all guides to Dutch |
service untranslated nl | Translate services missing Dutch content |
all nl | Translate all services + guides to Dutch |
For service untranslated nl:
Fetch all services, then for each check if the Dutch locale has content:
mcp__payload__findServices: {"limit": 100, "locale": "nl"}
Filter for services where description or name is empty/matches English (not translated).
For service all nl: Fetch all services regardless of translation status.
Show count, list, and target locale. Ask for confirmation.
Agent prompt template for services:
You are translating the service "{SERVICE_NAME}" to {LOCALE} for switch-to.eu.
Use the /translate skill. Process:
1. Fetch English content:
mcp__payload__findServices: {"where": "{\"name\": {\"contains\": \"{SERVICE_NAME}\"}}", "limit": 1, "locale": "en", "depth": 1}
Get: name, description, startingPrice, features, content, issues
2. Translate all localized fields to {LOCALE}:
- Translate meaning, not words. Read naturally in the target language.
- Keep same tone: direct, practical, slightly opinionated.
- Do NOT translate: brand names, service names, technical terms (API, GDPR, URL).
- Dutch: use "je/jij" (informal), compound words as one word, short sentences, "data" singular/plural.
- Also translate SEO fields: metaTitle, metaDescription, ogTitle, ogDescription, keywords.
3. Save via mcp__payload__updateServices with locale: "{LOCALE}".
Only send localized fields.
Return: service name, locale, fields translated, any issues.
Agent prompt template for guides:
You are translating the guide "{GUIDE_SLUG}" to {LOCALE} for switch-to.eu.
1. Fetch English: mcp__payload__findGuides by slug with locale: "en"
Get: title, description, intro, beforeYouStart, steps, troubleshooting, outro, missingFeatures
2. Translate all localized fields following the same rules.
3. Save via mcp__payload__updateGuides with locale: "{LOCALE}".
Return: guide slug, locale, fields translated, any issues.
## Bulk Translation Complete
Translated: X/Y items to {LOCALE}
| Item | Type | Fields | Status | Notes |
|------|------|--------|--------|-------|
| ProtonMail | Service | 6 | Done | — |
| Gmail to ProtonMail | Guide | 8 | Done | richText saved as plain text |
| ... | ... | ... | ... | ... |
Failed: [list with reasons]
Next steps:
- Review translations in Payload admin (/admin)
- Run /bulk-seo-check to audit translated SEO fields
- Run /bulk-humanize if translations read stiffly
Research multiple services in parallel using subagents. Each service gets the full research pass — vendor site, pricing, privacy/GDPR, Reddit sentiment, and recent news — written to both existing research fields and the newer structured fields (userSentiment, redditMentions, recentNews). Use when asked to "research all services", "bulk research", "research these services", or need to populate Research tabs for many services at once.
Post-publish SEO audit on a live page. Pulls GSC performance data, Jina Search for competitor SERP + content, current page content from Payload, and (optionally) Unlighthouse scores. Writes a prioritised rewrite plan to the pageAudits collection. Use when asked to "audit this page", "seo audit", "what's wrong with this page's SEO", "analyze ranking performance".
Surgically edit Payload CMS rich-text fields via the Payload MCP. Swap link URLs across all rich-text fields of a doc (including per-step `content` for guides), with optional visible-text rewriting. Pure MCP — no scripts, no file paths. Use when fixing broken outbound links from an SEO crawl, retargeting a vendor's canonical URL, or otherwise rewriting URLs inside published content.
Produce a ranked backlog of content ideas grounded in real signals. Mode A mines GSC for queries we don't rank for; Mode B mines Reddit and Jina SERP for services and categories we don't cover. Writes ranked findings to the contentOpportunities collection. Use when asked to "find opportunities", "what should we write next", "seo backlog", "content gaps".
Research a digital service and store structured findings in Payload CMS. Gathers company basics, pricing, privacy posture, Reddit sentiment, and recent news via Jina Reader/Search and the Reddit MCP. Use when asked to research a service, investigate a company, gather pricing/privacy/compliance data, or populate the Research tab on a service. Trigger phrases include "research this service", "investigate", "gather data on", "fill in research for".
ALWAYS use when writing code importing "unlighthouse". Consult for debugging, best practices, or modifying unlighthouse.