Loading the registry…
Make a 1:1 블로그 썸네일 (square blog/SNS thumbnail, 1000×1000 → exported as a 2000×2000 PNG) from a user-supplied photo plus short Korean text — a 제목(title), 카테고리(category), and 주제/키워드(topic keyword). The signature look: the photo fills the whole square uncovered, and the text sits in a bottom gradient band with a sky-blue + white palette (강조는 하늘색). Built with self-contained HTML/CSS and rendered to an image with Playwright. Use this skill whenever the user wants a 블로그 썸네일 / 썸네일 / thumbnail / 대표 이미지 / 표지 이미지 for a blog post or SNS, ESPECIALLY when they hand over a photo and want title/category/topic text on it — even if they just say "이걸로 썸네일 만들어줘", "이미지 업로드 했으니 썸네일 뽑아줘", or drop an image with a 제목·카테고리·주제. Also use it to re-render after changing text, swapping the photo, or tweaking the accent color while keeping the same look. Prefer this skill over ad-hoc HTML so every thumbnail stays on-brand and consistent.
Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
8 critical findings reported by cisco-skill-scanner. The composite score alone does not reflect this — read the per-scanner reports below.
Claude Skills install to a single target, no runtime picker.
nerlo install -- 'blog-plugins/blog-thumbnail-plugin (blog-thumbnail-generator)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'blog-plugins/blog-thumbnail-plugin (blog-thumbnail-generator)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
4 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v2.0.11
17 findings · 6.8s
v0.3.74
2 findings · 0.9s
v0.1.0
0 findings · 3.0s
v0.1.0
0 findings · 3.0s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 0.9s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 17, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicable | rejected |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
This review has not run for this scan yet. It runs once per scan, in the background, and is kept; it appears here when it has. Until then all 19 findings above stand exactly as their scanners reported them, at full severity.