glebis/library-sync
skills/library-sync/SKILL.md
Sync and manage bilingual (EN/RU) library content for agency-docs. Use when adding, updating, or reviewing library articles. Handles translation, sync checks, and Russian stylistic review.
$ install --global
skillsauthnpx skillsauth add glebis/claude-skills library-syncInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 4, 2026, 2:13 AM399.9s1 file scanned
SKILL.md
- name:
- library-sync
- description:
- Sync and manage bilingual (EN/RU) library content for agency-docs. Use when adding, updating, or reviewing library articles. Handles translation, sync checks, and Russian stylistic review.
Library Sync Skill
Manages the bilingual library at ~/Sites/agency-docs/content/docs/library/ with English (en/) and Russian (ru/) versions.
Commands
add <slug> — Add a new article to both languages
- Create the article in English first at
content/docs/library/en/<slug>.mdx - Translate to Russian at
content/docs/library/ru/<slug>.mdx - Add to both
meta.jsonfiles in the appropriate section - Run Russian stylistic review
- Verify both render correctly
sync — Check sync status between EN and RU
- List all files in
en/andru/ - Report files missing in either language
- Compare frontmatter titles (ensure they match conceptually)
- Flag articles updated in one language but not the other (compare git timestamps)
translate <slug> <from> <to> — Translate an article
- Read the source article
- Translate to target language
- Adapt examples and links for the target audience
- Run stylistic review if target is Russian
- Update meta.json
review-ru — Russian stylistic review
Run on all Russian library articles. Check for:
- Consistency: same terms used throughout (not mixing Агент/Эйджент)
- Natural Russian: not word-for-word translation from English
- Technical terms: keep English terms where standard (Git, MCP, API, CLAUDE.md)
- Links: internal links use
/library/ru/paths - Tone: educational but not condescending, informal "ты" address
update <slug> — Update an existing article in both languages
- Read the current version
- Apply changes to the primary language
- Sync changes to the other language
- Run Russian review if Russian was changed
File Structure
content/docs/library/
├── index.mdx # Landing page
├── meta.json # Top-level nav (separators + language folders)
├── en/
│ ├── meta.json # English article order with section separators
│ └── *.mdx # English articles
└── ru/
├── meta.json # Russian article order with section separators
└── *.mdx # Russian articles
Russian Style Guide
- Use "ты" (informal), not "вы" (formal)
- Keep technical terms in English: Git, API, MCP, CLAUDE.md, CLI, LLM, token
- Transliterate only when a Russian term is well-established: агент, промт, токен
- Don't translate code examples or command-line output
- Adapt cultural references (e.g., currency examples: use both $ and ₽)
- Cross-link to English version at the bottom:
[English version](/library/en/<slug>) - Cross-link from English to Russian:
[Русская версия](/library/ru/<slug>)
Meta.json Sections
Use ---SectionName--- separators in meta.json for nav grouping:
- Modes / Режимы
- Core Concepts / Ключевые концепции
- Features / Возможности
- Tools / Инструменты
- Reference / Справочник
Related Skills
glebis/tufte-report
development
VerifiedTrustedCommunity
Create Tufte-inspired data reports and infographic dashboards as standalone HTML files. Uses EB Garamond for text, Monaspace Argon for numbers, Chart.js for interactive charts, and inline SVG sparklines. Produces publication-quality reports with 2-column narrative+data layouts, status dashboards, scroll animations, and responsive mobile support. Use this skill whenever the user wants to create a data report, activity dashboard, infographic, personal analytics page, health tracker visualization, or any document that combines narrative text with interactive charts and tables. Also triggers for "make a report like Tufte", "create an infographic", "build a dashboard", "visualize my data", or requests for beautiful data-driven documents.
246SKILL.mdUpdated Apr 24, 2026
glebis/release
documentation
VerifiedTrustedCommunity
Cut a software release and maintain a tiered compatibility policy. Use when the user wants to release, ship a version, bump the version, tag a release, write a changelog, or update COMPATIBILITY. Config-driven via release.config.json; bumps version files, runs a readiness gate, updates COMPATIBILITY.md tiers and deprecations, tags (→ release workflow), and reports closed issues. Teaches the underlying standards as it runs.
242SKILL.mdUpdated Jun 4, 2026
glebis/job-babysitter
development
VerifiedTrustedCommunity
This skill should be used to watch a long-running background job (ffmpeg/media encode, qmd or other embedding/vector-DB run, batch agent/LLM pipeline, or a real-browser/agent-browser daemon) until it finishes or wedges, then deliver a verdict (done, needs-attention, or blocked) plus the exact next command, without burning dozens of manual poll commands. Triggers on "babysit this job", "watch this until it's done", "ping me when the encode/embed/batch finishes", "is this background process stuck", "monitor this ffmpeg/qmd run", or any request to wait on a long-running process and be told when it's complete or hung.
242SKILL.mdUpdated Jun 4, 2026
glebis/peer-agent-collaboration
development
VerifiedTrustedCommunity
Use when the user wants Claude Code, Codex, or other AI coding/business agents to work together as peers. This skill should be used whenever the user mentions coordinating Claude Code and Codex, agent handoffs, multi-agent workflows, parity, respect, pushback between agents, deciding which agent should lead, or turning a business/code workflow into a two-agent operating model.
242SKILL.mdUpdated Jun 4, 2026