compile

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

Quality

75%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/compile/SKILL.md

Quality

Discovery

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a solid, concise description that clearly identifies three specific build/validation actions for the SkyWalking OAP project and provides an explicit 'when' clause. Its main weakness is that trigger terms could be broader to capture more natural user phrasings like 'compile', 'lint', or 'pull request'.

Suggestions

Expand trigger terms to include common variations like 'compile', 'lint', 'code style', 'pull request', or 'CI validation' to improve discoverability.

Dimension	Reasoning	Score
Specificity	Lists three specific concrete actions: 'Build SkyWalking OAP server', 'run javadoc checks', and 'verify checkstyle'. These are clear, actionable tasks.	3 / 3
Completeness	Clearly answers 'what' (build OAP server, run javadoc checks, verify checkstyle) and 'when' ('Use to validate changes before submitting a PR'), providing an explicit trigger scenario.	3 / 3
Trigger Term Quality	Includes relevant terms like 'SkyWalking', 'OAP server', 'javadoc', 'checkstyle', and 'PR', but misses common variations users might say such as 'build', 'compile', 'lint', 'code style', 'pull request', or 'CI checks'.	2 / 3
Distinctiveness Conflict Risk	Highly specific to the SkyWalking OAP project with distinct triggers (SkyWalking, OAP server, javadoc, checkstyle). Very unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Implementation

64%

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

This is a solid, actionable skill with concrete commands and useful project-specific knowledge (javadoc error interpretation, heading rules). Its main weaknesses are the lack of an explicit end-to-end verification workflow with validation checkpoints, and some redundancy in the command listings. The javadoc reference material is valuable but could benefit from being split into a separate file.

Suggestions

Add an explicit end-to-end pre-PR workflow with numbered steps and validation checkpoints, e.g., '1. Run full build → 2. Check for javadoc errors (only `error:` lines) → 3. Run checkstyle → 4. Fix any issues and re-run failed step'

Deduplicate the 'all' and 'javadoc' commands — note that they're identical and explain when you'd use one vs the other, or consolidate them

Consider moving the javadoc heading rules and common errors tables to a separate JAVADOC_REFERENCE.md to keep the main skill focused on the build workflow

Dimension	Reasoning	Score
Conciseness	Generally efficient but includes some redundancy — the 'all' and 'javadoc' commands are identical and listed twice. The javadoc heading rules and error table are useful project-specific knowledge Claude wouldn't have, but the prerequisites section explains basics Claude already knows (what LTS versions are, what a Maven wrapper is).	2 / 3
Actionability	Provides fully executable, copy-paste-ready Maven commands for each scenario. The error table with specific fixes and the heading rules table give concrete, actionable guidance for resolving common issues.	3 / 3
Workflow Clarity	Commands are clearly organized by use case, and the javadoc dependency on `install` is explicitly called out. However, there's no explicit validation workflow — no sequence like 'build → check output → fix → rebuild' with feedback loops, which matters for a pre-PR verification skill involving multiple checks (build + javadoc + checkstyle).	2 / 3
Progressive Disclosure	Content is well-structured with clear sections and headers, but it's somewhat long for a single file with no references to supporting documents. The javadoc heading rules and error tables could be split into a reference file, keeping the main skill focused on the build workflow.	2 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: apache/skywalking
Commit: bf0fe4b

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