compile

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

Quality

83%

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

88%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 highly actionable, well-structured skill body with copy-paste commands for every variant and a genuine error-recovery loop for javadoc failures. The main improvement is trimming duplicated content between the 'all' command and the CI reference section, and considering a reference file if the javadoc detail grows.

Suggestions

Deduplicate the CI reference section — the 'dist-tar' job command is byte-identical to the 'all' command; a one-line note ('CI runs the same command as `all`') would save ~10 lines.

If the javadoc error table and heading rules grow, move them to a references/javadoc.md file and keep a pointer plus the most common error inline.

Trim the heading-nesting rationale sentence ('The generated javadoc page uses <h1>...') to one clause; the table already conveys the rule.

Dimension	Reasoning	Score
Conciseness	The body is dominated by executable commands and tables, and its explanatory content (JDK 13+ heading rules, the Maven [ERROR]-prefix quirk) is genuinely non-obvious. Minor over-explanation remains: the CI reference section repeats the identical 'all' command verbatim, and the heading-nesting rationale sentence could be trimmed — anchor 4, not 3 (mostly efficient) nor 5 (duplication exists).	4 / 5
Actionability	Every argument variant has a copy-paste-ready Maven command, and the common-javadoc-errors table maps each error to a concrete fix (e.g., "Use {@code ->} or ->"). Commands cover all the common cases (all, backend, javadoc, checkstyle, module), matching anchor 5.	5 / 5
Workflow Clarity	Per-argument dispatch is unambiguous, the critical ordering constraint is explicit ("Running javadoc:javadoc alone without install will miss errors"), and the output-reading section plus error/fix table forms an error-recovery feedback loop. No destructive or batch operations, so the validation-cap rule does not apply; this matches anchor 5's explicit validation and feedback loops.	5 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is well-organized with clear section headers. It exceeds the ~50-line simple-skill exception, and the javadoc error/heading-rule reference material is inlined, so anchor 4 ('good structure, minor organization gaps') fits better than 5.	4 / 5
	Total	18 / 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 strong, specific description in third person that clearly states what the skill does and when to use it. The trigger coverage is good but could add common synonyms like "compile" and "CI checks".

Suggestions

Add trigger synonyms such as "compile", "lint", or "CI checks" so the description fires on more of the phrases users naturally say.

Mention the single-module build capability (e.g., "or build a single module by name") to make the what-clause fully comprehensive.

Dimension	Reasoning	Score
Specificity	Third-person description lists three concrete actions ("Build SkyWalking OAP server, run javadoc checks, and verify checkstyle") with minor gaps — single-module builds and the ui/dist profile variants from the body are not mentioned. It lists several specific actions but is not fully comprehensive, matching anchor 4 rather than 5.	4 / 5
Completeness	Both what and when are explicit ("Use to validate changes before submitting a PR"), but the when clause offers only a single trigger phrase, matching anchor 4's 'when could be more explicit or specific' rather than anchor 5's multiple concrete trigger phrases.	4 / 5
Trigger Term Quality	Good natural keyword coverage: "build", "javadoc", "checkstyle", "OAP server", "validate changes", "PR" are phrases users would plausibly say. A few natural synonyms are missing (e.g., "compile", "lint", "CI checks"), so it fits anchor 4 rather than 5 and is clearly above anchor 3's partial coverage.	4 / 5
Distinctiveness Conflict Risk	Names a specific project (SkyWalking OAP) and specific tools (javadoc, checkstyle), giving it a clear niche with distinct triggers and minimal conflict risk with other skills.	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: 0a01d89

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.