CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

humanize-scan

한글 글에 AI 티가 얼마나 있는지 재고, 실제로 고치면 어떻게 되는지 표본으로 보여주는 정찰 스킬. 실측 판별력 상위 6개만 본다. 워크스페이스·진단·게이트·서브에이전트 없이 이 대화 안에서 끝낸다(파일 0개, 서브에이전트 0회). 손볼 게 많다고 나오면 전수 윤문은 humanize-korean(=/humanize)으로 넘긴다. 트리거 — "이 글 AI 같아?", "AI 티 있나 봐줘", "스캔해줘", "윤문 돌릴 값어치 있나", "AI 티 점수", "quick humanize", "/humanize-scan".

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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, instruction-only skill body that gives specific, operational rules and guardrails rather than vague direction, with a clear decision-driven workflow and validation checkpoints. The 6-signal table and output spec are highly actionable; adding one concrete before→after example would round it out.

Suggestions

Add one short before→after example pair inline (e.g. for C-8 대구) so the prescription is unambiguous without leaving the body.

Tighten the '이건 일부러 안 본다' section to a compact list; the rationale for each omission can be one phrase rather than a clause.

Make the 30% changed-ratio guard an explicit validate→rollback feedback step in the workflow section so the checkpoint is named as a loop.

DimensionReasoningScore

Conciseness

Dense and operational with almost no padding of concepts Claude already knows; the '이건 일부러 안 본다' justification section and some guardrail elaboration could be trimmed slightly, but every section earns its place.

4 / 5

Actionability

Concrete prescriptions per signal ('2회+', '쉼표 삭제', '종결어미만 변주'), a specified 4-part output format, and a 3-signal decision threshold; minor gap is the absence of an illustrative before→after example in the body itself.

4 / 5

Workflow Clarity

Clear sequence (input → scan 6 signals → count triggers → branched output) with validation checkpoints — '안 고쳐 보고 숫자를 쓰지 않는다', the 30% changed-ratio guard, and the rollback rule — leaving only minor explicit feedback-loop gaps.

4 / 5

Progressive Disclosure

Single well-sectioned file with clear headers; the one external reference (humanize-korean/references/empirical-validation.md) is clearly signaled as the evidence basis and is one level deep, with only minor organization room remaining.

4 / 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-crafted description that clearly states a focused purpose, scopes the work tightly (6 signals, no files/subagents), and provides explicit natural-language triggers. The only soft spot is minor overlap with the sibling humanize-korean skill and a few missing trigger synonyms.

DimensionReasoningScore

Specificity

Names the domain (Korean AI-tint detection) and several concrete actions — '재고', '표본으로 보여주는', '실측 판별력 상위 6개만 본다', 'humanize-korean으로 넘긴다' — with only minor coverage gaps around how the measurement is expressed.

4 / 5

Completeness

Explicitly answers both what (measure AI-tint, show sample fixes, scope to 6 signals, hand off) and when (concrete trigger phrases listed), in third-person declarative voice with no first/second-person phrasing.

5 / 5

Trigger Term Quality

Good coverage of natural phrases users would say — '이 글 AI 같아?', 'AI 티 있나 봐줘', '스캔해줘', '윤문 돌릴 값어치 있나', 'AI 티 점수', 'quick humanize', '/humanize-scan' — with synonyms across Korean and English, though a few common variations are absent.

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche (정찰/recon vs 전수 윤문) and distinct slash command '/humanize-scan' vs '/humanize', with only minor overlap risk against the closely related humanize-korean skill.

4 / 5

Total

17

/

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

epoko77-ai/im-not-ai

Path

skills/humanize-scan/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.