test-suite-prioritizer
Orders tests so failures surface earliest — runs tests covering changed code first, historically flaky/failing tests early, and slow low-value tests last. Use when the suite is too slow to run in full on every change, when CI feedback takes too long, or when deciding what to run in a smoke-test tier.
Install with Tessl CLI
npx tessl i github:santosomar/general-secure-coding-agent-skills --skill test-suite-prioritizer100
Quality
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly articulates what the skill does (test ordering with specific prioritization strategies) and when to use it (slow suites, CI feedback delays, smoke-test decisions). It uses third person voice correctly, includes natural trigger terms developers would use, and carves out a distinct niche that won't conflict with general testing skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'runs tests covering changed code first, historically flaky/failing tests early, and slow low-value tests last' - these are clear, actionable ordering strategies. | 3 / 3 |
Completeness | Clearly answers both what ('Orders tests so failures surface earliest' with specific strategies) AND when ('Use when the suite is too slow to run in full on every change, when CI feedback takes too long, or when deciding what to run in a smoke-test tier'). | 3 / 3 |
Trigger Term Quality | Includes natural terms users would say: 'suite is too slow', 'CI feedback takes too long', 'smoke-test tier', 'run tests', 'changed code'. These match real developer vocabulary when discussing test optimization. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on test ordering/prioritization with distinct triggers around CI speed and test suite optimization. Unlikely to conflict with general testing or code quality skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that demonstrates mastery of the format. It provides a complete, actionable framework for test prioritization with concrete formulas, ecosystem-specific tooling, a detailed worked example, and clear anti-patterns. The content is dense yet readable, respecting Claude's intelligence while providing genuinely useful domain-specific knowledge.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place with actionable tables, formulas, and examples. No explanation of concepts Claude already knows (like what tests are or why fast feedback matters). The content is dense with useful information without padding. | 3 / 3 |
Actionability | Provides a concrete scoring formula, ecosystem-specific tooling commands, a worked example with actual test names and scores, and a complete output format template. The guidance is specific and executable. | 3 / 3 |
Workflow Clarity | Clear tiered execution model with explicit cutoffs and run conditions. The worked example demonstrates the complete workflow from change to priority order to run plan. The 'Do not' section provides explicit validation guardrails. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections (signals, formula, ecosystem tools, tiers, worked example, anti-patterns, output format). Content is appropriately self-contained for a skill of this scope without needing external references. | 3 / 3 |
Total | 12 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.