Outreach
andrew-shwetzer/career-ops-plugin-do-not-fork-currently-updating-v2-
Draft personalized outreach messages for LinkedIn connections, hiring managers, or recruiters.
End-to-end hiring signal composite. An agent skill from gooseworks-ai/goose-skills.
$ npx skills add gooseworks-ai/goose-skills --skill hiring-signal-outreach -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gooseworks-ai/goose-skills hiring-signal-outreach --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/outreach/composites/hiring-signal-outreach .claude/skills/hiring-signal-outreach && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "hiring-signal-outreach" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/outreach/composites/hiring-signal-outreach into .claude/skills/hiring-signal-outreach/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hiring-signal-outreach", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/gooseworks-ai/goose-skills/tree/main/skills/outreach/composites/hiring-signal-outreachType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add gooseworks-ai/goose-skills --skill hiring-signal-outreach -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gooseworks-ai/goose-skills hiring-signal-outreach --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/outreach/composites/hiring-signal-outreach .agents/skills/hiring-signal-outreach && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "hiring-signal-outreach" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/outreach/composites/hiring-signal-outreach into .agents/skills/hiring-signal-outreach/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hiring-signal-outreach", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add gooseworks-ai/goose-skills --skill hiring-signal-outreach -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gooseworks-ai/goose-skills hiring-signal-outreach --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/outreach/composites/hiring-signal-outreach .cursor/skills/hiring-signal-outreach && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "hiring-signal-outreach" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/outreach/composites/hiring-signal-outreach into .cursor/skills/hiring-signal-outreach/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hiring-signal-outreach", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/gooseworks-ai/goose-skills.git --path skills/outreach/composites/hiring-signal-outreach--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add gooseworks-ai/goose-skills --skill hiring-signal-outreach -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gooseworks-ai/goose-skills hiring-signal-outreach --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/outreach/composites/hiring-signal-outreach .gemini/skills/hiring-signal-outreach && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "hiring-signal-outreach" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/outreach/composites/hiring-signal-outreach into .gemini/skills/hiring-signal-outreach/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hiring-signal-outreach", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install gooseworks-ai/goose-skills hiring-signal-outreachInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add gooseworks-ai/goose-skills --skill hiring-signal-outreach -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/outreach/composites/hiring-signal-outreach .github/skills/hiring-signal-outreach && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "hiring-signal-outreach" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/outreach/composites/hiring-signal-outreach into .github/skills/hiring-signal-outreach/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hiring-signal-outreach", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add gooseworks-ai/goose-skills --skill hiring-signal-outreach -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gooseworks-ai/goose-skills hiring-signal-outreach --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/outreach/composites/hiring-signal-outreach .opencode/skills/hiring-signal-outreach && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "hiring-signal-outreach" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/outreach/composites/hiring-signal-outreach into .opencode/skills/hiring-signal-outreach/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hiring-signal-outreach", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
hiring-signal-outreachEnd-to-end hiring signal composite. An agent skill from gooseworks-ai/goose-skills.
Hiring Signal Outreach is an agent skill from gooseworks-ai/goose-skills. 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.
Its SKILL.md is about 5.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `skill.meta.json`).
It sits in Business, Finance & HR, covering Recruiting and HR and Cold outreach. The repository describes itself as: Library of Growth & GTM skills + data APIs for Claude Code, Codex, Cursor to run ads, social, content, lead gen, seo and data scraping. The licence is MIT.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit c650c6d. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Hiring Signal Outreach loads about 5.1k tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 1,642 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from gooseworks-ai/goose-skills at commit c650c6d, republished under its MIT licence (© gooseworks-ai). 1,642 words, ~5,105 tokens.
.claude/skills/hiring-signal-outreach/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Detects job postings at target companies where the role being hired for is one your product augments, replaces, or directly supports. Finds the right people to contact (not just the person being hired — the hiring manager, budget holder, and potential champions), then drafts personalized outreach using the job posting as the hook.
Why hiring signals work: When a company posts a job, they've already acknowledged the problem your product solves. They've budgeted for it (headcount is budget). They're actively evaluating how to solve it. Your email arrives at exactly the moment they're thinking about this problem — and you're offering a faster, cheaper, or complementary solution.
Load this composite when:
On first run for a client/user, collect and store these preferences. Skip on subsequent runs.
| Question | Purpose | Stored As |
|---|---|---|
| What does your product do? (1-2 sentences) | Match against job descriptions | company_description |
| What job roles does your product replace? | Strongest signal — they're hiring for what you automate | roles_replaced |
| What job roles does your product augment? | Good signal — your product makes this person more effective | roles_augmented |
| What job roles buy your product? | Contact finding — who holds the budget | buyer_titles |
| What job roles champion your product? | Contact finding — who feels the pain daily | champion_titles |
| What job roles use your product? | Contact finding — who would operate it | user_titles |
| What keywords in a job description indicate relevance? | Filters out false positives | jd_keywords |
Example for an AI calling product:
roles_replaced: ["BDC Representative", "Call Center Agent", "Appointment Setter"]
roles_augmented: ["Sales Manager", "BDC Manager", "Service Advisor"]
buyer_titles: ["VP Sales", "Director of Operations", "General Manager", "COO"]
champion_titles: ["BDC Manager", "Sales Manager", "Fixed Ops Director"]
user_titles: ["BDC Rep", "Service Advisor", "Sales Consultant"]
jd_keywords: ["inbound calls", "outbound calls", "appointment setting", "customer follow-up"]| Question | Options | Stored As |
|---|---|---|
| How should we find job postings? | LinkedIn Jobs / Indeed / Apollo / Google Jobs / Web search | job_search_tool |
| How far back should we look? | 7 / 14 / 30 days | lookback_days |
| Question | Options | Stored As |
|---|---|---|
| How should we find contacts at these companies? | Apollo / LinkedIn / Clearbit / Web search | contact_tool |
| Question | Options | Stored As |
|---|---|---|
| Where do you want outreach sent? | Smartlead / Instantly / Outreach.io / Lemlist / CSV export | outreach_tool |
| Email or multi-channel? | Email only / Email + LinkedIn | outreach_channels |
| Question | Purpose | Stored As |
|---|---|---|
| What problem do you solve? | Email hook | pain_point |
| Name 2-3 proof points (customers, metrics, results) | Email credibility | proof_points |
| What's the cost comparison vs. a full-time hire? | ROI angle for outreach | cost_comparison |
| How fast can you deploy vs. a new hire? | Speed angle | deployment_speed |
Store config in: clients/<client-name>/config/signal-outreach.json or equivalent.
Purpose: For each company in the input list, find active job postings that match roles your product replaces or augments.
companies: [
{
name: string # Required
domain: string # Required
industry?: string # Optional
size?: string # Optional
}
]
roles_replaced: string[] # From config
roles_augmented: string[] # From config
jd_keywords: string[] # From config
lookback_days: integer # From config (default: 14)For each company (or in batches):
Search for job postings using the configured job_search_tool:
company_name + role_title for each role in roles_replaced and roles_augmentedsite:linkedin.com/jobs OR site:indeed.com "{company}" "{role}""{company_name}" AND ("hiring" OR "job" OR "careers") AND ("{role_1}" OR "{role_2}")For each job posting found, extract:
Classify each posting:
roles_replaced. Your product could eliminate or reduce the need for this hire. This is the strongest signal.roles_augmented. Your product makes this person more effective — they'd want it as a tool. Good signal.jd_keywords. Weaker signal — verify relevance.Filter: Drop companies with no matching job postings. Drop postings older than lookback_days.
companies_hiring: [
{
company: {
name: string
domain: string
industry: string
}
job_postings: [
{
title: string
location: string
posted_date: string
description_summary: string # 2-3 sentence summary of the role
source_url: string
signal_type: "replaces" | "augments" | "keyword_match"
relevance_reasoning: string # Why this posting matters for your product
}
]
posting_count: integer
strongest_signal: "replaces" | "augments" | "keyword_match"
}
]Found hiring signals at X of Y companies:
| Company | Postings | Strongest Signal | Top Role | Posted |
|---------|----------|-----------------|----------|--------|
| Acme Corp | 3 | Replaces | BDC Representative | 3 days ago |
| Beta Inc | 1 | Augments | Sales Manager | 1 week ago |
| ... | ... | ... | ... | ... |
Signal breakdown: X "replaces" (strongest), Y "augments", Z "keyword match"
Proceed with qualification? (Y/n)Purpose: Rank companies by outreach priority based on signal strength, relevance, and timing. Pure LLM reasoning — inherently tool-agnostic.
companies_hiring: [...] # From Step 1 output
your_company: {
description: string
pain_point: string
proof_points: string[]
cost_comparison: string
deployment_speed: string
}For each company, evaluate:
| Criterion | Weight | How to Assess |
|---|---|---|
| Signal type | Highest | "Replaces" > "Augments" > "Keyword match" |
| Posting volume | High | Multiple relevant postings = scaling that function = bigger need |
| Recency | High | Posted <7 days ago = actively evaluating. 14+ days = may have candidates already |
| Role seniority | Medium | Hiring a VP of the function you sell into = strategic buy. Hiring an individual contributor = operational buy. Both are good, different approach. |
| Industry fit | Medium | Is their industry one where your product has proven results? |
For each qualified company, generate:
qualified_companies: [
{
...company_hiring_fields,
priority_tier: "tier_1" | "tier_2" | "tier_3"
relevance_reasoning: string
outreach_angle: string
recommended_framing: "replace" | "complement" | "scale"
}
]
dropped_companies: [
{ name: string, drop_reason: string }
]## Qualification Results
### Tier 1 — Act Today (X companies)
| Company | Signal | Top Role | Framing | Angle |
|---------|--------|----------|---------|-------|
| Acme Corp | Replaces | BDC Rep (x3) | Replace | Before you hire 3 BDC reps... |
### Tier 2 — Act This Week (X companies)
| ... |
### Tier 3 — Queue (X companies)
| ... |
### Dropped (X companies)
| Company | Reason |
|---------|--------|
| ... | ... |
Approve this list before we find contacts?Purpose: For each qualified company, find the right people to contact. Unlike the funding composite, here we also identify who posted the job (the hiring manager) — they're often the best first contact.
qualified_companies: [...] # From Step 2 output
buyer_titles: string[] # From config
champion_titles: string[] # From config
user_titles: string[] # From config
max_contacts_per_company: integer # Default: 3-5For each qualified company, use the configured contact_tool:
First: Identify the hiring manager. The person who posted or owns the job posting is the most relevant contact.
Second: Find buyer-level contacts. People with buyer_titles at this company — they control budget.
Third: Find champions. People with champion_titles — they feel the pain daily and can advocate internally.
Classify each contact:
Cap at max_contacts_per_company. Prioritize: hiring manager > buyer > champion > user.
contacts: [
{
person: {
full_name: string
first_name: string
last_name: string
title: string
email: string | null
linkedin_url: string | null
role_type: "hiring_manager" | "buyer" | "champion" | "user"
}
company: {
name: string
domain: string
priority_tier: string
outreach_angle: string
recommended_framing: string
}
job_context: {
relevant_posting_title: string # The job posting that triggered this signal
signal_type: string # "replaces" or "augments"
posting_url: string
description_summary: string
}
}
]## Contacts Found
### Acme Corp (Tier 1 — Hiring 3x BDC Reps, "Replace" framing)
| Name | Title | Role Type | Email | LinkedIn |
|------|-------|-----------|-------|----------|
| Sarah Chen | VP Sales | Hiring Manager | sarah@acme.com | ... |
| Mike Johnson | COO | Buyer | mike@acme.com | ... |
| Lisa Park | BDC Manager | Champion | lisa@acme.com | ... |
Relevant posting: "BDC Representative" (posted 3 days ago)
### Beta Inc (Tier 2 — Hiring Sales Manager, "Complement" framing)
| ... |
Total: X contacts across Y companies
Approve before we draft emails?Purpose: For each contact, draft a personalized email sequence using three layers of personalization: the job posting context, your company's value, and the prospect's company context. Pure LLM reasoning — inherently tool-agnostic.
contacts: [...] # From Step 3 output (includes job_context per contact)
your_company: {
description: string
pain_point: string
proof_points: string[]
cost_comparison: string # e.g. "4x cheaper than a full-time hire"
deployment_speed: string # e.g. "Live in 2 weeks vs. 3-month hiring cycle"
}
sequence_config: {
touches: integer # Default: 3
timing: integer[] # Default: [1, 5, 12]
personalization_tier: 1 | 2 | 3
tone: string
cta: string
}Select framework based on framing:
Build three layers of personalization per contact:
| Layer | Source | Used In |
|---|---|---|
| Job posting context | Step 1 — the specific role, responsibilities, what the JD says | Subject line + hook |
| Your company context | Config — what you do, proof points, cost comparison | Body — proof + offer |
| Prospect company context | Step 2 — industry, what they do, why they're hiring | Body — relevance framing |
Adapt email angle by role_type:
| Role Type | Email Angle | Example Hook |
|---|---|---|
| Hiring manager | "Before you fill that role" | "I saw you're hiring a BDC Rep — before you finalize that, worth seeing what [product] does instead." |
| Buyer | Cost/ROI comparison | "You're budgeting for 3 BDC reps ($180K/year). [Product] handles the same workload for a fraction of that." |
| Champion | "This will make your life easier" | "When your new BDC rep starts, they'll need tools to be effective from day one. That's what [product] does." |
| User | "You'll want this on your desk" | "If you're scaling the BDC function at [company], [product] handles [task] so you can focus on [higher-value work]." |
Follow email-drafting skill rules:
email_sequences: [
{
contact: { full_name, email, title, role_type, company_name }
job_context: { posting_title, signal_type }
sequence: [
{
touch_number: integer
send_day: integer
subject: string
body: string
framework: string
personalization_layers: {
job_posting: string # What from the JD was referenced
company_context: string # What proof/value was used
prospect_context: string # What about their company was referenced
}
word_count: integer
}
]
}
]Present 3-5 sample sequences showing each role_type and framing:
## Sample Emails for Review
### Hiring Manager: Sarah Chen, VP Sales @ Acme Corp
Signal: Hiring 3x BDC Representatives | Framing: Replace
**Touch 1 — Day 1**
Subject: Before you fill those BDC roles
> Hi Sarah — I noticed Acme is hiring three BDC reps. Before you go through
> a 3-month hiring cycle, worth seeing what companies like [peer] are doing
> instead...
> [full email]
### Buyer: Mike Johnson, COO @ Acme Corp
Signal: Same | Framing: ROI
**Touch 1 — Day 1**
Subject: $180K/year in BDC hires — or this
> Hi Mike — Acme's hiring 3 BDC reps. At ~$60K each fully loaded, that's
> $180K/year. [Product] handles the same call volume for...
> [full email]
---
Approve these samples? I'll generate the rest in the same style.Identical to funding-signal-outreach Step 5. Package contacts + email sequences for the configured outreach tool. See that composite for the full handoff process.
campaign_package: {
tool: string
file_path: string
contact_count: integer
sequence_touches: integer
estimated_send_days: integer
next_action: string
}## Campaign Ready
Tool: [configured tool]
Signal type: Hiring signal
Contacts: X people across Y companies
Sequence: 3 touches over 12 days
Ready to launch?| Step | Tool Dependency | Human Checkpoint | Typical Time |
|---|---|---|---|
| 0. Config | None | First run only | 5 min (once) |
| 1. Detect | Configurable (LinkedIn Jobs, Indeed, web search) | Review companies with postings | 2-5 min |
| 2. Qualify | None (LLM reasoning) | Approve tier rankings | 2-3 min |
| 3. Find People | Configurable (Apollo, LinkedIn, etc.) | Approve contact list | 2-3 min |
| 4. Draft Emails | None (LLM reasoning) | Review samples, iterate | 5-10 min |
| 5. Handoff | Configurable (Smartlead, CSV, etc.) | Final launch approval | 1 min |
Total human review time: ~15-20 minutes
© gooseworks-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in skills/outreach/composites/hiring-signal-outreach of gooseworks-ai/goose-skills.
Open the folder on GitHubat commit c650c6d
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in gooseworks-ai/goose-skills, which our catalogue first saw on October 7, 2026.
Hiring Signal Outreach next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Hiring Signal Outreach this skillgooseworks-ai/goose-skills | 1.2k | 1 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Outreachandrew-shwetzer/career-ops-plugin-do-not-fork-currently-updating-v2- | 502 | — | ~939 | Automated safety check: Pass | MIT | |
| Sourcing Outreachshawnpang/startup-founder-skills | 343 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Networking Outreachmohitagw15856/pm-claude-skills | 1.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| LinkedIn MCP Usage Rulesstickerdaniel/linkedin-mcp-server | 3.8k | — | ~651 | Automated safety check: Pass | Apache-2.0 | |
| Outreach Messagemohitagw15856/pm-claude-skills | 1.4k | — | ~827 | Automated safety check: Pass | MIT |
andrew-shwetzer/career-ops-plugin-do-not-fork-currently-updating-v2-
Draft personalized outreach messages for LinkedIn connections, hiring managers, or recruiters.
shawnpang/startup-founder-skills
When the user needs to write recruiting outreach messages to attract passive candidates or request referrals.
mohitagw15856/pm-claude-skills
Write networking messages that actually get replies — warm, specific, and easy to say yes to — for reconnecting, cold outreach, referrals, or asking for advice.
stickerdaniel/linkedin-mcp-server
Rules for using the bundled LinkedIn MCP server for profile, company, job, post, feed and inbox work, with explicit authorization required for messages and connection requests.
mohitagw15856/pm-claude-skills
Write cold outreach and networking messages that actually get replies.
apify/awesome-skills
Set up a recurring buying-signal detection pipeline that finds companies showing buying intent across three signal types — job postings (hiring for the persona), fundraising events (recent raises)…
gooseworks-ai/goose-skills
Scrape and search Reddit posts using Apify. An agent skill from gooseworks-ai/goose-skills.
gooseworks-ai/goose-skills
Generate or edit an image via any FAL image model (nano-banana edit, gpt-image, flux, ...), ROUTED THROUGH THE fal-proxy so it bills the Ads agent.
gooseworks-ai/goose-skills
Replace an existing video's opening with a supplied clip or free kinetic text hook while retaining and verifying every original body frame, audio, captions and ending.
gooseworks-ai/goose-skills
Scrape blog posts via RSS feeds (free, no API key) with Apify fallback for JS-heavy sites.
gooseworks-ai/goose-skills
Find leads by scraping engagers from a competitor's top LinkedIn posts.
gooseworks-ai/goose-skills
Assemble a ChatGPT chat-reveal video ad from a thread + timeline JSON — one continuous Playwright recording of a ChatGPT mobile chat (user types with the iOS keyboard up → taps send → keyboard…
Categories
End-to-end hiring signal composite. An agent skill from gooseworks-ai/goose-skills. Hiring Signal Outreach is an agent skill from gooseworks-ai/goose-skills. End-to-end hiring signal composite.
Hiring Signal Outreach fits situations like: tasks that involve Recruiting and HR; tasks that involve Cold outreach.
Run `npx skills add gooseworks-ai/goose-skills --skill hiring-signal-outreach -a claude-code`. Or copy the skill folder (skills/outreach/composites/hiring-signal-outreach in gooseworks-ai/goose-skills) into .claude/skills/hiring-signal-outreach in your project. Claude Code loads it when a task matches its description.
Run `npx skills add gooseworks-ai/goose-skills --skill hiring-signal-outreach -a codex`. Or copy the skill folder (skills/outreach/composites/hiring-signal-outreach in gooseworks-ai/goose-skills) into .agents/skills/hiring-signal-outreach in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gooseworks-ai/goose-skills --skill hiring-signal-outreach -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hiring-signal-outreach, .gemini/skills/hiring-signal-outreach, .github/skills/hiring-signal-outreach and .opencode/skills/hiring-signal-outreach in your project.
SKILL.md names no scripts, command-line tools or credentials: Hiring Signal Outreach is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Hiring Signal Outreach is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 5.1k tokens (SKILL.md is roughly 20k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Hiring Signal Outreach: Outreach (andrew-shwetzer/career-ops-plugin-do-not-fork-currently-updating-v2-, 502 stars), Sourcing Outreach (shawnpang/startup-founder-skills, 343 stars), Networking Outreach (mohitagw15856/pm-claude-skills, 1.4k stars) and LinkedIn MCP Usage Rules (stickerdaniel/linkedin-mcp-server, 3.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
gooseworks-ai (a GitHub organization) maintains it in gooseworks-ai/goose-skills, which has 1,240 GitHub stars. The repository holds 273 skills in this directory. The repository was last updated on October 8, 2026.
Source: gooseworks-ai/goose-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.