BD ios-dev-skill
iOS/macOS 开发技能(SwiftUI + UIKit)与 Swift 6.3 语言权威参考合集。覆盖 MVVM/Cocoa 架构、 网络层(URLSession/async-await)、状态管理(@State/@Published/Combine)、依赖注入、 Navigation、性能优化、单元测试/UI 测试、持久化、App 分发,以及 Swift 完整语法 (类型系统/集合/闭包/协议/泛型/并发)。当用户询问 iOS 开发、SwiftUI、Swift 语法、 Swift 语言任何相关内容时触发。
As a process D 40/100 · Unfinished process — 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.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 18. 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") - warning
body-longSKILL.md body ≈ 11684 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "trigger" - note
frontmatter-keyunknown frontmatter key "hermes"
Process rating: all ten parameters 40/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
- 30Running it twice. 42 mutating operations with no state check
- 40Execution cost. Instruction body is 11684 tokens: crowds the task out of the window
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 100Steps. 18 steps
- 100Consistency. Name and required fields are in place
- low The response is described with custom markup (5 tags): a typed call is more reliable
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
- -220 emoji in the instructions: noise for the model
- +2Single-language instructions
- +3Description length 259: enough signal without eating the budget
- +4Structure: 43 headings
- +3Step-by-step instructions: 18 items
- +4Has examples (82 code blocks)
- +4Reference files are cited in the instructions (3 of 15)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.