CtrlK
BlogDocsLog inGet started
Tessl Logo

macos-test-triage

Triage macOS tests across Xcode and SwiftPM. Use when narrowing failures, explaining assertions or crashes, or separating setup from regressions.

69

Quality

83%

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

The canonical home for this skill is test-triage in openai/plugins

SKILL.md
Quality
Evals
Security

Quality

Content

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

A tight, well-structured instruction skill with concrete commands and clear sequencing. Its main weakness is the absence of an explicit validation/retry feedback loop for rerun operations, which caps workflow clarity.

Suggestions

Add an explicit validation checkpoint in the rerun step, e.g. re-run the single failing case and confirm it passes before declaring a flake or a fix.

Show a concrete focused-rerun example (e.g. an xcodebuild -only-testing: filter or swift test --filter) so the 'Rerun intelligently' step is copy-paste ready.

Clarify how to distinguish a true flake from a regression (e.g. rerun-once-then-isolate) so classification and rerun steps connect with a feedback loop.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no concept over-explanation, no padding, every line (commands, categories, guardrails, output expectations) earns its place.

5 / 5

Actionability

Concrete commands ('xcodebuild test', 'swift test') and specific failure categories plus focused-rerun guidance make it mostly executable, but it lacks example flags/filters for focused reruns, a minor gap.

4 / 5

Workflow Clarity

A clear 5-step sequence is present, but the batch/rerun operation has no explicit validate→fix→retry checkpoint, and the rubric caps workflow_clarity at 3 when validation is missing from batch operations.

3 / 5

Progressive Disclosure

Under 50 lines, no external references needed, and well-organized sections (Quick Start, Workflow, Guardrails, Output Expectations) with no bundle files — the simple-skill exception applies.

5 / 5

Total

17

/

20

Passed

Description

87%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, concise description that pairs a concrete 'what' with an explicit 'Use when' trigger and a well-scoped niche. Minor keyword/synonym coverage is the only thing keeping it from a perfect specificity/trigger score.

DimensionReasoningScore

Specificity

Names the domain (macOS tests, Xcode, SwiftPM) and several concrete actions ('narrowing failures, explaining assertions or crashes, or separating setup from regressions'), with only minor coverage gaps — not a 5 because it stops short of a comprehensive action list.

4 / 5

Completeness

It clearly states what the skill does ('Triage macOS tests across Xcode and SwiftPM') and gives an explicit 'Use when' trigger with concrete phrases, matching the anchor that requires both.

5 / 5

Trigger Term Quality

Natural phrases a user would say ('narrowing failures', 'explaining assertions or crashes', 'Xcode', 'SwiftPM') are present, but it misses common synonyms and file/extension variants, keeping it below 5.

4 / 5

Distinctiveness Conflict Risk

The macOS-test-triage niche with Xcode/SwiftPM and assertion/crash/regression triggers is clearly distinct and unlikely to fire for unrelated skills.

5 / 5

Total

18

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
robinebers/openusage
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.