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

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/hiring-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.

The skill is highly actionable with an exceptionally clear, checkpointed workflow, but it is a long monolithic document that includes some conceptual padding and does not split any detail into reference files.

Suggestions

Move large, reusable blocks — the full sample email sequences and the complete per-step output contracts — into reference files under ./references/ and link to them one level deep from the body, improving progressive disclosure.

Trim or relocate the "Why hiring signals work" rationale and rationale-heavy Tips into an optional reference, keeping only the operational rule in the main body to improve conciseness.

Consider extracting the Step 0 configuration tables (role mapping, signal/contact/outreach config) into a CONFIG.md reference so the main workflow stays a lean overview.

Dimension	Reasoning	Score
Conciseness	Most of the body is dense operational content (contracts, tables, frameworks), but sections like the "Why hiring signals work" paragraph and several Tips restate sales rationale Claude already knows and could be trimmed.	3 / 5
Actionability	Provides fully actionable guidance: concrete search strings (e.g. `site:linkedin.com/jobs OR site:indeed.com "{company}" "{role}"`), explicit word-count rules per touch, named frameworks mapped to framings, and per-role example hooks covering the common cases.	5 / 5
Workflow Clarity	Steps 0–5 are clearly sequenced, each with a Purpose, Input/Output Contract, and an explicit Human Checkpoint approval gate ("Proceed with qualification? (Y/n)", "Approve before we draft emails?") forming validation feedback loops across the whole pipeline.	5 / 5
Progressive Disclosure	The ~505-line body is a single monolithic file with good section headings but no bundle/reference files; large blocks (full email examples, full contracts) are inlined rather than split out, and the one external pointer ("See that composite") is a cross-skill reference rather than a clearly-signaled bundled file.	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 concrete with strong distinctiveness, but it omits any "when to use" trigger clause, which caps completeness. Adding an explicit "Use when..." sentence would lift the weakest dimension.

Suggestions

Append a "Use when..." clause naming concrete triggers, 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 hiring-signal outreach."

Broaden trigger terms with user-natural synonyms such as "recruiting", "cold email", "prospecting", and "job boards" to improve trigger-term coverage.

Keep the third-person voice (currently correct: "Takes", "detects", "drafts") — do not introduce first/second person when editing.

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 using the job role as the hook" — covering the full input-to-outreach pipeline comprehensively.	5 / 5
Completeness	The "what" is explicit and concrete, but there is no "Use when..." trigger clause in the description — the trigger guidance lives only in the body's "When to Auto-Load" section, so per the rubric completeness is capped at 3.	3 / 5
Trigger Term Quality	Includes natural terms like "job postings", "hiring", "outreach", "hiring manager", and "job board", but is missing common synonyms a user might say such as "recruiting", "cold email", or "prospecting".	4 / 5
Distinctiveness Conflict Risk	The hiring-signal framing ("detects job postings that your product augments or replaces", "drafts personalized outreach using the job role as the hook") carves a clear niche, with only minor overlap risk against closely related outreach skills referenced elsewhere.	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: 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.