staticphp-build-troubleshooting

Diagnose StaticPHP v3 failures. Use when investigating build, compile, linker, download, doctor, environment, CI, smoke-test, terminal output, spc.output.log, spc.shell.log, config.log, CMake logs, or user-provided error snippets from StaticPHP commands.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An efficient, highly actionable troubleshooting skill with a sequenced diagnostic workflow, a guardrail around destructive cache clearing, and a well-signaled single-level reference split. It respects token budget while giving copy-paste commands and precise file paths throughout.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: it never explains what StaticPHP or a compiler is, and every section (Overview, First Pass, Diagnosis Rules, Repro Commands, Fix Direction, Resources) earns its place.	3 / 3
Actionability	Copy-paste-ready repro commands (e.g. 'php bin/spc doctor -vvv', 'php bin/spc build:libs "openssl" -vvv') plus concrete file paths and a precise log-inspection order give fully executable, specific guidance.	3 / 3
Workflow Clarity	The 'First Pass' is a clearly sequenced four-step checklist with a routing table in 'Fix Direction', and it includes an explicit checkpoint around the destructive 'spc reset --with-download --yes' (ask before clearing caches).	3 / 3
Progressive Disclosure	SKILL.md is a concise overview that delegates detailed pattern matching and likely fixes to the one-level-deep, clearly signaled 'references/log-triage.md' (verified to exist), with the split being appropriate for an under-50-line skill.	3 / 3
	Total	12 / 12 Passed

Description

90%

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 well-crafted description that pairs a concrete diagnostic purpose with an explicit, trigger-rich 'Use when' clause in third-person voice. The only minor gap is that it states one diagnostic action rather than a range of distinct concrete actions.

Dimension	Reasoning	Score
Specificity	Names a concrete domain and a single diagnostic action ("Diagnose StaticPHP v3 failures"), but does not enumerate multiple distinct concrete actions like the score-3 anchor, so it sits at the 'names domain and some actions' level.	2 / 3
Completeness	It clearly answers what ("Diagnose StaticPHP v3 failures") and when with an explicit 'Use when investigating...' trigger clause, matching the score-3 anchor exactly.	3 / 3
Trigger Term Quality	The 'Use when investigating build, compile, linker, download, doctor, environment, CI, smoke-test, terminal output' plus specific log filenames gives strong coverage of the natural terms a user would say when hitting this kind of failure.	3 / 3
Distinctiveness Conflict Risk	The narrow 'StaticPHP v3 failures' niche with distinctive log-file triggers (spc.output.log, spc.shell.log, CMake logs) makes it unlikely to fire for the wrong skill.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

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: crazywhalecc/static-php-cli
Path: .github/skills/staticphp-build-troubleshooting/SKILL.md
Commit: 59584de

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.