design-talent-signal

Designs and reviews evidence-first recruiter product surfaces with provenance-preserving UI rules.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing recruiter-facing product surfaces risks losing evidence provenance, misrepresenting candidate state, or letting visual polish hide failed mutations. This Skill enforces a governed design process so every UI change to Talent Signal surfaces keeps facts traceable to source evidence and preserves recruiter control. ## Core Features & Use Cases - Surface classification and design reads: Classifies work across marketing pages, candidate cards and lists, living candidate pages, evidence review, timelines, relationship graphs, and iOS capture before any layout begins. - Provenance and state rules: Enforces one-click access to exact evidence, before/after change display, and distinct visual treatment for proposed, confirmed, edited, inferred, dismissed, and superseded states. - Relationship graph safeguards: Constrains graph design to typed, time-bounded, traceable edges with one-hop ego networks and no unexplained scoring. - Use Case: When redesigning a candidate card, use this Skill to verify semantic parity between Card and List views, trace a fact to its evidence, and test empty, ambiguous, and stale-evidence states. ## Quick Start Use the design-talent-signal skill to review my new candidate page layout for evidence provenance and state coverage.

Frequently Asked Questions about design-talent-signal

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

FAQPage Schema
How do I design a candidate profile UI that keeps evidence traceable?▼

Start by classifying the surface and mapping canonical entities, verified facts, and provenance paths before any layout. Place exact source evidence one click from every decision-relevant fact and show before-and-after states when a fact changes.

What UI states should an evidence review screen include?▼

Include loading, empty, insufficient evidence, proposed, confirmed, edited, dismissed, execution failed, expired, superseded, and deleted states. Never let a polished success state hide a failed or unverified mutation.

How should a relationship graph visualize recruiter networks?▼

Start with a one-hop ego network and expand to two hops only on request. Map edge width to confirmed interaction count, opacity to recency, use dashed edges for unverified relationships, and never display unexplained relationship scores.

Can this Skill be used for marketing site design?▼

Yes, it covers marketing narrative surfaces in addition to product UI. For marketing work it directs you to read the site's design documentation and allows more expressive composition than review or action surfaces.

When should visual weight not be used in recruiter UI design?▼

Visual weight must signal work attention, never candidate worth. Node size in graphs stays independent of human value, and no visual device may rank a person.