knowledge-base

Synchronize German and English knowledge base content after project updates.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/gw-ai-security/ats-cv-scorer --skill knowledge-base-gw-ai-security
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge-base
Source: https://github.com/gw-ai-security/ats-cv-scorer/tree/main/.codex/skills/knowledge-base
Command: npx skills add https://github.com/gw-ai-security/ats-cv-scorer --skill knowledge-base-gw-ai-security

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps the ATS CV Scorer knowledge base up to date in both German and English, ensuring consistency after updates.

Core Features & Use Cases

  • Mirror DE/EN content after changes in project docs and snapshots.
  • Update Last Updated timestamps and ensure navigation consistency across INDEX.md files.
  • Link repo artifacts without duplicating content.

Quick Start

Update both language versions by reviewing the latest project snapshot and mirroring changes to docs/knowledge_base/de/ and docs/knowledge_base/en/.

Frequently Asked Questions about knowledge-base

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I synchronize a bilingual knowledge base after updating project documentation?

To synchronize a bilingual knowledge base, review the latest project snapshot and mirror content changes across both language directories, ensuring mirrored content, correct references, and consistent navigation in both index files.

What is the best way to maintain cross-language consistency in project snapshots?

Maintaining cross-language consistency requires mirroring updates across DE/EN directories after changes occur in architecture, quality, or evaluation docs, ensuring both language versions reflect identical project snapshots and updated timestamps.

How do I update Last Updated timestamps and index navigation for a multi-language knowledge base?

Updating Last Updated timestamps and navigation involves validating both INDEX.md files after mirroring content, ensuring correct cross-language references and synchronized timestamps across all mirrored knowledge base entries.

Do I need to duplicate content when linking repo artifacts in a bilingual knowledge base?

No, you do not need to duplicate content when linking repo artifacts; the knowledge base synchronization links repository artifacts directly within the mirrored DE/EN docs without duplicating the underlying content.

When should I update mirrored DE/EN documentation directories?

You should update mirrored DE/EN documentation directories whenever changes occur in requirements, architecture, quality, evaluation docs, skills, phase plans, or when new project snapshots are generated.

Why does my knowledge base navigation break after cross-language updates?

Knowledge base navigation breaks when index files are not validated after cross-language updates; synchronizing both INDEX.md files ensures correct references and structural consistency across mirrored DE/EN content.