compile

Build SkyWalking OAP server, run javadoc checks, and verify checkstyle. Use to validate changes before submitting a PR.

Quality

80%

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

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.

A well-organized, highly actionable build/verify catalog with executable commands for every mode and valuable non-obvious project knowledge. The main gaps are minor command-block duplication and the absence of explicit success-check validation steps.

Suggestions

De-duplicate the repeated full-build and checkstyle command blocks — reference the canonical command from the 'all' section instead of reprinting it in the javadoc and CI sections.

Add explicit validation checkpoints after each command, e.g. 'Confirm BUILD SUCCESS' or 'Confirm 0 checkstyle violations' before treating a run as passing.

Consider moving the javadoc heading-rules and common-errors tables into a references/javadoc.md file so the main body stays a lean command overview.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Maven/build knowledge, surfacing genuinely non-obvious project specifics (delombok requirement, [ERROR]-prefix severity quirk, heading hierarchy); the only trim opportunity is verbatim duplication of the full build block in the 'all', 'javadoc', and CI sections (and the checkstyle block twice), which keeps it at anchor 4 rather than 5.	4 / 5
Actionability	Every argument mode ships a copy-paste-ready executable command, and the javadoc section pairs concrete error/warning samples with a fix table — fully executable coverage of the common cases per anchor 5.	5 / 5
Workflow Clarity	Per-mode commands are clear and the javadoc section encodes a sequence dependency (install before javadoc:javadoc) plus error-reading feedback, but there are no explicit validation checkpoints such as 'confirm BUILD SUCCESS' or '0 checkstyle violations', so it sits at anchor 4 rather than 5.	4 / 5
Progressive Disclosure	No bundle files or external references exist and the catalog is well-sectioned and self-contained, but at ~109 lines the dense javadoc heading-rules and error tables are reference material that could be split into a separate file, matching anchor 4 rather than a clean 5.	4 / 5
	Total	17 / 20 Passed

Description

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

A concise, concrete description that clearly states what the skill does and when to use it, with a distinct SkyWalking-specific niche. Its only weakness is that the 'when' clause is a purpose statement rather than richer trigger phrases, and a few natural synonyms are missing.

Suggestions

Expand the trigger clause into concrete user-facing scenarios, e.g. 'Use when the user wants to build the OAP server, run javadoc or checkstyle checks, or verify changes before a PR'.

Add common synonyms such as 'compile', 'run CI', or 'build the project' to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists three concrete actions — 'Build SkyWalking OAP server', 'run javadoc checks', 'verify checkstyle' — matching the anchor-4 example of several specific actions with minor gaps; not a 5 because per-module builds and the profile concept are absent.	4 / 5
Completeness	Both halves are present — a clear 'what' (build/javadoc/checkstyle) and an explicit 'Use to validate changes before submitting a PR' when clause — but the when is a purpose statement rather than concrete trigger phrases, so it lands at anchor 4 rather than 5.	4 / 5
Trigger Term Quality	Natural developer terms appear ('SkyWalking OAP server', 'javadoc', 'checkstyle', 'validate changes', 'submitting a PR') with good coverage, but common synonyms like 'CI', 'compile', or 'run the build' are missing, fitting anchor 4.	4 / 5
Distinctiveness Conflict Risk	The SkyWalking OAP server plus javadoc/checkstyle framing carves a clear niche with distinct triggers and minimal overlap with other skills, matching the anchor-5 example.	5 / 5
	Total	17 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: apache/skywalking
Path: .claude/skills/compile/SKILL.md
Commit: 521b2ab

Reviewed: 5 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.