CtrlK
BlogDocsLog inGet started
Tessl Logo

test-triage

Triage failing macOS tests across Xcode and SwiftPM workflows. Use when asked to run macOS tests, narrow failing scopes, explain assertion or crash failures, or separate real test regressions from setup and environment problems.

64

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-triage/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

70%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 is exceptionally concise and well-structured for a simple skill, but its actionability and workflow clarity are limited by the absence of executable commands and explicit verification checkpoints around batch reruns.

Suggestions

Add concrete example commands for the rerun step (e.g., `xcodebuild test -only-testing:TargetSuite/TestClass/testCase` and the SwiftPM equivalent) to lift actionability.

Insert an explicit verification checkpoint before narrowing scope or rerunning (e.g., rerun the single failing case once to confirm it is stable before treating it as a regression) to satisfy the batch-operation feedback-loop requirement.

Give one concrete example per failure category (assertion vs. crash vs. flake) so classification guidance is copy-paste ready rather than abstract.

DimensionReasoningScore

Conciseness

Lean throughout: short bullets and minimal prose with no padding and no explanation of concepts Claude already knows; every line earns its place.

5 / 5

Actionability

Gives concrete tool names ('xcodebuild test', 'swift test') but the workflow is mostly high-level direction with no executable commands for classification/rerun steps; guidance is actionable in intent but light on copy-paste-ready specifics.

3 / 5

Workflow Clarity

A clear five-step sequence exists, but the cap applies: rerunning tests is a batch operation and there are no explicit validation/verification checkpoints (e.g., confirm a failure is stable before narrowing), so workflow clarity cannot exceed 3.

3 / 5

Progressive Disclosure

A short, well-sectioned single-purpose skill under 50 lines with no external references needed; structure (Quick Start, Workflow, Guardrails, Output Expectations) is clean and easy to navigate, qualifying for the simple-skill top score.

5 / 5

Total

16

/

20

Passed

Description

83%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 specific, action-oriented, and clearly pairs a 'what' with an explicit 'Use when...' trigger clause. It is a strong, well-targeted description with only minor synonym/coverage gaps.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('run macOS tests, narrow failing scopes, explain assertion or crash failures, separate real test regressions from setup and environment problems'), with minor coverage gaps (e.g., no mention of producing reports).

4 / 5

Completeness

Explicitly answers both what ('Triage failing macOS tests across Xcode and SwiftPM workflows') and when ('Use when asked to run macOS tests, narrow failing scopes, explain assertion or crash failures...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user phrases like 'asked to run macOS tests', 'explain assertion or crash failures', and 'failing scopes'; a few common synonyms (e.g., 'Xcode tests', 'CI failures') are absent.

4 / 5

Distinctiveness Conflict Risk

The macOS/Xcode/SwiftPM test-triage niche is fairly distinct, with only minor overlap risk against a generic test-running skill.

4 / 5

Total

17

/

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.