CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

vc-red-team-review

VC와 회의적인 동료 관점에서 산출물의 약한 가정을 공격하고 수정 우선순위를 만든다.

Quality

77%

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/vc-red-team-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 lean, well-structured instruction-only skill: an exact output template with precise ratio and fix-direction rules makes the expected deliverable unambiguous, and the short single-task body justifies having no external files. The only minor gaps are an undefined severity scale and the absence of a worked example, which keep actionability just below full marks.

DimensionReasoningScore

Conciseness

Every line earns its place: one sentence of persona framing ("친절한 멘토가 아니라 회의적인 투자자처럼 본다"), a three-item input list, a compact output template, and three rules — no concept explanations, no padding, and it fully assumes Claude's competence at critiquing deliverables.

5 / 5

Actionability

The output template is fully concrete — exact sections, table columns "# | 우려 | 왜 중요한가 | 심각도 | 수정 방향", and priority tiers "오늘 고칠 것 / 1주 안에 검증할 것 / 나중에 해도 되는 것" — and the rules are specific ("칭찬 30%, 공격 70%", "모든 비판에는 수정 방향을 붙인다"). It falls short of 5 only because the "심각도" scale is undefined and no worked example of a criticism-and-fix pair is given.

4 / 5

Workflow Clarity

This is a simple single-purpose skill whose single action is unambiguous: read the listed inputs (산출물 전체, 특히 걱정되는 부분, 피치 대상), apply the three rules, and emit the memo in the given format. The simple-skill exception applies, and since the skill is non-destructive and non-batch, no validation checkpoint is required.

5 / 5

Progressive Disclosure

The body is well under 50 lines and needs no external references (none exist in the bundle, and none are required for this task); the four clearly labeled sections (역할, 입력, 출력 형식, 규칙) satisfy the simple-skill criterion for a top progressive-disclosure score.

5 / 5

Total

19

/

20

Passed

Description

53%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 and fairly distinctive 'what' — red-teaming weak assumptions from a VC/skeptical-colleague viewpoint and turning them into revision priorities — in lean third-person Korean prose. However, it entirely lacks 'when to use' guidance and omits the natural trigger phrases (peer review, red team) that live only in the frontmatter triggers list, leaving completeness and trigger coverage at mid-scale.

Suggestions

Add an explicit 'Use when...' clause to the description (e.g., "Use when the user asks for a red-team review, peer review, or VC-perspective critique of deliverables") to raise completeness above the cap of 3.

Fold the frontmatter trigger terms (피어 리뷰, 레드팀, VC 리뷰, 약한 가정) into the description text itself so the natural phrases users actually say appear in the evaluated description, improving trigger_term_quality.

Enumerate one or two more concrete actions in the description — such as posing critical questions or ranking the top weak assumptions with verification methods — to move specificity from 1-2 actions toward comprehensive coverage.

DimensionReasoningScore

Specificity

The description names its domain and exactly two concrete actions — "약한 가정을 공격하고" and "수정 우선순위를 만든다" — which matches the '1-2 concrete actions, but not comprehensive' anchor. It is not 4 because it does not list several specific actions (e.g., posing critical questions, ranking assumptions), and not 2 because the actions are concrete rather than generic.

3 / 5

Completeness

The 'what' is clear (attack weak assumptions in deliverables and produce revision priorities from a VC/skeptical-colleague perspective), but there is no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

The description contains some genuinely natural terms a user would say — "VC", "약한 가정", "피치 대상" is absent but "VC와 회의적인 동료" is present — yet the most common trigger phrases ("피어 리뷰", "레드팀") appear only in the separate triggers field, not the description itself. This matches 'some relevant keywords but missing common variations or synonyms' rather than the good coverage of anchor 4.

3 / 5

Distinctiveness Conflict Risk

"VC와 회의적인 동료 관점에서" carves out a distinct reviewer persona focused on "약한 가정" and "수정 우선순위", giving it mostly distinct triggers with only minor overlap risk against generic feedback/review skills. It is not 5 because "산출물" (deliverables) is broad and the description itself carries no distinguishing trigger phrases to minimize conflict with general critique skills.

4 / 5

Total

13

/

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/vc-red-team-review/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.