CtrlK
BlogDocsLog inGet started
Tessl Logo

senior-laravel-developer-phpunit-interpreter

Cleans and interprets raw PHPUnit CI logs into a compact, AI-friendly failure report. Use this skill whenever the user pastes or uploads a PHPUnit log, GitHub Actions test output, CI test results, or asks to interpret/summarize/analyze failing tests. Trigger even if the user says things like "here's my test output", "tests are failing", "can you look at my PHPUnit log", or pastes a block of text that contains PHPUnit output. Always use this skill before attempting to diagnose failures.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 a tight, actionable transformation spec with clear sequencing and concrete examples. It assumes Claude's competence and avoids fluff; the only minor weakness is partial redundancy between the Failure Formats and Output Structure sections.

DimensionReasoningScore

Conciseness

Lean, instructional prose with no padding or explanations of concepts Claude already knows; the Output Structure template partially overlaps the Failure Formats examples and could be tightened slightly.

4 / 5

Actionability

Concrete, specific guidance throughout — exact removal rules, preserved fields, and copy-ready failure-format templates leave no ambiguity about what to produce.

5 / 5

Workflow Clarity

Clearly sequenced sections (Cleanup, Path Cleanup, Stack Trace, Formats, Duplicate Removal, Formatting, Output) with a conditional output checkpoint; no explicit validate-fix-retry loop, but none is needed for a deterministic one-pass transform.

4 / 5

Progressive Disclosure

Single self-contained file with well-organized section headers and no nested references; at ~180 lines it slightly exceeds the simple-skill threshold, and a couple of template sections could conceptually live in a reference file.

4 / 5

Total

17

/

20

Passed

Description

95%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 strong, with explicit what/when structure, comprehensive natural trigger phrases, and a well-defined niche. The only minor gap is that the capability list is condensed into two verbs rather than enumerating several distinct actions.

DimensionReasoningScore

Specificity

Names the domain ('raw PHPUnit CI logs') and concrete actions ('Cleans and interprets ... into a compact, AI-friendly failure report'), but the action list is limited to two verbs rather than a comprehensive enumeration.

4 / 5

Completeness

Explicitly answers both what ('Cleans and interprets raw PHPUnit CI logs into a compact, AI-friendly failure report') and when ('Use this skill whenever the user pastes or uploads ... Trigger even if the user says things like ...').

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms including synonyms and exact user phrasings ('PHPUnit log', 'GitHub Actions test output', 'CI test results', "here's my test output", 'tests are failing').

5 / 5

Distinctiveness Conflict Risk

Clear niche (PHPUnit log interpretation) with distinct, specific triggers; minimal overlap risk with unrelated skills.

5 / 5

Total

19

/

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
Bottelet/DaybydayCRM
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.