code-card-news-generator

Generate code explanation cards with syntax highlighting for tutorials and education. Creates title cards and explanation cards with Korean descriptions and code examples.

Quality

71%

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 ./backup/code-card-news-generator/SKILL.md

Quality

Content

76%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 body is highly actionable with concrete, copy-paste-ready commands and clear sequencing, but the batch-generation workflow lacks an explicit validation checkpoint and the inlined design/reference material could be split out for better progressive disclosure.

Suggestions

Add an explicit validation step to Step 3, e.g. after running the script verify each PNG was created and text did not overflow before presenting download links, turning Error Handling into a checkpoint.

Move the Design Specifications and Manual Single Card Creation sections into separate reference files (e.g. design-spec.md, manual-creation.md) referenced from SKILL.md to reduce inline bulk.

De-duplicate the useNavigate example so the Step 2 illustration and Step 3 heredoc do not repeat the same content verbatim.

Dimension	Reasoning	Score
Conciseness	Mostly lean and command/spec-driven, but the useNavigate example is duplicated across the Step 2 example and the Step 3 heredoc, and a few intro/tips lines are trimmable; not quite a token-perfect 5.	4 / 5
Actionability	Fully copy-paste-ready commands with complete arguments and heredoc input, exact input format, color hex codes, canvas dimensions, and font names cover both batch and single-card creation; examples span the common cases.	5 / 5
Workflow Clarity	The four steps are clearly sequenced, but this batch operation (multiple cards) has no explicit validate-then-proceed checkpoint; the Error Handling section is reactive rather than a validation gate, so the batch-operation cap of 3 applies.	3 / 5
Progressive Disclosure	Well-organized into clearly labeled sections with no bundle files to navigate, but at ~255 lines substantial material (design specs, manual creation, example topics) is inlined that could move into separate reference files; not a 5 because no reference split exists and the file is well over 50 lines.	4 / 5
	Total	16 / 20 Passed

Description

66%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 clearly states what the skill does with several concrete actions and a distinct niche, but it omits an explicit 'Use when...' trigger clause, which caps completeness and weakens trigger-term coverage.

Suggestions

Add an explicit 'Use when...' clause naming concrete user triggers, e.g. 'Use when the user asks for code tutorial cards, code card news (코드 카드뉴스), or syntax-highlighted explanation cards for a library, hook, or concept.'

Include the natural Korean trigger phrases users say (e.g. '코드 설명 카드 만들어줘', '코드 카드뉴스 생성해줘') so the description matches real requests.

Mention the output format (PNG, 1080x1080) to make the 'what' more concrete and further reduce overlap with generic diagram skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'Generate code explanation cards with syntax highlighting', 'Creates title cards and explanation cards with Korean descriptions and code examples' — with only minor coverage gaps; not comprehensive enough for a 5.	4 / 5
Completeness	Has a clear 'what' but no explicit 'Use when...' trigger clause — 'for tutorials and education' only weakly implies when; per guideline, a missing explicit trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Good natural keyword coverage ('code explanation cards', 'tutorials and education', 'title cards', 'explanation cards'), but misses common synonyms and the Korean trigger phrases a user would actually say ('코드 카드', '코드 설명 카드') that appear only in the body.	4 / 5
Distinctiveness Conflict Risk	The Korean-language code-tutorial-card niche is mostly distinct with minor overlap risk against general diagram/screenshot skills; triggers are not yet concrete enough to reach 5.	4 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 3 suspicious	Warning

	Total	15 / 16 Passed

Repository: bear2u/my-skills
Path: backup/code-card-news-generator/SKILL.md
Commit: 8ed5784

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