license

Check and fix Apache 2.0 license headers and dependency licenses using skywalking-eyes. Use before submitting a PR.

Quality

92%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

100%

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

This is an excellent, well-crafted skill that is concise, actionable, and clearly structured. It provides exact commands with validation steps, includes non-obvious platform-specific caveats, and respects Claude's intelligence by avoiding unnecessary explanations. The pinned commit hash for CI parity is a particularly valuable detail.

Dimension	Reasoning	Score
Conciseness	Every section is lean and purposeful. No unnecessary explanations of what Apache 2.0 is or how license checking works conceptually. The platform artifact note is a genuinely useful non-obvious detail.	3 / 3
Actionability	Provides fully executable bash commands for each scenario (check, fix, deps), includes the exact go install command with pinned commit matching CI, and gives concrete output patterns to interpret results.	3 / 3
Workflow Clarity	Clear multi-step sequences with validation: fix is always followed by re-check, dependency resolve includes a diff-based validation step with explicit error messaging, and the platform artifact caveat provides important error recovery guidance.	3 / 3
Progressive Disclosure	For a skill of this size (~50 lines), the content is well-organized into logical sections (Steps, Rules, Installation) without needing external references. The structure is easy to navigate and appropriately scoped.	3 / 3
	Total	12 / 12 Passed

Description

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 communicates what the skill does and when to use it. It names a specific tool and specific license type, making it highly distinctive. The main weakness is that trigger term coverage could be broader to capture more natural user phrasings around license compliance.

Suggestions

Add more natural trigger terms users might say, such as 'license check', 'copyright header', 'license compliance', 'missing license', or 'SPDX header'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: 'check and fix Apache 2.0 license headers' and 'dependency licenses' using a specific tool 'skywalking-eyes'. These are clear, actionable capabilities.	3 / 3
Completeness	Clearly answers 'what' (check and fix Apache 2.0 license headers and dependency licenses using skywalking-eyes) and 'when' (before submitting a PR), providing an explicit trigger condition.	3 / 3
Trigger Term Quality	Includes relevant terms like 'license headers', 'Apache 2.0', 'dependency licenses', and 'skywalking-eyes', but misses common user variations like 'license check', 'copyright header', 'license compliance', or 'missing license'.	2 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche: Apache 2.0 license headers, skywalking-eyes tool, and dependency license checking. Unlikely to conflict with other skills due to the specific tool and domain.	3 / 3
	Total	11 / 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: 25 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.