Agent skill
evryg-kb:article_review
Review French articles and translate them to English. Use when the user asks to review, check, or translate KB articles.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/product/evryg-kbarticle-review-evryg-org-evryg
SKILL.md
Article Review Skill
You are reviewing French articles written by a human for the evryg knowledge base. Your role is to assist with quality checks and translation, NOT to rewrite the author's work.
Core Principles
1. Respect the Author's Voice
- DO NOT change the French wording, style, or structure unless explicitly asked
- The French version is the source of truth, written intentionally by the author
- Only fix obvious typos or grammatical errors if spotted (and mention them)
2. Translation to English
- Translate the French article to English as faithfully as possible
- Preserve the author's tone, structure, and rhetorical choices
- Keep technical terms consistent with existing EN articles
- Maintain the same paragraph breaks and heading structure
Article Format Requirements
Frontmatter (YAML)
French article:
---
pageType: article
sidebarTitle: Short Title
tags: [tag1, tag2, tag3]
---
English article:
---
pageType: article
sidebarTitle: Short Title
tags: [tag1, tag2, tag3]
canonical-slug: french-article-slug
---
pageType: Alwaysarticlefor content articlessidebarTitle: Short title for navigation (keep concise)tags: Always in English, kebab-case, same tags for both FR and EN versionscanonical-slug: Only in EN version, matches the FR folder name
File Structure
content/
├── fr/.../category/
│ ├── article-slug-in-french/
│ │ └── index.mdx
│ └── _meta.ts
└── en/.../category/
├── article-slug-in-english/
│ └── index.mdx
└── _meta.ts
Content Style
- Use
*italics*for technical terms in their original language (e.g., kanban, muda) - Use French quotes « » in FR articles, English quotes "" in EN articles
- Internal links use absolute paths:
/fr/path/to/articleor/en/path/to/article - Footnotes use
[^1]syntax with definition at end of file
Typography Rules
French:
- Use non-breaking spaces before colons, semicolons, exclamation marks, and question marks
- Use em-dash (—) sparingly; prefer parentheses or commas for appositions
English:
- No space before punctuation
- Use commas or parentheses for appositions
Paragraph Structure
- Add line breaks between logical units within sections to improve readability
- Each major idea should be its own paragraph
- Avoid walls of text
Review Checklist
When reviewing an article, verify:
-
Frontmatter
-
pageType: articleis set -
sidebarTitleis concise -
tagsare in English, kebab-case - EN version has
canonical-slugmatching FR folder name
-
-
Content
- Title matches the folder slug theme
- Internal links are correct for each language
- Technical terms are italicized consistently
- Paragraphs are well-spaced (not walls of text)
-
Translation Quality
- Meaning is preserved accurately
- Tone matches the original
- Technical terms are consistent with existing EN articles
- Quotes and punctuation follow EN conventions
-
Navigation
-
_meta.tsis updated for both FR and EN
-
Workflow
- Read the French article first
- Check format compliance
- Create English translation preserving structure and voice
- Update both
_meta.tsfiles - Report any issues or suggestions to the author
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?