know-before-you-go-perla-lobera

Pre-call intelligence skill that auto-assembles a role-specific brief from multiple data sources so no one walks into a customer call cold. Generates a polished HTML document with company context, stakeholder profiles, pain points, competitive intel, and gap analysis. ALWAYS use this skill when the user mentions: preparing for a call, pre-call prep, call brief, know before you go, customer brief, meeting prep for a prospect or customer, "what do we know about [company]", "brief me on [account]", "get me ready for my call with [company]", deal intel, account intelligence, or show up already knowing. Also trigger when the user asks to generate a demo script and wants account context pulled in first, or when prepping for a QBR, executive briefing, or renewal conversation. Works for both SEs and AEs with role-specific output.

Quality

63%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./sales-skills/skills/know-before-you-go-perla-lobera/SKILL.md

Quality

Discovery

100%

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 is an excellent skill description that clearly communicates what the skill does (generates role-specific pre-call briefs as HTML documents with specific content sections) and when to use it (extensive list of natural trigger phrases covering various sales preparation scenarios). The description is well-structured with concrete actions, comprehensive trigger terms, and a distinct niche that minimizes conflict risk with other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'auto-assembles a role-specific brief from multiple data sources', 'Generates a polished HTML document with company context, stakeholder profiles, pain points, competitive intel, and gap analysis.' These are detailed, concrete capabilities.	3 / 3
Completeness	Clearly answers both 'what' (assembles role-specific briefs with company context, stakeholder profiles, pain points, competitive intel, gap analysis as HTML) and 'when' (explicit 'ALWAYS use this skill when...' clause with extensive trigger scenarios). Both dimensions are thoroughly covered.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms users would actually say: 'preparing for a call', 'pre-call prep', 'call brief', 'what do we know about [company]', 'brief me on [account]', 'get me ready for my call with [company]', 'deal intel', 'account intelligence', 'meeting prep', 'QBR', 'executive briefing', 'renewal conversation'. These are highly natural phrases.	3 / 3
Distinctiveness Conflict Risk	Occupies a very clear niche: pre-call intelligence briefing for sales contexts. The combination of sales-specific terminology (SEs, AEs, QBR, deal intel, account intelligence) and the specific output format (HTML brief with stakeholder profiles, competitive intel) makes it highly distinctive and unlikely to conflict with other skills.	3 / 3
	Total	12 / 12 Passed

Implementation

27%

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

This skill has a well-thought-out domain model and comprehensive coverage of the pre-call intelligence workflow, but it is severely over-engineered for a single SKILL.md file. The extreme verbosity (explaining why every signal matters, repeating pain-hunting directives, including a v2 roadmap) wastes tokens, and the lack of any supporting bundle files means all detail is crammed into one monolithic document. Actionability suffers from the absence of concrete tool invocation patterns or executable templates.

Suggestions

Split the HTML template specification, data source playbook, and SE/AE output templates into separate referenced files (e.g., TEMPLATE.md, DATA_SOURCES.md, SE_OUTPUT.md, AE_OUTPUT.md) to dramatically improve progressive disclosure and reduce the main file to an overview.

Remove the v2 Vision section entirely — it provides no actionable guidance and wastes tokens.

Cut repeated explanations of why pain matters and why signals are important — state the priority once at the top and trust Claude to apply it throughout.

Add concrete tool invocation examples (e.g., actual MCP tool call syntax for Granola, Salesforce, Outreach) instead of abstract descriptions like 'Search Granola for meetings mentioning the company name'.

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~400+ lines. It over-explains concepts Claude already understands (what pain points are, why hiring signals matter, what a Story Arc is), includes a v2 roadmap section that adds no actionable value, and repeats the same 'hunt for pain' directive across multiple sections. Significant token waste throughout.	1 / 3
Actionability	The skill provides detailed structural guidance for the output (HTML sections, table columns, color schemes) and clear data source instructions, which is good. However, there is no executable code, no concrete MCP tool invocation syntax, no actual HTML/CSS template to use, and the data source searches are described abstractly ('Search Granola for meetings') without specifying actual tool calls or API patterns.	2 / 3
Workflow Clarity	The 4-step workflow (Collect Inputs → Run Intelligence Engine → Synthesize → Generate Brief) is clearly sequenced and logical. However, there are no validation checkpoints — no step to verify data quality before synthesis, no confirmation with the user before generating the final brief, and no feedback loop if the brief is incomplete or inaccurate. The gap detector is a good concept but lacks explicit 'stop and verify' gates.	2 / 3
Progressive Disclosure	The entire skill is a monolithic wall of text with no references to supporting files. The detailed HTML formatting spec, the SE vs AE output templates, the data source playbook, and the error handling could all be split into separate referenced files. With no bundle files provided, everything is crammed into one massive document, making it hard to navigate and consuming excessive context window.	1 / 3
	Total	6 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: amplitude/builder-skills
Commit: 221ffaa

Reviewed: 1 day 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.