How do I install the X9 Architecture Scout skill?

Run npx skillmds@latest add xonika9/x9-architecture-scout in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is X9 Architecture Scout safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with X9 Architecture Scout?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is X9 Architecture Scout free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published X9 Architecture Scout?

xonika9 (@xonika9) published this skill. Their other Agent Skills are listed on their SkillMD profile.

X9 Architecture Scout by xonika9 — Agent Skill

Name: X9 Architecture Scout
Author: xonika9

X9 Architecture Scout

Use when the user asks for a read-only architecture audit that compares plausible directions and makes component boundaries, dependencies, ownership, coupling, or change hotspots visible — «проведи архитектурный аудит», «покажи проблемные места архитектуры», "audit this codebase architecture". Do not use to implement a refactor, create a general implementation plan, or merely explain one file.

xonika9 Updated Sep 17, 2026

File contents

Architecture scout

Produce a read-only architecture report for a repository or user-named subsystem. This skill is model-invoked in Claude Code and Codex; its portable claim is structural Agent Skills compatibility only. Evidence tier: static.

Inspect component boundaries, dependency direction, ownership of data and behavior, coupling, duplication, change hotspots, and seams. Treat source, configuration, tests, and version history as evidence; distinguish observed facts from inferences. Do not edit production code, refactor, install dependencies, copy an external skill, or change external systems.

Method

Discover codebase-design from the live current-runtime catalog before any project or user/plugin roots that runtime declares. Resolve candidate paths symlink-aware, read the live skill version when one is found, and do not retain, reproduce, or hard-code its machine path. Use its method only to enrich the audit.

If no readable live codebase-design is found, perform the direct baseline audit and mark the method status DEGRADED. If the user requires Matt's exact method, stop with method status BLOCKED; do not substitute an invented version. Read the report contract before creating an HTML report; read x9-diagrams' Mermaid and design references when a diagram is needed.

Follow the repository's report-location convention. When it has none, write one HTML file at docs/architecture-reviews/YYYY-MM-DD-<stable-slug>.html. A same-day fallback audit must not silently replace a prior report: re-read and replace a named existing report only for an explicit update; otherwise choose a non-colliding stable suffix or path, or ask one short question when the report identity matters. The report may recommend a candidate, but it does not implement it; after a selection, hand the decision to ce-plan when available or provide a portable planning handoff.

Evidence and handoff

Run python3 scripts/validate_report.py <report.html> from this skill directory against the actual report. It proves structural and accessibility-contract compliance only. Keep the validator result separate from the actual render status: only a browser check at 1280px and 390px can make rendering PASS; otherwise state DEGRADED or NOT_PROVEN with the missing evidence.

Completion is one report that validates and makes the decision question, method/structure/render statuses, conclusion with confidence, candidate comparison, evidence, diagrams, risks, and next step inspectable without JavaScript. Report the artifact path, all three statuses, source scope, principal evidence, and the planning handoff or blocker.

The onboarding declaration lists external prerequisites.

---name: x9-architecture-scoutdescription: Use when the user asks for a read-only architecture audit that compares plausible directions and makes component boundaries, dependencies, ownership, coupling, or change hotspots visible — «проведи архитектурный аудит», «покажи проблемные места архитектуры», "audit this codebase architecture". Do not use to implement a refactor, create a general implementation plan, or merely explain one file.---# Architecture scoutProduce a read-only architecture report for a repository or user-named subsystem. This skill is model-invoked in Claude Code and Codex; its portable claim is structural Agent Skills compatibility only. Evidence tier: static.Inspect component boundaries, dependency direction, ownership of data and behavior, coupling, duplication, change hotspots, and seams. Treat source, configuration, tests, and version history as evidence; distinguish observed facts from inferences. Do not edit production code, refactor, install dependencies, copy an external skill, or change external systems.## MethodDiscover `codebase-design` from the live current-runtime catalog before any project or user/plugin roots that runtime declares. Resolve candidate paths symlink-aware, read the live skill version when one is found, and do not retain, reproduce, or hard-code its machine path. Use its method only to enrich the audit.If no readable live `codebase-design` is found, perform the direct baseline audit and mark the method status `DEGRADED`. If the user requires Matt's exact method, stop with method status `BLOCKED`; do not substitute an invented version. Read [the report contract](references/report-contract.md) before creating an HTML report; read `x9-diagrams`' Mermaid and design references when a diagram is needed.Follow the repository's report-location convention. When it has none, write one HTML file at `docs/architecture-reviews/YYYY-MM-DD-<stable-slug>.html`. A same-day fallback audit must not silently replace a prior report: re-read and replace a named existing report only for an explicit update; otherwise choose a non-colliding stable suffix or path, or ask one short question when the report identity matters. The report may recommend a candidate, but it does not implement it; after a selection, hand the decision to `ce-plan` when available or provide a portable planning handoff.## Evidence and handoffRun `python3 scripts/validate_report.py <report.html>` from this skill directory against the actual report. It proves structural and accessibility-contract compliance only. Keep the validator result separate from the actual render status: only a browser check at `1280px` and `390px` can make rendering `PASS`; otherwise state `DEGRADED` or `NOT_PROVEN` with the missing evidence.Completion is one report that validates and makes the decision question, method/structure/render statuses, conclusion with confidence, candidate comparison, evidence, diagrams, risks, and next step inspectable without JavaScript. Report the artifact path, all three statuses, source scope, principal evidence, and the planning handoff or blocker.The [onboarding declaration](references/onboarding.json) lists external prerequisites.

Frequently asked questions