yes-and
Think bigger about your idea while solving the real risks. Inspired by how the best startup advisors give feedback — they find the kernel of something great, push you to see the larger version you're missing, then help you defuse the landmines between here and there.
33
17%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./execution-skills/skills/yes-and/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description reads like inspirational marketing copy rather than a functional skill description. It fails to specify concrete actions, lacks natural trigger terms users would use, provides no explicit 'when to use' guidance, and is too generic to distinguish from other advisory or brainstorming skills. It also uses second person ('your idea') which violates the third-person voice requirement.
Suggestions
Replace metaphorical language with concrete actions, e.g., 'Evaluates startup ideas by identifying strengths, expanding the vision, and analyzing key risks such as market fit, competition, and execution challenges.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks for startup feedback, idea validation, pitch review, business idea critique, or risk assessment.'
Rewrite in third person voice (e.g., 'Analyzes startup ideas and provides structured feedback') instead of second person ('your idea').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses entirely abstract, motivational language ('think bigger', 'solve real risks', 'defuse landmines') without naming any concrete actions. There are no specific capabilities listed — no verbs like 'analyze', 'generate', 'evaluate', or 'create'. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is clearly answered. There is no 'Use when...' clause or equivalent explicit trigger guidance. The description reads like marketing copy rather than functional documentation. | 1 / 3 |
Trigger Term Quality | The description lacks natural keywords a user would type. Terms like 'kernel of something great' and 'defuse the landmines' are metaphorical, not searchable trigger terms. Missing obvious terms like 'startup feedback', 'idea review', 'business plan critique', or 'pitch evaluation'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague it could apply to any brainstorming, feedback, coaching, or strategy skill. 'Think bigger about your idea' and 'solving real risks' are generic enough to conflict with numerous other skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a well-structured advisory framework with a clear four-beat sequence, but it is significantly over-written for its purpose. Much of the content is motivational coaching language and meta-commentary that Claude doesn't need — the actual actionable content (the prompt template structure and the rules) could be delivered in roughly half the tokens. The cross-references to companion skills are a strength, but the lack of any validation/iteration mechanism and the monolithic presentation weaken it.
Suggestions
Cut the preamble and meta-commentary drastically — remove sentences like 'The best startup advisors don't just tell you what's wrong' and 'Most people describe their idea too small' which explain concepts Claude already understands. Lead directly with the prompt template.
Add a brief validation checkpoint between beats 1-2: e.g., 'Confirm the kernel resonates with the user before expanding to the bolder version' to create a feedback loop.
Extract the prompt template into a separate file (e.g., PROMPT.md) and keep SKILL.md as a concise overview with usage instructions and references, improving progressive disclosure.
Tighten the Rules section — several rules restate what's already implicit in the beat descriptions (e.g., 'Be specific when you push bigger' is already covered by the Beat 2 instructions).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose for what is essentially a prompt template. The preamble explains what good advisors do (Claude knows this), the prompt itself contains extensive coaching language and meta-commentary ('Most people describe their idea too small'), and the tips section adds more padding. The entire skill could be reduced to the prompt template with minimal framing. | 1 / 3 |
Actionability | The prompt template provides a structured four-beat framework with specific sub-questions and output format, which is reasonably actionable. However, it's a prompt template rather than executable code/commands, and some guidance remains abstract ('Be concrete enough to act on'). The landmine defusal format is well-structured but the overall approach is more descriptive than prescriptive. | 2 / 3 |
Workflow Clarity | The four beats are clearly sequenced and the ordering rationale is explicit ('if you lead with risks, people stop listening'). However, there are no validation checkpoints — no way to verify the kernel was correctly identified before pushing to the bolder version, no feedback loop if the user disagrees with the reframing. For an advisory/generative skill this is less critical, but the lack of any checkpoint or iteration step keeps it at 2. | 2 / 3 |
Progressive Disclosure | The content is a monolithic wall — the entire prompt template is inline with no separation of the template from supporting guidance. The tips section references other skills (yc-office-hours, pre-mortem, prioritize) which is good navigation, but the main body could benefit from separating the prompt template into its own file or at least having a concise overview before the full template. No bundle files exist to offload content to. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- amplitude/builder-skills
- Commit
221ffaa
- 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.