ce-test-xcode

Test iOS apps in a simulator with XcodeBuildMCP. Use when iOS changes need simulator evidence before handoff.

Quality

91%

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

100%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 instruction-only skill body: concise, highly actionable, with a clear sequenced workflow, explicit validation/feedback rules, and clean one-level-deep progressive disclosure. No material weaknesses found.

Dimension	Reasoning	Score
Conciseness	Lean body that assumes Claude's competence: it states outcomes, ownership, and routing without explaining concepts Claude already knows, and every section earns its place.	5 / 5
Actionability	Concrete, specific guidance throughout: explicit reference-file routing, per-file ownership statements, and a fixed output schema with PASS/FAIL/SKIP rules, which is actionable for an instruction-only skill.	5 / 5
Workflow Clarity	A clear two-step sequence (prepare/launch then exercise/report) with explicit validation rules and a retest feedback loop ("Only an applied fix triggers rebuild and retest").	5 / 5
Progressive Disclosure	A concise overview pointing to two real, well-signaled, one-level-deep references (setup-and-build.md, test-and-report.md) with no nested indirection.	5 / 5
	Total	20 / 20 Passed

Description

82%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 strong, third-person description that explicitly pairs a concrete capability with a trigger clause, giving it a distinct niche. The only weakness is specificity, where a single action leaves the capability list non-comprehensive.

Suggestions

Add one or two more concrete actions (e.g. capture screenshots/logs, run human-verification checks) to lift specificity beyond a single named action.

Dimension	Reasoning	Score
Specificity	Names the domain and one concrete action ("Test iOS apps in a simulator with XcodeBuildMCP"), but offers only a single action rather than a comprehensive list.	3 / 5
Completeness	Explicitly answers both what ("Test iOS apps in a simulator with XcodeBuildMCP") and when ("Use when iOS changes need simulator evidence before handoff") with a concrete trigger phrase.	5 / 5
Trigger Term Quality	Good natural keywords users would say ("iOS apps", "simulator", "iOS changes") with only a few variations like "simulator evidence" missing.	4 / 5
Distinctiveness Conflict Risk	A clear niche (iOS simulator testing via XcodeBuildMCP) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 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: EveryInc/compound-engineering-plugin
Path: skills/ce-test-xcode/SKILL.md
Commit: 26bf5b1

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.