CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wiki-changelog

Generate structured changelogs from git history. Use when user asks "what changed recently", "generate a changelog", "summarize commits" or user wants to understand recent development activity.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/wiki-changelog/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 compact, reasonably structured instruction-only skill whose main deficits are a duplicated, filler-padded section and the absence of executable specifics (git commands, an example changelog format). The workflow itself is clear and appropriately sequenced for a read-only task.

Suggestions

Delete the duplicate "When to Use" section at the end, including the vacuous sentence "This skill is applicable to execute the workflow or actions described in the overview."

Add a concrete git command per step, e.g. `git log --since="7 days ago" --pretty=format:"%h %ad %an %s"` for the examination step.

Include a short example of the expected changelog output format (period heading, categorized entries with the emoji prefixes) so generation is unambiguous.

DimensionReasoningScore

Conciseness

The body is mostly lean, but the "When to Use" section is duplicated verbatim and closes with the filler sentence "This skill is applicable to execute the workflow or actions described in the overview.", which is pure padding. This matches the anchor for content that is mostly efficient but includes unnecessary material that should be trimmed.

3 / 5

Actionability

Steps like "Examine git log (commits, dates, authors, messages)" and "Group by time period: daily (last 7 days), weekly (older)" offer some concrete guidance (categories, time windows), but no actual git commands or example output format are given. This is incomplete concrete guidance with missing key details rather than mostly-executable instruction.

3 / 5

Workflow Clarity

The four-step Procedure (examine -> group -> classify -> generate) is a clear, coherent sequence for a read-only task, so the destructive/batch validation cap does not apply. Minor gaps such as a missing output template or merge-commit handling keep it below the explicit-checkpoint anchor.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references, and its sections provide reasonable structure. The duplicated "When to Use" heading at the end is an organization flaw that prevents it from meeting the well-organized-sections bar for a top score.

4 / 5

Total

14

/

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 description with an explicit what/when structure and genuinely natural trigger phrases. Its main weakness is specificity: it names only the headline action rather than the concrete operations the skill actually performs.

Suggestions

Enumerate 2-3 concrete sub-actions in the description, e.g. "Generate structured changelogs from git history: group commits by time period, classify them by type (feature, fix, breaking), and produce user-facing descriptions."

Add common trigger synonyms such as "release notes" or "commit history" to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

"Generate structured changelogs from git history" names the domain and one concrete action, but does not enumerate the sub-actions (grouping, classifying, formatting) that the body performs. This matches the anchor for naming a domain with 1-2 concrete actions, not the several-specific-actions anchors above.

3 / 5

Completeness

The description explicitly answers both questions: the "what" ("Generate structured changelogs from git history") and the "when" ("Use when user asks..." with three concrete quoted trigger phrases). It matches the anchor that clearly and explicitly answers both with concrete triggers.

5 / 5

Trigger Term Quality

Natural user phrases like "what changed recently", "generate a changelog", and "summarize commits" are quoted verbatim, giving good keyword coverage. It stays below comprehensive because common synonyms such as "release notes" or "commit history" are missing.

4 / 5

Distinctiveness Conflict Risk

Changelog generation from git history is a distinct niche with dedicated triggers. Minor overlap risk remains because "summarize commits" could also fire for commit-message-writing or repo-summary skills, keeping it just below the minimal-conflict anchor.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/wiki-changelog/SKILL.md

Reviewed

Table of Contents

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.