translation
Skill1.1k starsChanged 26 days agoMITView on GitHub
Translate, transcreate, review, or maintain multilingual product and marketing content, including source locking, glossary decisions, language style, machine-assisted workflows, legal-content safeguards, QA, and source-change synchronization. Use localization-strategy for market scope, locale architecture, rollout, and production release planning.
9 other projects use a version of this.
Trending
More talk lately.thin dataabout the whole repository
Most recently taken up by
- lengrufeng2008/dsh-skill-librarytheir own version, first seen Nov 15, 2026
- dongdong945/Skillstheir own version, first seen Nov 15, 2026
- Littlpinguin/marketing-cockpit-templatetheir own version, first seen Nov 3, 2026
- artemnovichkov/xcode-skillstheir own version, first seen Oct 30, 2026
- fastclaw-ai/fastclawtheir own version, first seen Oct 8, 2026
- doxygen/doxygentheir own version, first seen Oct 8, 2026
Who's talking about kostja94/marketing-skills
- akhmadilham/pinax-registry“[Skill Proposal]: marketing-skills”GitHub · Nov 2, 2026
- ProSkillsMD/proskills“[Candidate] kostja94/marketing-skills - large collection (172 SKILL.md files)”GitHub · Oct 17, 2026
- sudosubin/agents.nix“agent-skills.github.kostja94.marketing-skills: init at 1.0.0”GitHub · Oct 3, 2026
- alexanderkinging/Skill-Checker“False positives: Marketing terminology flagged as promotional content (CONT-005)”GitHub · Mar 9, 2026
The biggest 4 of 4 mentions linking to the repository that our crawl found. Each line is their own headline.
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- doxygen/doxygen★ 6.6ksame name
- fastclaw-ai/fastclaw★ 1.4ksame name
- artemnovichkov/xcode-skills★ 87same name
- dalroot/agentic-seo★ 26same name
- Littlpinguin/marketing-cockpit-template★ 9same name
- dongdong945/Skills★ 1same name
- lengrufeng2008/dsh-skill-library★ 0same name
- poorvith-mp/skills-writing★ 0same name
- Shugar86/my-agent★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- analytics-trackingSkill
- competitor-researchSkill
- article-contentSkill
- copywritingSkill
- podcast-marketingSkill
- video-marketingSkill
- visual-contentSkill
- keyword-clusteringSkill
- keyword-discoverySkill
- keyword-mappingSkill
- keyword-opportunitySkill
- keyword-researchSkill
- githubSkill
- grokipedia-recommendationsSkill
- linkedin-postsSkill
- medium-postsSkill
- pinterest-postsSkill
- reddit-postsSkill
- tiktok-captionsSkill
- twitter-x-postsSkill
- youtube-seoSkill
- entity-seoSkill
- local-seoSkill
- parasite-seoSkill
- programmatic-seoSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 12 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
12
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Read root {project}.md when present.
- Distinctive: line 31
If the source is unstable or contradictory, report the conflict before producing many dependent translations.
- Distinctive: line 47
Use one project termbase or glossary rather than embedding competing lists in multiple plans.
- Distinctive: line 63
check interpolation variables, plurals, gender, truncation, line wrapping, and RTL behavior.
- Distinctive: line 65
keep the same concept named consistently across navigation, onboarding, billing, and help.
- Distinctive: line 70
use natural target-market phrasing and approved query language without keyword stuffing.
- Distinctive: line 72
keep Title, H1, description, body, and social copy semantically aligned without requiring identical strings.
- Distinctive: line 78
keep source and localized update states visible so stale versions can be found.
- Distinctive: line 83
do not add a “source language prevails” clause or change legal effect without authorized legal direction.
- Distinctive: line 92
Run terminology, factual, completeness, and formatting checks.
- Very specific: line 96
When the source changes, calculate affected strings or sections, move the translation to outdated, and review only after understanding the …
- Distinctive: line 102
Check what matters for the artifact:
- Distinctive: line 104
no missing or accidentally untranslated user-facing content.
- Distinctive: line 126
Do not create a new translation-plan document when an existing project context, glossary, CMS workflow, or Skill should be updated.
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Translation
Own the language-production lifecycle. Deliver natural, accurate target-language content without changing product facts, inventing market claims, or treating translated words as proof that a locale is ready to launch.
Boundaries
- This skill owns translation, transcreation, terminology, style, linguistic review, and keeping translations current.
- localization-strategy owns locale selection, page coverage, URL architecture, routing, rollout, and release verification.
- keyword-research owns target-market queries. Never translate a source keyword list and call it localized research.
- Project positioning, feature availability, legal facts, and approved terminology remain in their project SSOTs.
Prepare the Source
Read root {project}.md when present. Before translating, establish:
- source version and owner;
- content type and target locale or market;
- user task, audience, tone, and channel;
- product facts and claims that must remain unchanged;
- approved terminology, forbidden terms, and terms intentionally left untranslated;
- layout, UI, metadata, structured-data, or character constraints;
- review level required by business, legal, safety, or conversion risk.
If the source is unstable or contradictory, report the conflict before producing many dependent translations.
Choose the Right Treatment
| Treatment | Use when | Main risk |
| Direct translation | Meaning and context transfer cleanly | Literal but unnatural phrasing |
| Localization | Formats, examples, terminology, or market facts differ | Unverified adaptation |
| Transcreation | Taglines, campaigns, landing-page persuasion, or cultural framing must change | Drifting from the product promise |
| Machine-assisted translation with review | Volume is high and risk is controlled | Fluent factual or terminology errors |
| Specialist translation | Legal, regulated, safety-critical, or technically exact material | Liability from semantic change |
Machine translation is a production method, not an automatic quality verdict. Match review depth to risk and page importance. Do not publish raw machine output merely because it reads fluently.
Maintain Terminology
Use one project termbase or glossary rather than embedding competing lists in multiple plans. Useful fields include:
- source term and approved target term;
- definition or product context;
- allowed variants and forbidden translations;
- keep-untranslated decision;
- locale or market scope;
- owner and approval status.
Distinguish brand names, registered entities, product features, technical standards, generic category terms, UI labels, and search-language variants. A search phrase may differ from the UI term; document the role rather than forcing one string everywhere.
Translate by Content Type
Product UI
- preserve action, state, and error meaning;
- check interpolation variables, plurals, gender, truncation, line wrapping, and RTL behavior;
- review strings in screen context, not only in a spreadsheet;
- keep the same concept named consistently across navigation, onboarding, billing, and help.
Marketing and Landing Pages
- preserve the page's audience, product promise, evidence, and desired action;
- use natural target-market phrasing and approved query language without keyword stuffing;
- adapt examples, proof, CTA, and objection handling only when the market facts support the change;
- keep Title, H1, description, body, and social copy semantically aligned without requiring identical strings.
Articles and Documentation
- preserve technical meaning, examples, code, citations, and internal-link intent;
- localize headings and anchors only when the publishing system supports the resulting links;
- keep source and localized update states visible so stale versions can be found.
Legal and Regulated Content
- preserve section correspondence, parties, defined terms, numbers, dates, rights, obligations, prohibitions, governing law, and dispute terms;
- do not add a “source language prevails” clause or change legal effect without authorized legal direction;
- record unresolved ambiguity for counsel rather than silently choosing a convenient interpretation;
- require specialist review before release.
Production Workflow
- Lock the source version and collect context.
- Load the project glossary and style guidance.
- Produce a first pass using the selected treatment.
- Run terminology, factual, completeness, and formatting checks.
- Review in the rendered product or page context.
- Complete native or specialist review at the required risk level.
- Mark the content ready and record its source version.
- When the source changes, calculate affected strings or sections, move the translation to
outdated, and review only after understanding the semantic change.
Suggested lifecycle states are translation-draft, review, localized-ready, outdated, and not-applicable. Use the project's existing state model when one exists.
Quality Gates
Check what matters for the artifact:
- no missing or accidentally untranslated user-facing content;
- approved terms and intentional untranslated terms are respected;
- claims, numbers, links, entities, prices, and feature availability match verified facts;
- grammar, register, punctuation, dates, numbers, units, and address formats suit the locale;
- UI variables, markup, links, and code remain valid;
- metadata and headings match the localized page intent;
- the rendered page has no clipping, mixed-language fallback, broken RTL, or inaccessible controls;
- the source version and approval state are traceable.
For large inventories, test every template and risk tier plus representative pages; do not pretend a small sample proves every page correct.
Output
Return the requested translation or review result plus only the supporting artifacts needed, such as:
- translator brief;
- approved and unresolved terminology decisions;
- translated or transcreated copy;
- issues requiring product, legal, or market decisions;
- QA and rendered-context findings;
- source-version and update-status notes.
Do not create a new translation-plan document when an existing project context, glossary, CMS workflow, or Skill should be updated.
Related Skills
- localization-strategy: locale scope, architecture, migration, rollout, and production validation
- keyword-research: target-market queries and search intent
- page-metadata, title-tag, meta-description, heading-structure: localized search and page copy
- copywriting, content-optimization: source and target copy quality
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
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.

