funding-signal-outreach

End-to-end funding signal composite. Takes any set of companies, detects recent funding events, qualifies against your company context, finds relevant people (buyers, champions, users), and drafts personalized outreach. Tool-agnostic — works with any company source, contact finder, and outreach platform.

Quality

68%

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/outreach/composites/funding-signal-outreach/SKILL.md

Quality

Content

77%

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

The body is a well-sequenced, highly actionable multi-step workflow with explicit approval gates at every stage, strong on actionability and workflow clarity. Its main weakness is conciseness and progressive disclosure: it is a single large file with no reference splitting and some redundant detail.

Suggestions

Move the full config question tables and email-framework detail into a references file (e.g. CONFIG.md / EMAIL-FRAMEWORKS.md) and link to it from the main body to improve progressive disclosure and reduce length.

Trim the duplicated Execution Summary table and consolidate the human-checkpoint mock tables into a single reusable template.

Cut explanatory prose that restates what the contracts already specify (e.g. re-explaining each step's purpose after the Purpose line).

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete contracts and tables, but at ~548 lines it includes padding (elaborate human-checkpoint mock tables, an Execution Summary duplicating per-step info, and a Tips section) that could be tightened, matching the 'mostly efficient but could be tightened' anchor.	2 / 3
Actionability	Provides fully concrete guidance — typed input/output contracts, per-tool action tables, scoring criteria with weights, and tier definitions — leaving Claude with exact, executable instructions rather than vague direction.	3 / 3
Workflow Clarity	Steps 0-5 are clearly sequenced with an explicit human checkpoint (review/approve gate) after each one, including a final 'Ready to launch?' gate before batch email sends — a clear sequence with explicit validation steps for a batch operation.	3 / 3
Progressive Disclosure	Sections are well-organized, but the skill is a monolithic ~548-line wall of text with all detail inline and no bundle files or one-level-deep references; content like config schemas and email frameworks that could be separate stays inline, matching the 'some structure but content that should be separate is inline' anchor.	2 / 3
	Total	10 / 12 Passed

Description

60%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and concrete about capabilities but omits any explicit 'Use when...' trigger guidance, capping completeness and trigger term quality. It reads well but stops short of telling Claude exactly when to load this skill.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user has a list of companies and wants to act on recent funding signals, or says things like reach out to recently funded companies.'

Include natural user phrasings such as 'recently funded companies', 'raised money', and 'funding rounds' alongside the technical terms.

Sharpen distinctiveness by framing it as the composite that chains funding detection -> qualification -> outreach, distinguishing it from standalone email/LinkedIn outreach skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'detects recent funding events, qualifies against your company context, finds relevant people (buyers, champions, users), and drafts personalized outreach' — matching the 'multiple specific concrete actions' anchor.	3 / 3
Completeness	Thoroughly answers 'what does this do' but provides no explicit 'when should Claude use it' clause; per the guidelines, a missing 'Use when...' trigger caps completeness at 2.	2 / 3
Trigger Term Quality	Contains relevant keywords ('funding signal', 'funding events', 'outreach') but lacks the common natural variations a user would say ('recently funded companies', 'raised money') and has no explicit trigger phrasing, matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The 'funding signal composite' niche is reasonably distinct, but generic terms like 'outreach' and 'contact finder' overlap with sibling skills (cold-email-outreach, linkedin-outreach), so it could still overlap with similar skills.	2 / 3
	Total	9 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (548 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: gooseworks-ai/goose-skills
Path: skills/outreach/composites/funding-signal-outreach/SKILL.md
Commit: 8866b2a

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.