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

74%

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%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 well-structured, actionable composite workflow with strong sequencing and validation gates; its main weakness is that all detail lives in a single long file with no progressive disclosure into reference files.

Suggestions

Extract the Step 0 configuration tables and/or the per-step input/output contracts into reference files (e.g. references/contracts.md, references/config.md) and link to them from the body to reduce inline bulk.

Trim the overlap between the ASCII architecture diagram and the Execution Summary table, keeping one as the canonical overview.

Consider pulling the per-tool integration notes (Apollo/Crunchbase/LinkedIn/Clearbit specifics) into a references/tools.md so the core workflow stays lean.

Dimension	Reasoning	Score
Conciseness	The body is efficient and free of concept-explanation padding, with detailed input/output contracts that earn their place; minor duplication between the architecture diagram and the execution summary table could be trimmed.	4 / 5
Actionability	Provides concrete search queries (e.g. '"{company_name}" AND ("raised" OR "funding" OR "Series") AND "2026"'), explicit field schemas, tier definitions, and named frameworks; gaps are limited because the skill is deliberately tool-agnostic.	4 / 5
Workflow Clarity	Steps 0–5 are clearly sequenced with explicit human validation checkpoints at every step and a final launch gate, providing the feedback loops the rubric expects for a batch/outreach operation.	5 / 5
Progressive Disclosure	The ~520-line body is well-sectioned but monolithic: detailed config tables and input/output contracts that could live in separate reference files are all inlined, and no bundle/reference files exist.	3 / 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.

The description is specific and action-oriented with a clear niche, but it omits an explicit 'when to use' trigger clause, leaving the activation guidance implicit rather than stated.

Suggestions

Append an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when the user has a list of companies and wants to act on recent funding signals, or mentions recently funded companies or funding-round outreach.'

Add a few natural synonyms/extensions (e.g. 'raised funding', 'Series A', 'newly funded') to broaden trigger-term coverage.

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' — giving comprehensive coverage of the composite's capabilities.	5 / 5
Completeness	The 'what' is clearly stated across four actions, but the description lacks any explicit 'Use when...' trigger clause, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Includes natural terms like 'funding events', 'funding signal', 'outreach', and 'recently funded', but is missing some common synonyms and explicit trigger phrases a user might say.	4 / 5
Distinctiveness Conflict Risk	The funding-signal niche is distinct and unlikely to trigger for unrelated skills, though there is minor overlap risk with the related cold-email-outreach and linkedin-outreach skills it chains to.	4 / 5
	Total	16 / 20 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: 2523432

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.