Autonomously port a module, script, CLI, or function from one language to another across the polyglot fleet — Rust, Python, Go, C++, Swift, TypeScript, JavaScript, Ruby, and Bash/Shell — preserving business logic exactly while adopting the target language's idioms, error model, concurrency shape, and toolchain, AND proving behavioural equivalence with a differential golden-I/O harness rather than eyeballing. Load when the user says "port this to <lang>", "translate to <lang>", "rewrite in <lang>", "convert this to <lang>", "reimplement <X> in <lang>", "give me the <lang> equivalent", or asks for a Rust↔Python↔Go↔Swift↔TS/JS↔Ruby↔C++ ↔Bash equivalent of existing code. Not for micro-snippets (do those inline) or behaviour-changing redesigns (that's a rewrite, clarify intent first).
Meta-router for the AgtMLS skill catalog — read this first when you are unsure which AgtMLS skill (if any) to load for a task, when several skills look like they might apply, or when onboarding to how this hub's skills and shared references fit together. Points at the cross-language-port skill for porting/translating code between languages, at project bundles (e.g. the noyalib/ family) for project-specific work, and at references/ for the shared Definition of Done. Use when the question is "which skill do I use for X" or "how do AgtMLS skills work".
Use when the user needs this reusable workflow. Replace this with trigger-rich wording that says when to load the skill, what task it handles, and when not to use it.
Use when preparing a pull request, reviewing implementation risk, writing release notes, checking CI, packaging artifacts, or deciding whether a repository is ready to ship.
Use when turning repeated agent work into a loop with trigger conditions, evidence, stopping criteria, uninstall state, validation checks, and reviewable artifacts.
Use when auditing AI-agent supply chain risk, prompt or skill provenance, dependency trust, SBOM/SLSA evidence, MCP tool-poisoning, package provenance, or agent runtime guardrails before release.
Use when gathering current web evidence, comparing sources, triaging credibility, reading GitHub repositories, checking docs, or deciding whether a claim needs live verification.
Maintain noyalib's docs of record and house writing style. Use when authoring or editing README, CHANGELOG, RELEASE-NOTES-vX.Y.Z.md, ADRs under doc/adr/, doc/POLICIES.md, doc/ARCHITECTURE.md, doc/USER-GUIDE.md, GLOSSARY.md, MIGRATION*.md, GETTING_STARTED.md, or crate-level and item-level rustdoc. Covers house rustdoc style (# Examples,