build-run

Build, configure, and run rtp2httpd locally, including embedded Web UI builds and build/runtime troubleshooting. Excludes cross-compilation and deployment.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/build-run/SKILL.md

Quality

Content

93%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 content is lean, fully actionable, and well-structured with clear external references, offering copy-paste build/run/verify commands. Its only gap is the absence of a complete validate-fix-retry feedback loop for the run/verify workflow.

Dimension	Reasoning	Score
Conciseness	The body is lean and executable, assuming Claude's competence (e.g., "Reuse that environment; repeat setup only when dependencies are missing or changed") with no padding about concepts Claude already knows.	5 / 5
Actionability	Copy-paste-ready commands cover the common cases: pnpm/cmake build steps, a concrete run invocation with flags, and a curl readiness check.	5 / 5
Workflow Clarity	A clear build -> run -> verify sequence with an explicit readiness checkpoint and port-conflict guidance exists, but there is no full validate-fix-retry feedback loop, leaving minor validation gaps.	4 / 5
Progressive Disclosure	The body is a well-organized overview with clearly signaled one-level-deep references (AGENTS.md, configuration.md, url-formats.md, devlab, e2e/SKILL.md) and no nested reference chains.	5 / 5
	Total	19 / 20 Passed

Description

62%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 and clearly distinct, naming concrete build/run/troubleshooting actions for a named binary, but it lacks any explicit "Use when" trigger guidance, which caps completeness.

Suggestions

Append a "Use when..." clause naming natural trigger phrases (e.g., "Use when building or running rtp2httpd locally, debugging build failures, or rebuilding the embedded Web UI") to raise completeness.

Add natural-language synonyms users might say (e.g., "compile", "start the daemon", "local preview") alongside the technical terms.

Dimension	Reasoning	Score
Specificity	Phrases like "Build, configure, and run rtp2httpd locally" plus "embedded Web UI builds and build/runtime troubleshooting" name several concrete actions, falling just short of fully comprehensive coverage.	4 / 5
Completeness	The "what" is clearly stated, but there is no explicit "when/Use when" trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Domain keywords (build, configure, run, Web UI, troubleshooting) are present but there is no natural "Use when..." trigger phrase and common synonyms/variations are missing.	3 / 5
Distinctiveness Conflict Risk	The skill is anchored to a specific binary (rtp2httpd) with a clear niche and distinct triggers, giving minimal conflict risk with other skills.	5 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 6 suspicious	Warning

	Total	15 / 16 Passed

Repository: stackia/rtp2httpd
Path: .agents/skills/build-run/SKILL.md
Commit: f189205

Reviewed: 1 day 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.