Enforces the Airbnb iOS Swift Style Guide on Swift code. Use this skill any time the user wants to: review Swift code for style compliance, lint or audit an iOS codebase, apply Airbnb Swift conventions to new or existing code, understand why code violates Airbnb style rules, or get corrected rewrites of Swift snippets. Triggers on any request mentioning Swift code quality, iOS code review, Airbnb style, linting Swift files, or when the user pastes Swift code and asks for feedback, fixes, or a review. Also use when the user asks to "clean up" or "format" Swift code, or asks "is this good Swift?" — even if they don't mention Airbnb by name.
94
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Quality
Discovery
100%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 an excellent skill description that clearly defines its scope (Airbnb iOS Swift Style Guide enforcement), lists multiple concrete actions, and provides extensive trigger term coverage including both explicit mentions and implicit user phrasings like 'clean up' or 'is this good Swift?'. It uses proper third-person voice throughout and is well-structured with distinct what/when sections.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: review Swift code for style compliance, lint or audit an iOS codebase, apply Airbnb Swift conventions, explain why code violates rules, and provide corrected rewrites of Swift snippets. | 3 / 3 |
Completeness | Clearly answers both 'what' (enforces Airbnb iOS Swift Style Guide, reviews compliance, provides corrected rewrites) and 'when' with explicit trigger guidance ('Use this skill any time...', 'Triggers on any request mentioning...', 'Also use when...'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'Swift code quality', 'iOS code review', 'Airbnb style', 'linting Swift files', 'clean up', 'format', 'is this good Swift?', 'feedback', 'fixes', 'review'. Covers both explicit and implicit user phrasings. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — scoped specifically to Airbnb's iOS Swift Style Guide, which is a clear niche. The combination of 'Airbnb', 'Swift', and 'style guide' makes it very unlikely to conflict with general code review or formatting skills. | 3 / 3 |
Total | 12 / 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 skill that provides clear, actionable guidance for enforcing the Airbnb Swift Style Guide. Its strengths are the concrete output format, decision tree for request routing, comprehensive quick-reference table, and clean progressive disclosure to the full rules file. Minor verbosity in the introductory sections and philosophy blurb could be trimmed, but overall the content is high quality.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary content. The 'How to handle a request' section explains workflow routing that Claude can infer, and the 'Philosophy' section adds context Claude doesn't strictly need. However, the rules table and output format are dense and useful. | 2 / 3 |
Actionability | The skill provides a concrete output format template, a decision tree for handling different request types, a comprehensive quick-reference rules table with specific examples (e.g., `didTapButton()` not `handleSave`), and clear instructions for each mode (review, rewrite, explain). The guidance is specific and directly executable. | 3 / 3 |
Workflow Clarity | The decision tree clearly sequences what to do for each type of request. The review workflow has explicit steps: read rules.md first, go line-by-line, group by category, quote offending code + name rule + show fix. The rewrite workflow specifies applying rules silently then summarizing changes. Each path is unambiguous. | 3 / 3 |
Progressive Disclosure | The skill provides a concise overview with key rules inline for quick reference, while pointing to `references/rules.md` for the complete rule catalog. This is a clean one-level-deep reference structure with clear signaling about when to consult the detailed file. | 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.
7bd3f9f
Table of Contents
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.