Software architecture and design records: system structure and styles, C4 views, quality-attribute trade-offs, internal module boundaries, coupling and cohesion, Architecture Decision Records. Use when asking "how should we structure this system", "monolith or microservices", "which architecture style", "will this scale", "C4 view", "where should this code live", "this module does too much", "reduce coupling", "record this decision", "write an ADR". Not for the external API contract itself, line-level code cleanup, or drawing slide-deck diagrams; those sit outside this skill.
cp -r cryptoskill/skills/exchanges/anoscranel-ac-architecture .claude/skills/clawhub install anoscranel-ac-architectureCapabilities below are detected automatically by an open-source scanner that reads the skill's text and scripts (see how this is computed). Not measured means the scanner couldn't make a confident call — it is NOT a green check, and you should treat it as a possible red flag until a human or a stronger scanner has measured it.
read_only Phase 1 single-mode classification — multi-mode breakdown deferred to Phase 2.
We did not find any well-known hosted services in this skill's text or scripts. This does NOT mean the skill is local-only — it might use services we don't yet recognize, or talk to them through code paths our scanner can't reach. A complete dependency list (every package, library, and binary, with integrity hashes) is on the roadmap; today we only show recognized hosts.
No one has audited this skill yet. That is different from “audited and clean” — it just means no professional reviewer (a security firm, the CryptoSkill team, or a verified independent researcher) has signed off on it. There are no audit reports to read. How reviewer levels work →
SKILL.md → SOURCE.md → TRUST.auto.yaml → Browse directory →
Auto-generated by cryptoskill/extract-capabilities/0.3.1 · hosted-service list version 2026-09-06 · how this is computed