what-would-lenny-do

Answers product strategy, growth, pricing, hiring, and leadership questions using Lenny Rachitsky's archive. ONLY use this skill if the `lennysdata` MCP server is connected and its tools (search_content, read_content, etc.) are available. If the lennysdata MCP is not connected, do NOT use this skill — respond using your own knowledge instead.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A high-quality, well-sequenced research-and-synthesis skill with concrete tool calls and strong error-recovery guidance, held back only by verbosity and a monolithic structure that doesn't progressively disclose its examples and troubleshooting.

Suggestions

Move the four worked Examples into a references/EXAMPLES.md and the Troubleshooting cases into references/TROUBLESHOOTING.md, leaving inline one-line pointers, to improve progressive disclosure.

Trim editorializing in Phase 1 and the Search Strategy Tips and collapse redundant guidance between 'Gotchas' and 'Troubleshooting' to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of basic-concept padding, but prose-heavy editorializing ('This framing shapes everything — a sharp question leads to a sharp search') and a long four-example block could be tightened to earn their tokens.	2 / 3
Actionability	Provides concrete tool calls (lennysdata:search_content, read_content, read_excerpt, list_content), explicit quantities (2–3 parallel searches, 2–4 pieces), and sample query strings with named guests — fully actionable guidance for an instruction-only skill.	3 / 3
Workflow Clarity	A clearly sequenced five-phase workflow (Understand → Search → Select/Read → Map → Deliver) with a Troubleshooting section supplying explicit error-recovery loops for empty results, tangential content, broad questions, and conflicting advice.	3 / 3
Progressive Disclosure	Sections are well-organized but the skill is monolithic — no bundle files exist and the substantial Examples and Troubleshooting content stays inline; at ~150 lines it exceeds the small-skill leniency threshold, so appropriate splitting is not realized.	2 / 3
	Total	10 / 12 Passed

Description

82%

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 clear, distinctive description that names concrete domains and natural trigger terms, but its explicit 'when' guidance is a runtime precondition (MCP connectivity) rather than a content-based 'Use when…' trigger, so it falls short of full completeness.

Suggestions

Add an explicit content trigger, e.g. 'Use when the user asks about product strategy, growth, pricing, hiring, or leadership dilemmas and wants advice grounded in Lenny Rachitsky's archive.'

Keep the MCP-availability guard but frame it as a precondition alongside, not in place of, the content trigger.

Dimension	Reasoning	Score
Specificity	Enumerates five concrete domains ('product strategy, growth, pricing, hiring, and leadership questions') plus the mechanism ('using Lenny Rachitsky's archive'), listing multiple specific capabilities rather than a single vague action.	3 / 3
Completeness	The 'what' is clear, but the only explicit 'when' is an MCP-availability precondition ('ONLY use this skill if the lennysdata MCP server is connected') rather than a content trigger; no explicit 'Use when the user asks about…' clause, which caps completeness at 2.	2 / 3
Trigger Term Quality	'product strategy, growth, pricing, hiring, and leadership questions' are natural terms a user would actually say, giving good coverage of likely trigger phrasing.	3 / 3
Distinctiveness Conflict Risk	The tight coupling to the 'lennysdata' MCP server and Lenny Rachitsky's archive creates a clear, unique niche extremely unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: amplitude/builder-skills
Commit: 22b0634

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.