CtrlK
BlogDocsLog inGet started
Tessl Logo

code-changelog

AI가 만든 모든 코드 변경사항을 reviews 폴더에 기록하고 간단한 HTML 뷰어로 웹 브라우저에서 실시간 확인할 수 있습니다. 매 수정마다 문서가 생성되고 Python 서버로 즉시 확인 가능합니다.

49

Quality

52%

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 ./skills/code-changelog/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

46%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.

The skill body is highly actionable with concrete code examples and a clear sequence, but it is severely padded with repetition and marketing sections, lacks validation checkpoints, and fails to split content into referenced files despite its length.

Suggestions

Collapse the repeated server/port instructions into a single section and remove redundant 장점/비교/배포 marketing content to respect the token budget.

Add an explicit validation step after save_and_build() (e.g. confirm the new .md appears in reviews/ and index.html lists it) to satisfy the batch-operation checkpoint requirement.

Move the HTML viewer source, tracker implementation, and deployment options into referenced files under assets/ or references/ and link to them one level deep instead of inlining or omitting them.

DimensionReasoningScore

Conciseness

The ~393-line body is noticeably verbose: the `python3 -m http.server 4000` command is repeated roughly six times, and padded marketing sections (장점, 비교 표, 배포 옵션, multiple near-identical scenario examples) add little actionable value.

2 / 5

Actionability

Concrete, copy-paste-ready code and commands are provided throughout (CodeChangeLogger usage, log_file_creation/modification calls, save_and_build, server commands), with only the minor gap that code_changelog_tracker.py itself is referenced but not bundled.

4 / 5

Workflow Clarity

The workflow is sequenced with numbered steps (초기 설정 → 개발 사용 → 서버 실행) and illustrative scenarios, but there are no explicit validation/verification checkpoints for the file-generating batch operations.

3 / 5

Progressive Disclosure

No bundle files exist and the body is a monolithic 393-line document; content that belongs in separate files (full HTML viewer, tracker implementation, deployment guide, comparison) is either inlined or missing rather than split into one-level-deep references.

2 / 5

Total

11

/

20

Passed

Description

58%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.

The description concretely describes what the skill does across multiple actions but omits any explicit 'when to use' trigger guidance, capping completeness. Trigger term coverage is adequate but lacks synonyms.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g. when the user asks to track or review AI-generated code changes).

Include natural synonyms and file extensions users might say, such as 'changelog', '변경 이력', and '.md', to improve trigger term coverage.

Tighten the description to third-person imperative voice and lead with the trigger condition before the capability list.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('코드 변경사항을 reviews 폴더에 기록', '간단한 HTML 뷰어로 웹 브라우저에서 실시간 확인', '매 수정마다 문서가 생성', 'Python 서버로 즉시 확인'), giving broad coverage with only minor gaps.

4 / 5

Completeness

It clearly states what the skill does but contains no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant natural keywords are present (코드 변경사항, reviews 폴더, HTML 뷰어, Python 서버) but common synonyms/variations (changelog, 변경 이력, .md) are missing, placing it at the middle anchor.

3 / 5

Distinctiveness Conflict Risk

The combination of AI code-change logging plus an HTML viewer is a fairly distinct niche with only minor overlap risk against general documentation skills.

4 / 5

Total

14

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
bear2u/my-skills
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.