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

63%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, highly actionable composite workflow with explicit input/output contracts and human approval gates at every step. Its weaknesses are verbosity from repeated framing guidance and a purely monolithic layout: no reference files despite 530 lines, plus a Step 5 that is not self-contained.

Suggestions

Move the Step 0 configuration questionnaires and the Step 4 sample email sequences into reference files (e.g. references/config-questions.md, references/email-examples.md), keeping SKILL.md as a lean overview with clearly signaled one-level-deep links.

De-duplicate the framing/angle guidance repeated across Steps 2, 4, and Tips into a single section, and trim the 'Why hiring signals work' rationale to one or two lines.

Inline the Step 5 handoff process (or summarize its key steps) instead of deferring wholesale to funding-signal-outreach, and add brief guidance on iterating when a human checkpoint is rejected or a tool search returns no results.

Dimension	Reasoning	Score
Conciseness	The body is information-dense (contracts, tables, checkpoints) but includes a sales-rationale section ('Why hiring signals work') and repeats framing/angle guidance across Steps 2, 4, and the Tips section — more than minor trimming would be needed to tighten it. Not 2 because it never explains concepts Claude already knows and most sections earn their tokens.	3 / 5
Actionability	Concrete search query strings, classification rules, input/output contracts, word-count rules, and example hooks make the guidance mostly executable. Not 5 because Step 5 delegates its entire process to another skill ('Identical to funding-signal-outreach Step 5. See that composite'), leaving a self-containment gap.	4 / 5
Workflow Clarity	A clear 6-part sequence (Steps 0-5) with explicit human checkpoints ('Proceed with qualification? (Y/n)', 'Approve before we draft emails?') after each step. Not 5 because there are no feedback-loop instructions for what to do when a checkpoint is rejected or a tool call fails, and not 3 because checkpoints are explicit and present at every stage.	4 / 5
Progressive Disclosure	Sections are well-organized with clear headers, but all ~530 lines live inline in SKILL.md — the Step 0 config questionnaires and sample email sequences are prime candidates for separate reference files, and no bundle files (references/, scripts/, assets/) exist to offload detail. Not 4 because substantial content that should be separate is inline with no references at all.	3 / 5
	Total	14 / 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, well-scoped description that clearly enumerates the composite's actions and stays tool-agnostic without over-claiming. Its main deficiency is the absence of any 'Use when...' trigger guidance, which caps completeness and slightly weakens trigger-term coverage.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user has a list of companies and wants to find those hiring for roles their product replaces or augments, or mentions hiring signals, job-posting signals, or recruiting-based outreach.'

Add natural synonyms users would say, such as 'who's hiring', 'recruiting signals', or 'job-posting triggers', to broaden trigger-term coverage.

Lead the description with the distinctive trigger (hiring/job-posting signals) before the general outreach framing to reduce overlap with generic outreach skills.

Dimension	Reasoning	Score
Specificity	The description 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 using the job role as the hook' — covering the full pipeline comprehensively, matching the top anchor rather than leaving minor gaps.	5 / 5
Completeness	The 'what' is clear and detailed, but there is no 'Use when...' clause or equivalent explicit trigger guidance; the rubric guideline caps completeness at 3 for this case. It is not 2 because the 'what' is fully articulated, not vague.	3 / 5
Trigger Term Quality	Natural terms like 'hiring signal', 'job postings', 'outreach', 'job board', and 'contact finder' are present, but common variations a user might say ('who's hiring', 'recruiting', 'prospect', 'sales trigger') are missing.	4 / 5
Distinctiveness Conflict Risk	The hiring-signal niche is distinct and would rarely trigger the wrong skill, but the closing emphasis on 'drafts personalized outreach' creates minor overlap risk with generic cold-email/outreach skills. Not 5 because it does not carry a uniquely distinct trigger phrase to fully separate it from those.	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 (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: 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.