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

78%

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

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

A highly actionable, well-structured playbook whose search templates, scoring rubric, and output formats are copy-paste ready. Its main weakness is the absence of validation/verification steps in what is a batch scan workflow, plus some trimmable marketing copy and duplicated trigger sections.

Suggestions

Add validation checkpoints to the workflow: how to handle failed or ambiguous searches, accounts without LinkedIn URLs or usage data, and a step to confirm signal dates/sources before scoring (batch operations need verify-then-proceed guidance).

Trim the marketing-style intro and merge the duplicated 'When to Use' and 'Trigger Phrases' sections to reduce token overhead.

Consider moving the Phase 1 signal catalog and the Phase 3/4 templates into one-level-deep reference files so SKILL.md reads as a leaner overview.

Dimension	Reasoning	Score
Conciseness	The body is dominated by dense, high-value material (signal tables, scoring formula, output templates), with only minor trimmable padding: the marketing-style intro ('Find expansion revenue hiding in your existing customer base... before a competitor gets there first') and the duplicated trigger-phrase lists ('When to Use' vs 'Trigger Phrases'). This matches 'efficient with minor instances of over-explanation' rather than the lean score-5 anchor.	4 / 5
Actionability	Guidance is fully executable: copy-paste-ready search query strings, a completely specified scoring formula ('Signal Strength (1-5)... 2.0x = Top 20% accounts by MRR'), explicit tier thresholds (Hot 15+ / Warm 8-14 / Watch 3-7), and complete talk-track and report templates. Specific examples cover the common cases, matching the top anchor.	5 / 5
Workflow Clarity	Phases 0–4 are clearly sequenced, but this is a batch operation (scanning all accounts weekly) with no validation or verification steps — no handling for failed or ambiguous searches, accounts missing LinkedIn URLs, or stale/unconfirmed signals before scoring. Per the judging guidelines, a batch workflow without validation is capped at 3; it is not 4 because checkpoints are absent rather than merely gapped.	3 / 5
Progressive Disclosure	The single-file body is well-organized into clearly headed phases with easy navigation and no nested or buried references (no bundle files exist). It is not 5 because at ~270 lines the Phase 1 signal catalog and the report/talk-track templates could be offloaded to one-level-deep reference files for a leaner overview; it is not 3 because the structure and content placement are solid, with only minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

71%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, capability-rich description with concrete signal types and outputs, held back by a missing 'Use when...' clause. Adding explicit trigger guidance and a few more natural user phrases would lift completeness and trigger-term quality to the top anchors.

Suggestions

Append an explicit trigger clause, e.g., 'Use when the user asks about upsell or cross-sell opportunities, account expansion, or wants a recurring expansion signal scan.'

Include more natural trigger variations users would actually say, such as 'expansion revenue', 'account growth', 'ready to upgrade', or 'renewal/expansion playbook'.

Clarify the distinct boundary vs. new-logo prospecting (e.g., 'for existing customers only, not new lead sourcing') to reduce overlap with generic lead-generation skills.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete capabilities — 'team growth on LinkedIn, new job postings, product usage patterns, funding announcements, and public company news' — and a concrete output ('weekly expansion opportunity list with context and talk tracks'), in third-person voice. Coverage of signal types is comprehensive with no minor gaps, matching the top anchor rather than the score-4 anchor.	5 / 5
Completeness	The 'what' is clearly answered (monitor these signals, produce this list), but there is no 'Use when...' clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 4 because the 'when' is entirely absent rather than merely implicit.	3 / 5
Trigger Term Quality	Natural CS/sales phrases like 'upsell', 'cross-sell', 'expansion', 'funding announcements', and 'job postings' give good keyword coverage. A few natural terms users would say are missing (e.g., 'expansion revenue', 'account growth', 'ready to upgrade'), so it falls short of the comprehensive synonym coverage of the score-5 anchor.	4 / 5
Distinctiveness Conflict Risk	The niche — expansion signals in existing customer accounts via LinkedIn and job-posting monitoring — is mostly distinct with clear triggers. Minor overlap risk remains with generic lead-generation/prospecting skills (the tag itself is 'lead-generation'), keeping it below the score-5 anchor.	4 / 5
	Total	16 / 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: cc3e518

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