recruiting-trend-radar

Investigate and classify recruiting industry signals into product actions using curated source research.

1|Updated Aug 3, 2026
One-click install
npx skills add https://github.com/getyak/talent-signal --skill recruiting-trend-radar-getyak
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: recruiting-trend-radar
Source: https://github.com/getyak/talent-signal/tree/main/.agents/skills/recruiting-trend-radar
Command: npx skills add https://github.com/getyak/talent-signal --skill recruiting-trend-radar-getyak

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Recruiting product teams drown in trend noise—vendor announcements, viral posts, and syndicated headlines—without a disciplined way to decide which signals deserve attention. This Skill applies a Hung Lee–inspired manual curation lens to separate noise from genuine market shifts and translate them into concrete product decisions. ## Core Features & Use Cases - Signal Classification: Labels each finding as noise, weak_signal, emerging_pattern, or established_shift based on evidence independence, maturity, and counter-signals. - Structured Research Workflow: Enforces source diversity (primary, empirical, practitioner, counterarguments, APAC context), date separation, and disconfirming-evidence searches before any conclusion. - Product Translation: Converts relevant signals into watch, test, build, avoid, or no_action recommendations with revisit triggers. - Use Case: A product lead asks whether AI candidate-screening tools are an established shift; the Skill browses current sources, weighs vendor claims against practitioner evidence, and returns a calibrated review packet with a falsifiable experiment. ## Quick Start Use the recruiting-trend-radar skill to investigate current AI-in-hiring signals and recommend what Talent Signal should watch, test, or avoid this quarter.

Frequently Asked Questions about recruiting-trend-radar

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I research recruiting industry trends for product decisions?▼

Form a sharp question tied to a specific product decision, then browse current primary, empirical, practitioner, and counterargument sources. Classify each finding as noise, weak signal, emerging pattern, or established shift, and translate only relevant signals into watch, test, build, avoid, or no_action recommendations.

How to separate real hiring-AI shifts from vendor hype?▼

Separate event date, publication date, vendor claim, practitioner signal, and independent evidence for every claim. Search actively for disconfirming evidence and second-order effects, and never count syndicated copies of a story as independent support.

What sources should a recruiting market scan include?▼

A credible scan mixes primary product or policy sources, empirical research, practitioner observations, credible counterarguments, and China/APAC context when relevant. The skill requires browsing current sources on every run rather than relying on cached knowledge.

Can this skill evaluate or rank job candidates?▼

No. This is a market research skill, not a candidate evaluator. Its guardrails explicitly prohibit evaluating candidates or making automated employment recommendations; it only assesses industry trends and their product implications.

What are the limitations of trend-based product research?▼

Newsletter inclusion is not validation, trend volume is not product-market fit, and viral examples should not outrank local user behavior. Classifications must record what evidence or date would change them, since editorial curation is not scientific validation.