Critique an architecture
critique_architectureRead-onlyIdempotent
Validate your architecture design against rule-based checks to get scored findings before committing. Deterministic and free, with no model call or data storage.
Instructions
Check a design against SkeletIQ's architecture rules and get scored findings back. Deterministic and free — no model call, no credits, nothing stored. Useful on a design you drafted yourself before committing to it.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| domain | No | The design's domain — e-commerce, fintech, healthcare, saas, social, iot, gaming, infrastructure, streaming, logistics, ai-ml, search, data-analytics, content-platform, internal-tool. Worth sending: the domain is what selects the compliance frameworks to check against, and without it none apply, so no compliance finding is possible and the score comes back higher than the SkeletIQ app would show for the same design — by up to 15 points. | |
| exposure | No | Where the design runs. Worth sending: four checks — CDN, WAF, rate limiting and multi-region — ask whether traffic arriving from the public internet is handled safely, and they only apply to a system that takes any. Left unset, the design is assessed as internet-facing, which is why an air-gapped design comes back told to add a CDN. exposure_assessed says which exposure was actually used. | |
| architecture_json | No | A design to check. Free and deterministic — no model call. The shape SkeletIQ uses: title, description, components[{id,name,type,technology?}], connections[{source,target,protocol?}]. | |
| secondary_domains | No | Further domains the design spans, when it spans more than one — a multi-tenant shop that takes payments is e-commerce plus fintech and saas. These select frameworks on top of the primary domain's, so leaving them off is why a design already checked against SOC2 and SOX in the app comes back here checked against neither, and scored higher for it. frameworks_checked says which were actually used. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| findings | Yes | ||
| data_score | Yes | ||
| score_basis | Yes | This score is findings only. It is not held to a traceability ceiling, because this tool is given a design and no requirement set to trace it against. The app can show a lower number for the same stored design for exactly that reason. | |
| finding_count | Yes | ||
| security_score | Yes | ||
| compliance_note | Yes | ||
| resilience_score | Yes | ||
| exposure_assessed | Yes | The exposure this critique was actually run under. An absent or unreadable exposure is assessed as public_internet, so a value the server could not read shows up here rather than arriving silently as four extra security findings. | |
| performance_score | Yes | ||
| architecture_score | Yes | ||
| frameworks_checked | Yes | ||
| compliance_assessed | Yes | False means no compliance framework was checked, so no compliance finding was possible. |