swift-style-skill
Apply the Google Swift Style Guide to Swift code generation, review, and refactoring. Covers naming, file structure, formatting, and source-backed programming practices. Use for Google Swift compliance, not architecture, framework design, or project policy outside the guide.
88
85%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
85%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that clearly defines its scope (Google Swift Style Guide application), lists concrete actions (generation, review, refactoring), and provides explicit boundary conditions. The main weakness is that trigger terms could be broader to capture more natural user phrasings. The exclusion clause ('not architecture, framework design, or project policy') is a nice touch for reducing conflict risk.
Suggestions
Add more natural trigger term variations such as 'Swift style', 'Swift conventions', 'Swift code style', '.swift files', or 'Swift linting' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'code generation, review, and refactoring' and specifies domains covered: 'naming, file structure, formatting, and source-backed programming practices'. Also clearly scopes what it does NOT cover. | 3 / 3 |
Completeness | Clearly answers 'what' (apply Google Swift Style Guide to code generation, review, refactoring covering naming, file structure, formatting) and 'when' ('Use for Google Swift compliance, not architecture, framework design, or project policy outside the guide'). The 'Use for...' clause serves as an explicit trigger with boundary conditions. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'Swift', 'Google Swift Style Guide', 'naming', 'formatting', 'refactoring', but misses common user variations like 'Swift style', 'Swift linting', 'Swift conventions', 'code style', or '.swift files'. The phrase 'Google Swift compliance' is somewhat niche. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive by specifying 'Google Swift Style Guide' specifically, and explicitly excluding architecture, framework design, and project policy. This clearly differentiates it from general Swift coding skills, other style guides, or architecture-focused skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that efficiently defines scope, workflow modes, behavioral constraints, and core rules for Google Swift Style Guide compliance. Its main weakness is the lack of concrete code examples showing correct/incorrect patterns, which would strengthen actionability. The progressive disclosure via the routing section to four reference files is excellent.
Suggestions
Add 1-2 brief before/after Swift code examples demonstrating key rules (e.g., naming conventions, brace style) to make the core rules section more immediately actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. It assumes Claude knows Swift and doesn't explain basic concepts. Every section serves a clear purpose—scope, workflow, behavior rules, core rules, and routing—with no padding or redundant explanation. | 3 / 3 |
Actionability | The core rules are specific and concrete (e.g., '100-column limit, 2-space indentation, K&R braces'), and the workflow modes are clearly defined. However, there are no executable code examples showing correct vs incorrect Swift style, which would make the guidance more immediately actionable for generate/review/refactor tasks. | 2 / 3 |
Workflow Clarity | The four-step workflow is clearly sequenced with distinct mode outputs. The agent behavior section provides clear decision logic (e.g., when to follow this skill vs local convention). For a style-guide skill, destructive/batch operations aren't a concern, so validation checkpoints aren't needed. | 3 / 3 |
Progressive Disclosure | The routing section cleanly directs to four one-level-deep reference files organized by category. The main skill provides a concise overview of core rules while deferring detailed reference material to clearly signaled external files. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- pchelnikov/Swift-Style-Skill
- Commit
f0ad4d6
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.