expansion-signal-spotter

Monitor existing customer accounts for upsell and cross-sell signals: team growth on LinkedIn, new job postings, product usage patterns, funding announcements, and public company news. Produces a weekly expansion opportunity list with context and talk tracks. Chains web search, LinkedIn profile monitoring, and job posting detection.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/sales/composites/expansion-signal-spotter/SKILL.md

Quality

Content

68%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 actionable and reasonably concise with a clear phased workflow, but it lacks explicit validation/verification checkpoints for a weekly batch report. Adding a validation step between signal detection and talk-track generation would lift workflow clarity.

Suggestions

Insert an explicit validation checkpoint after Phase 1 (e.g. 'Verify each signal has a dated source URL; drop accounts in the exclusion filter; dedupe signals already reported last week') before scoring.

Move the full Phase 4 output template to a referenced file (e.g. OUTPUT_TEMPLATE.md) to tighten the main body and improve progressive disclosure.

Trim redundant 'What It Means' prose in the signal tables since Claude can infer expansion plays from the signal name and the dedicated Expansion Play column.

Dimension	Reasoning	Score
Conciseness	Mostly efficient: tables, scoring formulas, and templates carry the load, though the four inlined signal tables and full output template add length that could be trimmed without losing clarity. It does not pad with concepts Claude already knows.	4 / 5
Actionability	Provides concrete search-query strings, a quantified scoring formula (Signal Strength x Account Value x Timing with explicit multipliers), tier thresholds, and a copy-ready talk-track template; minor gaps remain in user-specific placeholders.	4 / 5
Workflow Clarity	Phases 0-4 are clearly sequenced, but this weekly batch operation has no explicit validation checkpoints (e.g. confirming signal source/date, applying exclusion filters, deduping across weeks), which per the rubric caps workflow clarity at 3.	3 / 5
Progressive Disclosure	A single well-organized SKILL.md with clear sections and tables; no bundle files exist or are referenced, and the inlined tables/output template are appropriate at this scope. Minor organization gaps keep it just below 5.	4 / 5
	Total	15 / 20 Passed

Description

82%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.

A specific, well-scoped description with strong trigger vocabulary and a distinct niche, weakened only by the absence of an explicit 'Use when' trigger clause. Adding that clause would raise completeness toward the top anchors.

Suggestions

Append an explicit 'Use when ...' clause, e.g. 'Use when scanning existing accounts for upsell/cross-sell opportunities or running the weekly expansion signal scan.'

Consider adding 'expansion revenue' or 'renewal upsell' as additional natural synonyms to broaden trigger matching.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete signal sources ('team growth on LinkedIn', 'new job postings', 'product usage patterns', 'funding announcements', 'public company news') plus a concrete output ('weekly expansion opportunity list with context and talk tracks'), matching the comprehensive-coverage anchor.	5 / 5
Completeness	The 'what' is clear (monitor accounts for expansion signals, produce a weekly list with talk tracks) but there is no explicit 'Use when...' trigger clause, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Natural sales-rep phrasing is well covered ('upsell', 'cross-sell', 'expansion', 'expansion opportunity list', 'job postings', 'funding announcements'), including synonyms a user would actually say.	5 / 5
Distinctiveness Conflict Risk	The niche is clear (existing-customer expansion detection via LinkedIn/funding/news monitoring) with distinct triggers and minimal overlap with unrelated skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: gooseworks-ai/goose-skills
Path: skills/sales/composites/expansion-signal-spotter/SKILL.md
Commit: 2523432

Reviewed: 5 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.