Name: ios-developer
Rating: 40 (1 reviews)
Author: administrakt0r

ios-developer

Develop native iOS applications with Swift/SwiftUI. Masters iOS 18, SwiftUI, UIKit integration, Core Data, networking, and App Store optimization.

Quality

39%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/ios-developer/SKILL.md

The canonical home for this skill is ios-developer in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

17%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body functions as a persona/capability manifesto rather than actionable guidance: it enumerates domain knowledge Claude already has, provides no executable code or commands, lacks validation-backed workflows, and references a playbook file that does not exist.

Suggestions

Replace the capability-knowledge bullets with concise, executable guidance: representative Swift/SwiftUI code snippets, concrete Xcode commands, and copy-paste patterns for the common cases.

Add a real multi-step workflow with validation checkpoints (e.g., build -> test -> Instruments profile -> fix -> re-validate) instead of the abstract 'Response Approach' list.

Move the long capability catalog into a real reference file under references/ and link to it one level deep, or trim it to a short overview so SKILL.md stops restating knowledge Claude already has.

Dimension	Reasoning	Score
Conciseness	The body is a ~210-line catalog of capability bullets (e.g., "State management with @State, @Binding, @ObservedObject", "XCTest framework for unit and integration testing") that extensively restates iOS/Swift knowledge Claude already has, with several padded sections.	2 / 5
Actionability	There is no executable code or commands anywhere; guidance is abstract ("Provide production-ready Swift code", "Apply relevant best practices and validate outcomes"), and the single referenced file `resources/implementation-playbook.md` does not exist, so it only describes rather than instructs.	1 / 5
Workflow Clarity	"Response Approach" offers a rough 8-step sequence, but steps are high-level and abstract with no validation checkpoints or feedback loops, and the "Instructions" mention of "validate outcomes" is vague.	2 / 5
Progressive Disclosure	Section headers provide minimal structure, but the large capability catalog that belongs in separate reference files is inlined into SKILL.md, and the only reference (`resources/implementation-playbook.md`) is a dangling path with no corresponding bundle file.	2 / 5
	Total	7 / 20 Passed

Description

61%Weight 40%Scale 1-5

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 is clearly scoped to native iOS development with good natural keyword coverage, but it lacks an explicit "Use when..." trigger clause and leans on a technology list rather than a comprehensive set of concrete actions.

Suggestions

Add an explicit 'Use when...' clause naming concrete user triggers (e.g., 'Use when building or debugging native iOS apps in Swift/SwiftUI, integrating UIKit, or preparing App Store submissions').

Replace some capability nouns with concrete action verbs (e.g., 'Architect MVVM apps', 'Profile with Instruments', 'Persist data with Core Data/SwiftData') to raise specificity.

Include common synonyms and file extensions (.swift, .xcodeproj, Swift packages) to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the iOS domain and several concrete technologies ("Swift/SwiftUI", "UIKit integration", "Core Data", "networking", "App Store optimization"), but only two genuine action verbs ("Develop", "Masters"), so the concrete-action coverage is limited rather than comprehensive.	3 / 5
Completeness	It clearly states what the skill does ("Develop native iOS applications...") but provides no "Use when..." clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Natural terms a user would say (Swift, SwiftUI, iOS 18, UIKit, Core Data) are well represented, but file extensions and common synonyms (.swift, .xcodeproj, Xcode) are missing, keeping it just short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	The iOS-native framing is a clear niche with distinct triggers, but broad terms like "networking" and "App Store optimization" create minor overlap risk with adjacent mobile/DevOps skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/ios-developer/SKILL.md
Commit: 57c135b

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.