get-unpublished-changes

Compare HEAD with the latest published npm versions and list all unpublished changes by release layer. Triggers: unpublished changes, changelog, what changed, whats new.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/get-unpublished-changes/SKILL.md

Quality

Content

72%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 tight, actionable analysis skill with good structure and concrete commands, weakened mainly by the absence of a validation checkpoint in a batch-over-commits workflow. Adding an explicit verification step and the missing version-detection command would lift the weakest dimensions.

Suggestions

Add a validation checkpoint to the workflow, e.g. a final step that verifies every changed file was classified into a release layer and that no `senpi`/`pi-*` excluded paths appear in user-facing notes.

Make step 1 executable by specifying the version-detection command, e.g. `npm view oh-my-opencode version` (and the other two packages), instead of only "Detect latest published versions".

Tighten the "Explain WHY it matters (if not obvious)" directive to a single concise instruction to nudge conciseness from 4 toward 5.

Dimension	Reasoning	Score
Conciseness	The body is lean with terse directives, a compact release-layer table, and concrete output-format examples that mostly assume Claude's competence; minor framing like "Explain WHY it matters (if not obvious)" is slight over-direction that keeps it just below a 5.	4 / 5
Actionability	It gives concrete commands (`git diff v{published-version}..HEAD`), specific package names, an explicit classification procedure, and copy-ready output templates, but step 1 ("Detect latest published versions") lacks an executable command such as `npm view <pkg> version`, leaving a minor gap.	4 / 5
Workflow Clarity	Six numbered steps give a clear sequence with a defined output format, but there is no validation checkpoint confirming that every file was classified or that excluded paths did not leak into user-facing notes; for a batch analysis over all commits, the missing feedback loop caps this at 3 per the rubric.	3 / 5
Progressive Disclosure	This is a single-purpose skill under 50 lines with no need for external references, yet it is cleanly organized into labeled sections (CRITICAL, Release Layers, Steps, Output Format) with an appropriately inline table, satisfying the simple-skill exception for a 5.	5 / 5
	Total	16 / 20 Passed

Description

83%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 well-constructed description that concretely states what it does and when to use it with natural trigger phrases and a clearly distinct niche. The main improvement area is broadening trigger-term synonyms and slightly expanding capability coverage.

Dimension	Reasoning	Score
Specificity	"Compare HEAD with the latest published npm versions and list all unpublished changes by release layer" names the domain plus several concrete actions (compare, list, segment by release layer), matching the score-4 anchor with only minor coverage gaps versus the comprehensive score-5 example.	4 / 5
Completeness	It explicitly states both what ("Compare HEAD with the latest published npm versions and list all unpublished changes by release layer") and when ("Triggers: unpublished changes, changelog, what changed, whats new") with concrete trigger phrases, matching the score-5 anchor exactly.	5 / 5
Trigger Term Quality	"Triggers: unpublished changes, changelog, what changed, whats new" provides good natural-keyword coverage a user would actually say, though it omits some synonyms/variants that would push it to a 5.	4 / 5
Distinctiveness Conflict Risk	The npm/unpublished-changes-by-release-layer niche is fairly distinct with specific triggers, but "changelog"/"whats new" carry minor overlap risk with general changelog-generation skills, placing it at 4 rather than 5.	4 / 5
	Total	17 / 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: code-yeongyu/oh-my-openagent
Path: .agents/skills/get-unpublished-changes/SKILL.md
Commit: 6108673

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.