무료GitHub에 공개

translation

When the user wants to translate content, create translation workflows, manage terminology, or optimize translation quality. Also use when the user mentions "translate," "translation," "localization copy," "glossary," "terminology," "style guide translation," "machine translation," "human translation," "TMS," or "multilingual content." For strategy, use localization-strategy.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

dalroot/agentic-seo스타 25(GitHub 25 + cccskills 0)

실행 점수 미검증

설치 방법 보기

포함된 파일(1)

SKILL.md8.5 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Content: Translation

Guides translation workflow, terminology, style, and quality for multilingual content. Covers when to use human vs machine translation, glossary and style guide creation, and SEO considerations. For i18n implementation, hreflang, and URL structure, see localization-strategy.

When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

Scope

Workflow: Brief → translate → review
Terminology: Glossary creation and management
Style guide: Voice, tone, formatting per language
Human vs MT: When to use each; post-editing
Quality: QA, consistency, SEO
Market-specific: Terminology by region

Initial Assessment

Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for brand voice, target markets, and product terminology.

Identify:

Content type: Product UI, marketing copy, blog, landing page, docs
Target language(s): Priority locales
Existing assets: Glossary, style guide, translation memory (TM)

1. Translation Workflow

Brief → Translate → Review

Phase	Purpose	Output
Brief	Context, audience, tone, glossary reference, style guide	Translator brief document
Translate	First pass; use glossary + TM when available	Draft translation
Review	Native speaker review; consistency, brand voice, SEO	Final translation

Translator Brief

Include in every project:

Context: What the content is for (landing page, product UI, blog)
Audience: Target market, user persona
Tone: Formal, casual, technical
Glossary: Link or attach; mandatory terms
Style guide: Reference or key rules
Constraints: Character limits (UI), SEO keywords to include naturally

Content-Type Workflow

Content Type	Approach	Notes
Product UI	Glossary-critical; short strings; consistency	Use TM; avoid machine translation
Marketing copy	Brand voice; cultural adaptation	Human translation; see terminology
Blog / Article	SEO; natural keyword placement	Re-research keywords in target language; don't translate keyword lists
Landing page	Conversion-focused; CTA clarity	Human; test localized CTAs
Technical docs	Precision; glossary	TM + glossary; consider MT + post-edit for high volume

2. Glossary & Terminology

Glossary Purpose

Consistency: Same term translated the same way across all content
Brand: Product names, feature names, approved phrasing
Compliance: Safety, legal, regulated terms
Cost: Reduces rework; accelerates review

Glossary Structure

Field	Purpose
Source term	Original (e.g., English)
Target term	Approved translation
Context	Where it appears; usage note
Do not translate	Brand names, product names (when applicable)

Market-Specific Terminology

Term	English	Chinese	Notes
Generative AI	Generative AI, GenAI	AIGC (人工智能生成内容)	Use "AIGC" for China; "Generative AI" for English
Influencer	Influencer	KOL (关键意见领袖)	"KOL" common in Chinese marketing
User	User	用户	Context-dependent
Dashboard	Dashboard	控制台, 仪表盘	Choose one; document in glossary

Principle: Don't translate terminology lists; research how target market searches and speaks. See keyword-research for multi-language keyword research.

3. Style Guide (Translation)

Elements to Define

Element	Purpose
Voice	Brand personality; formal vs casual
Tone	Varies by content type (support = helpful; marketing = persuasive)
Register	Formal (您) vs informal (你) in languages that distinguish
Punctuation	Quotation marks, spacing (e.g., no space before colon in French)
Formatting	Dates, numbers, units; locale-specific
Forbidden	Terms or phrases to avoid

Per-Language Considerations

Chinese: Simplified vs Traditional; measure word usage
German: Formal (Sie) vs informal (du); compound nouns
Japanese: Honorifics; keigo for formal contexts
Arabic: RTL; formal vs dialect

4. Human vs Machine Translation

When to Use Human Translation

Scenario	Reason
Product UI	Terminology, UX clarity, brand
Marketing copy	Persuasion, cultural nuance, CTAs
Landing pages	Conversion; tested copy
Legal, compliance	Accuracy, liability
Brand-critical	Taglines, campaign copy

When Machine Translation (MT) May Be Acceptable

Scenario	Condition
High-volume, low-stakes	Internal docs, user-generated content
Draft / triage	MT + human post-edit (MTPE)
Real-time	Chat, support; with disclaimer

Avoid

Raw MT for product/marketing: Terminology errors, cultural misfires, poor SEO
MT without post-edit for customer-facing content
Translating keyword lists instead of re-researching in target language

5. Translation Memory (TM) & TMS

Translation Memory

What: Stores approved source↔target sentence pairs
Benefit: Consistency; reuse; lower cost per word; faster turnaround
Best practice: Maintain TM; clean duplicates; align with glossary

Translation Management System (TMS)

Use for: Centralized workflow; glossary + TM integration; vendor management
When: Multiple languages; ongoing translation; team collaboration

6. Quality & SEO

Quality Checklist

SEO for Translated Content

Keywords: Re-research in target language; don't translate from source
Metadata: Title, description translated; see title-tag, meta-description
Hreflang: Technical implementation in localization-strategy; translation produces the content
Thin content: Avoid publishing many low-quality translated pages at once; can trigger penalties. See localization-strategy Multilingual Risks.

7. Integration with Localization

Topic	Skill
i18n implementation	localization-strategy
URL structure, hreflang	localization-strategy
Translation workflow, glossary, style	This skill (translation)
Keyword research by market	keyword-research; localization-strategy

When adding a new locale: create glossary, style guide, then translate. See localization-strategy for technical checklist (hreflang, sitemap, metadata).

Output Format

Translator brief (context, audience, glossary, style)
Glossary additions or updates
Style guide notes for target language
Human vs MT recommendation
Quality checklist

Related Skills

Strategy & Technical

localization-strategy: i18n, hreflang, URL structure, pricing by market; translation produces content for localized pages
content-strategy: Multilingual content planning; avoid thin translations
content-marketing: Content types and formats; translation as one channel adaptation

SEO & Content

keyword-research: Multi-language keyword research; don't translate keyword lists
page-metadata: Hreflang implementation
title-tag, meta-description: Translate metadata per locale
copywriting: Source copy to translate; brand voice
image-optimization: Localize image filenames for translated pages

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

같은 저장소의 스킬

404-page-generator

무료

When the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

dalroot/agentic-seo252026년 10월 20일 업데이트

about-page-generator

무료

When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

dalroot/agentic-seo252026년 10월 20일 업데이트

affiliate-marketing

무료

When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

dalroot/agentic-seo252026년 10월 20일 업데이트

affiliate-page-generator

무료

When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

dalroot/agentic-seo252026년 10월 20일 업데이트

ai-traffic-tracking

무료

When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

dalroot/agentic-seo252026년 10월 20일 업데이트

alternatives-page-generator

무료

When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

dalroot/agentic-seo252026년 10월 20일 업데이트

dalroot의 스킬 모두 보기

이 스킬의 문제 신고

설치

명령으로 설치

npx skills add https://github.com/dalroot/agentic-seo --skill translation

터미널에 붙여 넣고 실행합니다(Node.js 필요). Claude Code, Codex 등 설치할 에이전트를 고를 수 있습니다.

에이전트에게 부탁하기

다음 Agent Skill을 설치해 주세요.
https://github.com/dalroot/agentic-seo/tree/master/skills/content/translation

먼저 SKILL.md와 첨부 파일의 내용을 확인해 수상한 처리(외부 전송, 인증 정보 읽기 등)가 없는지 확인한 뒤 Claude Code는 ~/.claude/skills/translation/, Codex는 ~/.agents/skills/translation/ 에 배치해 주세요.

이 문장을 그대로 Claude Code나 Codex에 보내면 내용을 확인한 뒤 설치해 줍니다.

GitHub에서 소스 보기

저장소: dalroot/agentic-seo
스타: 25
포크: 3
카테고리: 비즈니스
라이선스: MIT
원문 언어: 중국어
최종 업데이트: 2026년 10월 20일

스킬은 에이전트를 위한 지시와 스크립트의 묶음입니다. cccskills는 내용의 안전성을 보증하지 않습니다. 설치하기 전에 내용을 확인하세요.

포함된 파일(1)

SKILL.md(원문)

Content: Translation

Scope

Initial Assessment

1. Translation Workflow

Brief → Translate → Review

Translator Brief

Content-Type Workflow

2. Glossary & Terminology

Glossary Purpose

Glossary Structure

Market-Specific Terminology

3. Style Guide (Translation)

Elements to Define

Per-Language Considerations

4. Human vs Machine Translation

When to Use Human Translation

When Machine Translation (MT) May Be Acceptable

Avoid

5. Translation Memory (TM) & TMS

Translation Memory

Translation Management System (TMS)

6. Quality & SEO

Quality Checklist

SEO for Translated Content

7. Integration with Localization

Output Format

Related Skills

Strategy & Technical

SEO & Content

Pages

리뷰

댓글

같은 저장소의 스킬

404-page-generator

about-page-generator

affiliate-marketing

affiliate-page-generator

ai-traffic-tracking

alternatives-page-generator