axiom-uikit

Use when bridging UIKit and SwiftUI, modernizing UIKit apps (scene lifecycle, resizability), debugging Auto Layout, Combine, TextKit, PencilKit, or UIKit animations.

Quality

80%

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

Quality

Content

86%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.

An exemplary progressive-disclosure router that maps concrete symptoms to precise referenced files with no padding. Its only meaningful weakness is redundancy between the dot-graph and numbered-list forms of the decision tree, which lightly costs conciseness and workflow clarity.

Suggestions

Collapse the Decision Tree into a single representation — keep either the `dot` graph or the numbered list, not both — to remove the duplicated routing and tighten conciseness.

De-duplicate the Quick Reference table against the Decision Tree so each symptom→file mapping appears once in a canonical location, improving workflow clarity.

Dimension	Reasoning	Score
Conciseness	The router body is lean, assumes Claude's competence (no UIKit primer), and uses punchy tables, but the decision tree is duplicated as both a `dot` graph and a numbered list and the Quick Reference table repeats much of the same routing, which is trimmable redundancy keeping it at 4 rather than 5.	4 / 5
Actionability	Every symptom and example invocation maps to a precise, executable target — "→ Read: `skills/uikit-bridging.md`", "Launch `resize-auditor` agent" — covering the common cases; per the instruction-skill note, the absence of inline code is not penalized because the routing guidance is fully actionable.	5 / 5
Workflow Clarity	The numbered Decision Tree (cases 0–10) and Conflict Resolution section give a clear, sequenced triage path with no destructive/batch operations requiring validation, but the two parallel decision representations (graph + list) muddy the single canonical path, so it sits at 4 rather than 5.	4 / 5
Progressive Disclosure	This is a textbook overview-router: SKILL.md stays a concise index and every detailed topic is one level deep via clearly signaled references (`skills/*.md`, the Quick Reference table, and Example Invocations), with the inline-auditor fallback noted for non-Claude-Code contexts; no bundle files exist to contradict the structure.	5 / 5
	Total	18 / 20 Passed

Description

75%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.

A focused, trigger-rich description that clearly carves out the UIKit domain and lists concrete sub-areas. It is strong across all dimensions but stops just short of the top anchor because what/when are blended rather than separately stated and a few natural synonyms are missing.

Dimension	Reasoning	Score
Specificity	Names the UIKit domain and several concrete action areas — "bridging UIKit and SwiftUI", "modernizing UIKit apps (scene lifecycle, resizability)", "debugging Auto Layout", "Combine", "TextKit", "PencilKit", "UIKit animations" — with only minor coverage gaps, matching the anchor that lists several specific actions.	4 / 5
Completeness	An explicit "Use when..." trigger clause is present and the gerund list (bridging, modernizing, debugging) conveys what the skill does, so both what and when appear; the two are fused rather than crisply separated as in the top anchor, placing it at 4 rather than 5.	4 / 5
Trigger Term Quality	Strong, natural developer keywords ("UIKit", "SwiftUI", "Auto Layout", "Combine", "TextKit", "PencilKit", "animations") that users would actually say, but a few natural synonyms/specifics (e.g. UIScene, UIHostingController, constraints) are absent, stopping short of the comprehensive-synonyms anchor.	4 / 5
Distinctiveness Conflict Risk	The UIKit niche is clear and the triggers are domain-specific, but there is nontrivial overlap with sibling SwiftUI, concurrency, and data skills (enough that the body itself carries a Conflict Resolution section), which is minor-overlap territory rather than minimal-conflict.	4 / 5
	Total	16 / 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
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: CharlesWiltgen/Axiom
Path: .claude-plugin/plugins/axiom/skills/axiom-uikit/SKILL.md
Commit: dd33347

Reviewed: 3 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.