mobile-ios
Mobile iOS Agent. Swift/SwiftUI를 사용한 iOS 앱 개발을 담당합니다.
Install with Tessl CLI
npx tessl i github:shaul1991/shaul-agents-plugin --skill mobile-ios47
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies the technology domain (iOS with Swift/SwiftUI) but is too brief and lacks actionable detail. It fails to include explicit trigger conditions ('Use when...') and doesn't list specific capabilities beyond general 'app development'. The Korean language mixed with English terms may also limit discoverability.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about iOS apps, iPhone development, Swift code, SwiftUI views, or .swift files'
List specific concrete actions such as 'Creates SwiftUI views, implements navigation, manages app state, handles iOS APIs, configures Xcode projects'
Include common user-facing trigger terms like 'iPhone app', 'Apple app', 'Xcode', 'mobile UI' to improve discoverability
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (iOS app development) and technology stack (Swift/SwiftUI), but lacks specific concrete actions like 'build UI components', 'implement navigation', or 'handle state management'. | 2 / 3 |
Completeness | Only addresses 'what' (iOS app development with Swift/SwiftUI) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'iOS', 'Swift', 'SwiftUI', and 'app development', but missing common variations users might say like 'iPhone app', 'mobile app', 'Xcode', or '.swift files'. | 2 / 3 |
Distinctiveness Conflict Risk | The iOS/Swift/SwiftUI focus provides some distinction from general mobile or Android skills, but 'Mobile iOS Agent' is somewhat generic and could overlap with other iOS-related skills without clearer boundaries. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is extremely concise but lacks actionable content. It functions more as a role description than a skill that teaches Claude how to perform iOS development tasks. The content needs concrete code examples, specific workflows for common tasks (like setting up a SwiftUI view or configuring push notifications), and references to detailed guides.
Suggestions
Add executable Swift/SwiftUI code examples for common tasks like creating a view, making network requests, or setting up CoreData
Define step-by-step workflows for key processes like App Store deployment or push notification setup with validation checkpoints
Include references to detailed documentation files for each major responsibility (e.g., NETWORKING.md, COREDATA.md, DEPLOYMENT.md)
Add specific commands or scripts for building, testing, and deploying the iOS app
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is extremely lean with no unnecessary explanations. Every line serves a purpose - role definition, responsibilities, and output locations are stated without padding. | 3 / 3 |
Actionability | The skill provides no concrete code, commands, or executable guidance. It only lists abstract responsibilities (e.g., 'SwiftUI/UIKit UI 개발') without any specific instructions on how to perform these tasks. | 1 / 3 |
Workflow Clarity | No workflow or process is defined. The skill lists responsibilities but provides no sequence, steps, or validation checkpoints for any iOS development task. | 1 / 3 |
Progressive Disclosure | The content is well-organized with clear sections, but there are no references to detailed documentation, examples, or advanced guides that would help with the listed responsibilities. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- 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.