build-run

Build, run, and configure rtp2httpd locally. Use this skill whenever the user wants to compile the project, start the daemon, pass command-line arguments, edit configuration, or troubleshoot build/runtime issues. Also activate when the user mentions cmake, build directory, rtp2httpd.conf, web-ui build, pnpm run, vite build, embedded_web_data.h, or asks how to test the service locally.

Quality

96%

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

92%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.

A strong, action-oriented SKILL.md with executable commands, tight tables, and sensible one-level references. It loses a point on workflow clarity (no explicit validate→retry loop) and progressive disclosure (the doc references are named but cannot be verified against a bundle).

Suggestions

Add an explicit validate→fix→retry loop for build failures (e.g., after `cmake --build`, on failure show how to read the error, fix, and rebuild) to reach a workflow_clarity of 5.

Complete the Troubleshooting section beyond the single 'Port in use' bullet — it trails off mid-list; add the common build/runtime failure cases and recovery steps.

Confirm the referenced docs (docs/reference/configuration.md, docs/guide/url-formats.md) exist as bundle files or are reachable, since progressive_disclosure is scored against actual reference structure.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout: tables for CMake options/CLI flags/URL formats, copy-paste commands, and no padding explaining what RTP/RTSP/HTTP or CMake are. Every section earns its tokens.	5 / 5
Actionability	Fully executable copy-paste commands for build, run, and verify, plus concrete CLI flag tables, an INI config example, and a URL-pattern table with working examples — covers the common cases precisely.	5 / 5
Workflow Clarity	Clear numbered build sequence with an explicit skip-rule ('Skip step 1 when only C code changed') and a 'Verify it works' section, but the run/build flows lack an explicit validate→fix→retry feedback loop and Troubleshooting trails off without recovery steps.	4 / 5
Progressive Disclosure	Well-organized into Build/Run/Configuration/URL formats/Verify/Troubleshooting with one-level-deep references to real files (rtp2httpd.conf, docs/reference/configuration.md, docs/guide/url-formats.md), though no bundle files exist alongside the skill to confirm deeper reference structure.	4 / 5
	Total	18 / 20 Passed

Description

100%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.

An excellent description: concise yet comprehensive, third-person, with a clear 'what' and an explicit 'Use when'/'Also activate when' trigger clause backed by natural user phrases and project-specific filenames.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'compile the project, start the daemon, pass command-line arguments, edit configuration, or troubleshoot build/runtime issues' — covering the full build/run/configure surface comprehensively.	5 / 5
Completeness	Explicitly answers 'what' (Build, run, and configure rtp2httpd locally) and 'when' ('Use this skill whenever the user wants to... Also activate when the user mentions...'), with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural user terms plus concrete file/tool triggers — 'cmake, build directory, rtp2httpd.conf, web-ui build, pnpm run, vite build, embedded_web_data.h' — with synonyms and exact filenames a user would mention.	5 / 5
Distinctiveness Conflict Risk	Tightly scoped to rtp2httpd with project-specific trigger tokens (rtp2httpd.conf, embedded_web_data.h), giving it a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	20 / 20 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: stackia/rtp2httpd
Path: .agents/skills/build-run/SKILL.md
Commit: 33fecb8

Reviewed: about 14 hours 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.