BC cloud-architect-design
云架构师专业版 —— 面向企业团队与架构师的高级云架构设计平台。核心能力: - 多云架构策略：AWS+Azure+GCP跨云架构设计与容灾方案 - 云迁移规划：本地到云、云到云的完整迁移路线图 - FinOps成本优化：深度成本分析与节省计划制定 - 合规架构设计：满足等保、GDPR、HIPAA等合规要求 - 灾难恢复方案：RPO/RTO规划与多区域灾备设计 - 架构评审与治理：架构决策记录(ADR)与治理框架 - 微服务架构设计：服务拆分、API网关、服务网格方案 - 性能工程：容量规划、性能基准与扩展策略 -...
云架构师专业版 —— 面向企业团队与架构师的高级云架构设计平台。核心能力: - 多云架构策略：AWS+Azure+GCP跨云架构设计与容灾方案 - 云迁移规划：本地到云、云到云的完整迁移路线图 - FinOps成本优化：深度成本分析与节省计划制定 - 合规架构设计：满足等保、GDPR、HIPAA等合规要求 -…
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "edition" - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "suggested_price" - note
frontmatter-keyunknown frontmatter key "pricing_tier" - note
frontmatter-keyunknown frontmatter key "pricing_model"
Process rating: all ten parameters 53/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 18 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2238 tokens
- 100Running it twice. No mutating operations
- low 12 top-level sections: this looks like several domains in one skill
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)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 262: enough signal without eating the budget
- +4Structure: 35 headings
- +3Step-by-step instructions: 18 items
- +4Has examples (11 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.