agent build
This commit is contained in:
93
skills/talent-pool-analysis.md
Normal file
93
skills/talent-pool-analysis.md
Normal file
@@ -0,0 +1,93 @@
|
||||
---
|
||||
id: talent-pool-analysis
|
||||
name: Talent Pool Analysis
|
||||
description: Analyse the talent already known to this workspace — who is in it, how they score, and who is available.
|
||||
category: hiring
|
||||
pages:
|
||||
- talent-pool
|
||||
status: active
|
||||
version: 1
|
||||
triggers:
|
||||
- talent pool
|
||||
- pool health
|
||||
- available talent
|
||||
- who is available
|
||||
- supply of talent
|
||||
owliver:
|
||||
enabled: true
|
||||
suggestions:
|
||||
- label: How healthy is the talent pool?
|
||||
capability: summary
|
||||
- label: Who is in the pool?
|
||||
capability: table
|
||||
- label: Strongest people in the pool
|
||||
capability: list
|
||||
capabilities:
|
||||
- summary
|
||||
- stats
|
||||
- table
|
||||
- list
|
||||
- progress
|
||||
- insight
|
||||
responses:
|
||||
summary:
|
||||
title: Talent pool
|
||||
source: talent.pool
|
||||
stats:
|
||||
title: Talent pool
|
||||
source: talent.pool
|
||||
table:
|
||||
title: Talent pool
|
||||
source: talent.pool
|
||||
list:
|
||||
title: Strongest in the pool
|
||||
source: talent.pool
|
||||
limit: 5
|
||||
progress:
|
||||
title: Talent pool
|
||||
source: talent.pool
|
||||
insight:
|
||||
title: Talent pool
|
||||
source: talent.pool
|
||||
---
|
||||
|
||||
# Talent Pool Analysis
|
||||
|
||||
## Purpose
|
||||
|
||||
- Report who this workspace already knows and could place.
|
||||
- Say how much of the pool has been assessed, and how much has not.
|
||||
- Report availability and certification coverage.
|
||||
|
||||
## Capabilities
|
||||
|
||||
- Summarize pool size, how many are scored, and average score.
|
||||
- List or tabulate people by score.
|
||||
- Report how many have availability on file and how many are certified.
|
||||
|
||||
## Data
|
||||
|
||||
Reads `talent.pool`, which counts `WorkerProfile` records — their `krow_score`,
|
||||
`availability`, `certifications` and stated role.
|
||||
|
||||
## Analysis
|
||||
|
||||
The average score is computed across **scored profiles only**. Counting an
|
||||
unassessed profile as zero would report a healthy pool as poor in exact
|
||||
proportion to how much of it nobody has got to yet — a figure that gets worse
|
||||
as the pool grows, which is the opposite of what it should do.
|
||||
|
||||
An unscored person is reported as "Not yet scored" rather than shown with a
|
||||
zero, because a zero reads as a bad assessment rather than an absent one.
|
||||
|
||||
## Output
|
||||
|
||||
Pool size, how many are scored and how many are not, average score across the
|
||||
scored, availability and certification counts, then people ranked by score.
|
||||
|
||||
## Limitations
|
||||
|
||||
- This is supply, not applicants. Someone in the pool has not applied to anything
|
||||
by being here, and must not be described as a candidate for a role.
|
||||
- Availability is what a person stated on their profile, not a live calendar.
|
||||
- A profile with no score is unassessed, which is not the same as being weak.
|
||||
Reference in New Issue
Block a user