SKILLEMALL.ai
GitHub ↗ RU Sign in

BB well-architected

6-pillar architecture review framework. Adapted from AWS Well-Architected for use by great_cto's architect agent on every non-nano ARCH document. Forces explicit answers across operational excellence, security, reliability, performance, cost, and sustainability — not just feature design.

avelikiy/great_cto Agent Skills author: avelikiy MIT 1 file body ≈ 1 388 tokens Open the sourcegithub.com↗ analyzed 11 d ago

6-pillar architecture review framework.

As a process B 72/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, running it twice

AnalyzerAWSData and analyticstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
93/100
safety, quality, tests
Safety 60%
100
Quality 40%
83
Run on models
none yet
Process rating
B
72/100
Nearly there
Inputs and preconditions w 11
0
When it triggers w 12
20
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "effort"
    • note frontmatter-key unknown frontmatter key "paths"

    Process rating: all ten parameters 72/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 2 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 100Tools and files. Tools declared in frontmatter
    • 100Steps. 46 steps
    • 100Result and completion. Output format and completion criterion are stated
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1388 tokens
    • 100Progress reporting. Reports progress

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • -228 emoji in the instructions: noise for the model
    • +1No license
    • +2Single-language instructions
    • +3Description length 288: enough signal without eating the budget
    • +4Structure: 27 headings
    • +3Step-by-step instructions: 46 items
    • +3Output format is stated explicitly
    • +4Has examples (1 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.