CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

evidence-research

시장 규모, 경쟁사, 가격, CAC, 인건비 같은 산출물 숫자에 필요한 근거를 찾고 신뢰도를 표시한다.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/evidence-research/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a well-built instruction-only skill: lean, concrete, and self-contained, with a clear procedure, a copy-paste output template, and explicit confidence criteria that provide genuinely non-obvious decision rules. The only meaningful improvement would be a short worked example showing a filled-in research memo.

DimensionReasoningScore

Conciseness

The body is lean and efficient across five tight sections (목적, 입력, 절차, 출력 형식, 신뢰도 기준) with no explanations of concepts Claude already knows and no padding; every token earns its place. It clearly matches the top anchor rather than level 4, which reserves room for trimmable over-explanation that is absent here.

5 / 5

Actionability

Concrete guidance throughout: a 5-step procedure, named source types ('공개 자료, 경쟁사 페이지, 통계, 기사, 채용공고'), a copy-paste output template with an exact table schema, and explicit confidence criteria with example sources per level. It stops short of level 5 because there is no filled-in worked example (e.g., one completed table row) demonstrating the intended result.

4 / 5

Workflow Clarity

The numbered 절차 is clearly sequenced with per-claim checkpoints (step 4 confidence assignment) and an explicit error-recovery path (step 5: mark as '[가정]' and write a verification plan). Minor gaps — e.g., the referent of '참가자' in step 1 is ambiguous — keep it at level 4 rather than 5.

4 / 5

Progressive Disclosure

The body is under 50 lines, needs no external references, and is organized into clear, well-labeled sections; per the rubric's simple-skill guidance this earns the top score. There are no bundle files, so structure alone is the correct basis for scoring.

5 / 5

Total

18

/

20

Passed

Description

61%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 communicates a clear, reasonably specific capability with good domain keywords, but it only answers 'what' and omits any 'when to use' guidance in the description text itself. Adding an explicit use-when clause and slightly more action variety would raise it substantially.

Suggestions

Add an explicit 'Use when...' clause to the description (e.g., 'Use when writing business plans, pitch decks, or financial projections that need sourced numbers'), since the missing when-guidance caps completeness at 3.

Expand the action verbs beyond 'find' and 'mark' — e.g., 'compiles a research memo, classifies each claim as high/medium/low confidence, and flags unverified numbers as assumptions' — to lift specificity.

Fold natural trigger phrases like '시장 조사', '리서치', and 'TAM' directly into the description text rather than keeping them only in the separate triggers field.

DimensionReasoningScore

Specificity

The description names the domain concretely ('시장 규모, 경쟁사, 가격, CAC, 인건비') with two concrete actions ('근거를 찾고', '신뢰도를 표시한다'), matching the anchor for domain plus 1-2 concrete actions. It is not level 4 because it does not list several distinct specific actions.

3 / 5

Completeness

The 'what' is clear (find evidence for output numbers and mark confidence) but the description field contains no 'Use when...' clause or equivalent, which caps completeness at 3 per the judging guidelines. The separate frontmatter triggers field partially compensates but is not part of the description.

3 / 5

Trigger Term Quality

'시장 규모', '경쟁사', '가격', 'CAC', '인건비' are natural terms a user would say when needing this skill, giving good keyword coverage. It falls short of level 5 because common variations like '시장 조사', '리서치', and 'TAM' appear only in the separate triggers field, not in the description itself.

4 / 5

Distinctiveness Conflict Risk

The niche — sourcing numeric evidence with confidence marking for business deliverables — is mostly distinct, with clear domain markers ('CAC', '인건비', '신뢰도'). It is not level 5 because it could still mildly overlap with a generic market-research or web-research skill.

4 / 5

Total

14

/

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

retention-corp/road-to-founders

Path

skills/evidence-research/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.