hiring-signal-outreach

End-to-end hiring signal composite. Takes any set of companies, detects job postings that your product augments or replaces, finds relevant people (the hiring manager, buyers, champions, users), and drafts personalized outreach using the job role as the hook. Tool-agnostic — works with any company source, job board, contact finder, and outreach platform.

Quality

72%

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/hiring-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 strongly actionable, clearly sequenced multi-step composite with explicit validation checkpoints and concrete search strings, contracts, and email frameworks. Its weaknesses are conciseness (some inferable rationale/prose) and progressive disclosure (monolithic single file with inline material that could be split into reference files).

Suggestions

Trim the "Why hiring signals work" paragraph and consolidate Tips into the relevant steps to reduce inferable prose.

Move the full Step 0 config questionnaires and the sample email templates into a references/ file (e.g. CONFIG.md, EMAIL_EXAMPLES.md) linked from the main body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete contracts and steps, but the "Why hiring signals work" rationale and Tips prose explain reasoning Claude could infer, and the full config questionnaires/sample emails make it longer than necessary; not the lean every-token-earns-its-place anchor at 3.	2 / 3
Actionability	Provides specific executable guidance — concrete search strings (e.g. `site:linkedin.com/jobs OR site:indeed.com "{company}" "{role}"`), typed input/output contracts, named email frameworks (Signal-Proof-Ask, BAB, PAS), per-touch word counts, and copy-ready sample subjects — matching the fully-actionable anchor.	3 / 3
Workflow Clarity	Steps 0–5 are clearly sequenced, each with Purpose/Input Contract/Process/Output Contract, and every step ends in an explicit Human Checkpoint validation gate ("Proceed with qualification? (Y/n)", "Approve before we draft emails?") with feedback loops, matching the clear-sequence-with-validation anchor.	3 / 3
Progressive Disclosure	Well-organized into sections but monolithic — no references/scripts/assets bundle exists and content that could be split (full config questionnaires, sample email templates) is inline, matching the structure-present-but-content-should-be-separate anchor at 2 rather than the one-level-deep-references anchor at 3.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 distinct, naming concrete actions and a clear hiring-signal niche, but it omits an explicit "Use when..." trigger clause and has only moderate coverage of natural trigger keywords. Completeness is therefore capped at 2 despite strong specificity and distinctiveness.

Suggestions

Add an explicit "Use when..." clause to the description (e.g. user mentions hiring signals, job postings to target, or wants outreach tied to open roles) so completeness can reach 3.

Broaden natural trigger terms in the description to include common phrasings like "cold email", "sales leads", or "target companies hiring".

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "detects job postings that your product augments or replaces, finds relevant people (the hiring manager, buyers, champions, users), and drafts personalized outreach" — matching the multiple-specific-actions anchor rather than the partial-actions anchor at 2.	3 / 3
Completeness	Clearly answers "what" with detailed actions but lacks an explicit "Use when..." trigger clause in the description, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Contains relevant natural terms ("hiring signal", "job postings", "outreach", "hiring manager") but offers limited coverage of common variations a user might say (e.g. "cold email", "leads", "job board"); the explicit trigger guidance lives in the body rather than the description.	2 / 3
Distinctiveness Conflict Risk	Targets a clear niche (hiring-signal-driven outreach using the job posting as the hook) with distinct triggers unlikely to fire for unrelated skills, rather than the overlapping-skill anchor at 2.	3 / 3
	Total	10 / 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 (534 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/hiring-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.