CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

test-macos-app

Slash command that runs the smallest meaningful macOS test scope first and explains failures by category. Invoke explicitly with /test-macos-app — this skill never self-triggers.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/test-macos-app/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 lean skill body: well-organized, no padding, honest scope, and clear sequencing with sensible guardrails. Its one real weakness is actionability — the workflow names tools and categories but never shows an actual command, leaving the executor to reconstruct xcodebuild/swift test invocations on its own.

Suggestions

Add one or two copy-paste-ready command templates under Workflow, e.g. 'xcodebuild test -scheme <scheme> -only-testing:<target>/<class>' and 'swift test --filter <pattern>', so focused execution is executable rather than inferred.

Insert an explicit validation/feedback step, e.g. 'Re-run only the failing test to confirm it reproduces before classifying it as a real failure vs. flake', to close the minor checkpoint gap in the workflow.

For step 1, give the concrete detection cue (e.g. 'Package.swift present → swift test; .xcodeproj/xcworkspace present → xcodebuild test') instead of leaving the detection method unstated.

DimensionReasoningScore

Conciseness

The ~25-line body is lean with zero padding: every line is either an argument definition, a workflow step, or a guardrail ('Detect whether the repo uses `xcodebuild test` or `swift test`', 'Avoid rerunning the full suite if a focused rerun is possible'), and no concepts Claude already knows are re-explained. It fully matches 'lean and efficient; assumes Claude's competence; every token earns its place' — the only near-redundancy, the one-line summary repeating the description, is negligible.

5 / 5

Actionability

Guidance is directionally concrete — named tools ('xcodebuild test', 'swift test'), a concrete failure taxonomy ('compile, assertion, crash, env/setup, or flake'), and explicit arguments — but no executable commands or examples are given (no 'xcodebuild test -scheme X -only-testing:...' or 'swift test --filter'), so key execution details are missing. This sits at 'some concrete guidance but incomplete ... missing key details', above the vague-hints level of 2 because the tools, categories, and parameters are specifically named.

3 / 5

Workflow Clarity

The four-step sequence (detect runner → prefer focused execution → classify failures → summarize blocker and next step) is clear and coherent, and the guardrails supply decision checkpoints ('Distinguish build failures from actual failing tests', 'Avoid rerunning the full suite if a focused rerun is possible'), fitting 'clear sequence with most checkpoints present; minor validation gaps'. It is not a 5 because there are no explicit feedback-loop steps (e.g., re-run the focused failing test to confirm flake vs. real failure) and not a 3 because the checkpoints are stated rather than merely implicit, though they are phrased as principles rather than inline validation steps.

4 / 5

Progressive Disclosure

The skill has no bundle files (references/, scripts/, assets/ are absent) and the body is under 50 lines, so the simple-skill exception applies: well-organized sections (Arguments, Workflow, Guardrails) with no content that belongs in a separate file. Per the guideline 'for skills under 50 lines with no need for external references, progressive disclosure can score 5 with just well-organized sections', this earns a 5.

5 / 5

Total

17

/

20

Passed

Description

62%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 concise, honest description that clearly states what the skill does and how it must be invoked, with the never-self-triggers note being a genuine strength for a slash-command skill. Its main gaps are thin natural-language trigger coverage (no 'Xcode', 'unit tests', 'test suite' style phrases) and only two explicitly stated capabilities.

Suggestions

Broaden natural trigger terms, e.g. 'Use when asked to run or triage tests for a macOS app, Xcode scheme, or Swift package' so users' phrasings match without the literal slash command.

Name one or two more concrete capabilities in the description itself (e.g., focused reruns via -only-testing/--filter, classifying failures as compile/assertion/crash/env/flake) to lift specificity from 1-2 actions to several.

DimensionReasoningScore

Specificity

The description names the domain ("macOS test scope") and two concrete actions ("runs the smallest meaningful macOS test scope first" and "explains failures by category"), matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor. It is not a 4 because it does not list several specific actions (e.g., focused test selection, failure triage, next-step recommendation are only implied by the body), and not a 2 because the actions stated go beyond a bare domain mention like 'Processes PDF files'.

3 / 5

Completeness

Both parts are explicitly answered: the 'what' is 'runs the smallest meaningful macOS test scope first and explains failures by category', and the 'when' is explicit invocation guidance ('Invoke explicitly with /test-macos-app — this skill never self-triggers'), so the missing-'Use when' cap of 3 does not apply. It is not a 5 because the 'when' states only the invocation mechanism rather than concrete situations in which the skill applies (e.g., 'when the user wants to run macOS/Xcode tests').

4 / 5

Trigger Term Quality

Relevant keywords are present ("macOS", "test", "failures", "/test-macos-app") but common variations a user would naturally say — "Xcode", "unit tests", "swift test", "test suite" — are missing, fitting 'some relevant keywords but missing common variations or synonyms'. Not a 4 because the natural-phrase coverage is thin beyond the literal slash-command name, and not a 2 because the terms given are domain-specific rather than generic filler.

3 / 5

Distinctiveness Conflict Risk

The macOS-app-testing niche plus 'smallest test scope first' and 'failures by category' gives it a clear identity, and the 'never self-triggers' statement eliminates accidental auto-invocation, leaving only minor overlap risk with general test-running skills — matching 'mostly distinct; minor overlap risk'. Not a 5 because it shares trigger territory (testing, failures) with broader testing skills and does not carve out, e.g., iOS-only or generic CI testing.

4 / 5

Total

14

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

robinebers/openusage

Path

.agents/skills/test-macos-app/SKILL.md

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.