mx-space-remote-translation-audit

Audit remote mx-space translation coverage and hash integrity via SSH and Docker exec.

61|1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/Innei/SKILL --skill mx-space-remote-translation-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mx-space-remote-translation-audit
Source: https://github.com/Innei/SKILL/tree/main/skills/infrastructure/mx-space-remote-translation-audit
Command: npx skills add https://github.com/Innei/SKILL --skill mx-space-remote-translation-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits remote translation state for mx-space to verify coverage, detect hash drift, and validate runtime freshness when direct Postgres access is unreliable.

Core Features & Use Cases

  • Remote SSH-based access to the swarm host to reach the translation data
  • Docker exec into the Postgres container to inspect ai_translations and translation_entries
  • Validate translation coverage, hash semantics, and runtime freshness against the current source data
  • Suited for environments migrating from MongoDB to PostgreSQL where direct DB access is limited

Quick Start

SSH into the swarm host, docker exec into the mx-core Postgres container, and run the audit queries to validate translations.

Frequently Asked Questions about mx-space-remote-translation-audit

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

FAQPage Schema
How do I audit remote mx-space translation data when direct Postgres access is unreliable?

You can audit remote mx-space translation data via SSH by connecting to the swarm host and using docker exec to inspect the Postgres container, validating translation coverage and hash integrity without direct database access.

What is translation hash drift and how do I detect it in an mx-space deployment?

Translation hash drift occurs when translations become misaligned with current source data. You detect it by running audit queries on translation_entries and ai_translations via SSH to compare hash semantics and identify gaps across languages.

Can I validate runtime freshness of ai_translations using SSH instead of a direct Postgres connection?

Yes, you can validate runtime freshness using SSH to access the swarm host, then docker exec into the mx-core Postgres container to run audit queries that check ai_translations against current source data.

How do I check translation coverage across multiple languages in a Postgres container?

You check translation coverage by using docker exec to enter the Postgres container and running audit queries on translation_entries across languages to detect gaps and verify hash integrity.

Does this SSH audit approach work for mx-space environments migrating from MongoDB to PostgreSQL?

Yes, this SSH-based audit approach is specifically suited for mx-space environments migrating from MongoDB to PostgreSQL where direct database access is limited, validating translations through container inspection.

What are the limitations of auditing translations via SSH and docker exec?

Limitations include relying on SSH access to the swarm host and requiring docker exec permissions, while documenting failure modes when translations are stale or misaligned to ensure strict semantics are observed.