CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pitch-coach

30초, 60초, 3분 피치와 예상 Q&A를 만든다.

Quality

80%

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/pitch-coach/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.

The body is an exemplar of token efficiency: it assumes Claude's competence and provides a concrete, copy-paste output template with an explicit input contract. The only meaningful gaps are craft-level guidance (word-count fit for each time limit, a worked example) and quality checkpoints, which keep actionability and workflow clarity at 4 rather than 5.

DimensionReasoningScore

Conciseness

The body is lean throughout: a two-sentence role section ("피치 코치처럼 본다. 많은 정보를 짧은 시간 안에 이해되는 순서로 재배열한다"), a plain input list, and a template-only output format with zero explanation of concepts Claude already knows. Every token earns its place.

5 / 5

Actionability

The 출력 형식 is a concrete, copy-paste-ready markdown skeleton with an exact 7-part 3-minute structure, a Q&A table schema, and an explicit input list (아이디어 정의서, BMC, GTM, 세일즈 플랜, 청중, 제한 시간). Not 5 because there is no worked example or craft criteria (e.g., how many words fit a 30-second Korean pitch); not 3 because the template is executable rather than pseudocode-level.

4 / 5

Workflow Clarity

As a single-purpose skill the flow is clear and well-sequenced: gather the listed inputs, fill the output template, and optionally test via `korean-synthetic-consumer`의 `message-test` 모드. Not 5 because there is no checkpoint that each pitch actually fits its stated time limit and no guidance for handling missing inputs; not 3 because the task is unambiguous and involves no risky operations requiring validation.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external reference files, and its four sections (역할, 입력, 출력 형식, 보조 스킬) are well-organized and easy to navigate. The single cross-skill pointer to `korean-synthetic-consumer`'s `message-test` mode is one level deep and clearly signaled, so the simple-skill exception applies.

5 / 5

Total

18

/

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 is concise, in third-person declarative form, and specific about its deliverables (three timed pitches plus anticipated Q&A) with strong natural trigger terms. Its main weakness is the missing explicit 'when to use' guidance within the description itself, which caps completeness, and a few natural synonyms are absent.

Suggestions

Add an explicit when-to-use clause to the description, e.g. "미니 피칭, 데모데이, 60초 발표 준비 시 사용한다", so the description itself answers 'when should Claude use it' and lifts completeness above 3.

Include natural synonyms and variations in the description — such as "엘리베이터 피치", "IR", "발표 준비" — alongside "피치" to broaden trigger term coverage.

Mention the full deliverable set (e.g., 첫 문장 후보 3개, 줄일 문장/더 강하게 말할 문장 정리) so the description comprehensively covers everything the skill outputs.

DimensionReasoningScore

Specificity

"30초, 60초, 3분 피치와 예상 Q&A를 만든다" names the domain and several concrete deliverables (three timed pitch variants plus anticipated Q&A). It falls short of 5 because a single verb covers the actions and other outputs the skill produces (첫 문장 후보, 줄일/강화할 문장) are absent, but it clearly exceeds the 1-2-action level of 3.

4 / 5

Completeness

The 'what' is clear and concrete, but the description field itself contains no "Use when..." clause or equivalent trigger guidance, so completeness is capped at 3 per the judging guidelines. Not 4 because the when-context lives only in the separate triggers field, not in the description; not 2 because the 'what' is specific rather than vague.

3 / 5

Trigger Term Quality

The description contains the natural core term "피치" with the exact duration variants users would say ("30초", "60초", "3분") plus "예상 Q&A", and the frontmatter triggers ("미니 피칭", "피치", "60초 발표", "데모데이") add good coverage. Not 5 because common synonyms like "엘리베이터 피치", "IR", or "발표 준비" are missing.

4 / 5

Distinctiveness Conflict Risk

The timed-pitch focus ("30초, 60초, 3분 피치") plus Q&A preparation defines a distinct niche unlikely to grab unrelated skills. Not 5 because broad terms like "피치" and "발표" have minor overlap with general presentation or speech-writing skills; not 3 because the specific durations and Q&A framing go beyond 'somewhat specific'.

4 / 5

Total

15

/

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/pitch-coach/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.