Agent skill

People Analytics

by borghei in borghei/Claude-Skills

People analytics across workforce metrics, predictive modeling, and employee insights.

MITAuto-check passedBusiness, Finance & HR

Install People Analytics

skills CLI
$ npx skills add borghei/Claude-Skills --skill people-analytics -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install borghei/Claude-Skills people-analytics --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/hr-operations/people-analytics .claude/skills/people-analytics && rm -rf skills-src

Use ~/.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/

Facts

Skill name
people-analytics
GitHub stars
881
Token cost
~4.7k tokens
SKILL.md length
1,509 words
Files
4 (incl. scripts)
Skills in repo
349
Repo updated
First seen
Licence
MIT

At a glance

People analytics across workforce metrics, predictive modeling, and employee insights.

  • Works in 6 steps: Frame the question -- Clarify the… → Assess data readiness -- Identify… → Analyze -- Apply the appropriate method… → …
  • Building turnover models
  • SKILL.md covers Clarify First, Workflow, Analytics Maturity Model and Core HR Metrics, plus 11 more sections
  • Runs Python scripts from its folder; calls python

What it does

People Analytics is an agent skill from borghei/Claude-Skills. People analytics across workforce metrics, predictive modeling, and employee insights. Use when building turnover models, analyzing engagement surveys, running pay equity regressions, or scoring flight risk.

Its SKILL.md is about 4.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `scripts/attrition_predictor.py`, `scripts/headcount_planner.py` and `scripts/survey_analyzer.py`).

It sits in Business, Finance & HR. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.

When your agent uses it

  • Building turnover models
  • Analyzing engagement surveys
  • Running pay equity regressions
  • Scoring flight risk

Example prompts

  • “/people-analytics”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Frame the question -- Clarify the business question with the HR or business stakeholder. Examples: "Why is Sales attrition 2x the company…
  2. Assess data readiness -- Identify required data sources (HRIS, ATS, survey platform, payroll). Check for completeness, recency, and…
  3. Analyze -- Apply the appropriate method from the analytics toolkit (descriptive stats, regression, classification, segmentation). Document…
  4. Validate findings -- Sense-check results with domain experts (HRBPs, managers). Test for statistical significance and practical…
  5. Recommend -- Translate findings into 2-3 specific, actionable recommendations with expected impact and cost.
  6. Deliver and monitor -- Present insights using the dashboard framework. Set up ongoing monitoring for key metrics with alert thresholds.

What it can do on your machine

Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    Ships 3 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

People Analytics loads about 4.7k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 1,509 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~56
When it runs · the whole SKILL.md, loaded when a task matches
~4.7k

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.

Safety

Auto-check passed

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); the scripts in this folder are not scanned.

SKILL.md

The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 1,509 words, ~4,693 tokens.

Download SKILL.mdSave it as .claude/skills/people-analytics/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
people-analytics
description
People analytics across workforce metrics, predictive modeling, and employee insights. Use when building turnover models, analyzing engagement surveys, running pay equity regressions, or scoring flight risk.
license
MIT + Commons Clause
metadata.version
1.0.0
metadata.author
borghei
metadata.category
hr-operations
metadata.updated
2026-03-31
metadata.tags
people-analytics, hr-metrics, workforce, insights, predictive

People Analytics

The agent operates as a senior people analytics partner, translating workforce data into actionable insights using statistical modeling, segmentation analysis, and data governance best practices.

Clarify First

Before generating the analysis, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • Business question + success metric — frames the entire analysis (step 1); a vague question yields an unfocused output
  • Analysis type (descriptive, attrition risk, pay equity, or engagement driver) — selects the method and which script applies
  • Available data sources + their quality/completeness — determines which method is even possible (step 2)
  • Segments + privacy threshold (minimum group size) — drives segmentation and the anonymization/aggregation applied

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Workflow

  1. Frame the question -- Clarify the business question with the HR or business stakeholder. Examples: "Why is Sales attrition 2x the company average?" or "Are we paying equitably across gender?" Define the success metric for the analysis.
  2. Assess data readiness -- Identify required data sources (HRIS, ATS, survey platform, payroll). Check for completeness, recency, and quality. Flag any gaps before proceeding.
  3. Analyze -- Apply the appropriate method from the analytics toolkit (descriptive stats, regression, classification, segmentation). Document assumptions and limitations.
  4. Validate findings -- Sense-check results with domain experts (HRBPs, managers). Test for statistical significance and practical significance. Check predictive models for bias across protected groups.
  5. Recommend -- Translate findings into 2-3 specific, actionable recommendations with expected impact and cost.
  6. Deliver and monitor -- Present insights using the dashboard framework. Set up ongoing monitoring for key metrics with alert thresholds.

Checkpoint: After step 2, confirm that all data has been anonymized or aggregated to comply with privacy policy before analysis begins.

Analytics Maturity Model

LevelNameCapabilitiesTypical Questions Answered
1Operational ReportingHeadcount, compliance, ad-hoc queries"How many people do we have?"
2Advanced ReportingDashboards, trends, benchmarking, segmentation"How has attrition changed by quarter?"
3AnalyticsStatistical analysis, correlation, root cause"What drives attrition in Sales?"
4PredictiveTurnover prediction, performance modeling, risk scoring"Who is likely to leave in the next 6 months?"
5PrescriptiveAutomated recommendations, real-time interventions"What should we do to retain this person?"

Core HR Metrics

Workforce Metrics
MetricFormulaBenchmark
Turnover Rate(Separations / Avg HC) x 10010-15%
Retention Rate(Retained / Starting HC) x 10085-90%
Time to FillDays from req open to offer accept30-45 days
Cost per HireTotal recruiting cost / Hires$3-5K
Regrettable TurnoverRegrettable exits / Total exits< 30%
Performance Metrics
MetricFormulaBenchmark
High Performers% rated top tier15-20%
Goal CompletionGoals achieved / Goals set80%+
Promotion RatePromotions / Headcount8-12%
Engagement Metrics
MetricFormulaBenchmark
eNPSPromoters % - Detractors %20-40
Engagement ScoreSurvey composite (1-100)70%+
AbsenteeismAbsent days / Work days< 3%

Turnover Prediction Model

python
import pandas as pd
from sklearn.ensemble import RandomForestClassifier
from sklearn.model_selection import train_test_split
from sklearn.metrics import classification_report

def build_turnover_model(employee_data: pd.DataFrame) -> dict:
    """
    Build and evaluate a turnover prediction model.

    Input: DataFrame with columns for features + 'left_company' (0/1).
    Output: dict with model, feature importance, and evaluation metrics.
    """
    features = [
        'tenure_months', 'salary_ratio_to_market', 'performance_rating',
        'months_since_last_promotion', 'manager_tenure', 'team_size',
        'engagement_score', 'training_hours_ytd', 'projects_completed'
    ]

    X = employee_data[features]
    y = employee_data['left_company']

    X_train, X_test, y_train, y_test = train_test_split(
        X, y, test_size=0.2, random_state=42, stratify=y
    )

    model = RandomForestClassifier(n_estimators=100, random_state=42)
    model.fit(X_train, y_train)

    y_pred = model.predict(X_test)
    report = classification_report(y_test, y_pred, output_dict=True)

    importance = (
        pd.DataFrame({'feature': features, 'importance': model.feature_importances_})
        .sort_values('importance', ascending=False)
    )

    return {'model': model, 'importance': importance, 'evaluation': report}


def score_flight_risk(model, current_employees: pd.DataFrame) -> pd.DataFrame:
    """
    Score current employees for flight risk.

    Returns DataFrame with employee_id, flight_risk_score (0-1), and risk_level.
    """
    probabilities = model.predict_proba(current_employees[model.feature_names_in_])[:, 1]

    risk_levels = pd.cut(
        probabilities,
        bins=[0, 0.25, 0.50, 0.75, 1.0],
        labels=['Low', 'Medium', 'High', 'Critical']
    )

    return pd.DataFrame({
        'employee_id': current_employees['employee_id'],
        'flight_risk_score': probabilities.round(3),
        'risk_level': risk_levels
    }).sort_values('flight_risk_score', ascending=False)

Example: Sales Attrition Root-Cause Analysis

QUESTION
  Sales voluntary turnover is 22% vs 12% company average. Why?

DATA
  Source: HRIS + engagement survey + exit interviews (n=45 exits, trailing 12 mo)

ANALYSIS
  Segmentation by tenure band:
    < 1 yr: 35% of exits (onboarding/ramp issues)
    1-2 yr: 40% of exits (comp dissatisfaction + career path)
    2+ yr: 25% of exits (manager relationship)

  Regression on exit survey scores (n=38 respondents):
    Top drivers of intent-to-leave:
      1. "I am paid fairly" (beta = -0.42, p < 0.01)
      2. "I see a career path here" (beta = -0.31, p < 0.01)
      3. "My manager supports my development" (beta = -0.28, p < 0.05)

  Compensation benchmark:
    Sales IC3 compa-ratio: 0.88 (12% below midpoint)
    Sales IC2 compa-ratio: 0.91 (9% below midpoint)
    Rest of company average: 0.98

FINDINGS
  1. Sales comp is significantly below market, especially at IC2-IC3
  2. No defined career ladder for Sales ICs beyond IC3
  3. New hires (< 1 yr) leaving due to unrealistic ramp expectations

RECOMMENDATIONS
  1. Market adjustment: Bring Sales IC2-IC3 to 95th percentile compa-ratio ($180K budget)
  2. Publish a Sales career ladder through IC5 with clear promotion criteria
  3. Redesign onboarding: extend ramp period from 30 to 90 days with milestone targets

EXPECTED IMPACT
  Reduce Sales attrition from 22% to 14-16% within 12 months
  ROI: $180K adjustment saves ~$450K in replacement costs (10 fewer exits x $45K/hire)

Pay Equity Analysis

python
import pandas as pd
import statsmodels.api as sm

def analyze_pay_equity(employee_data: pd.DataFrame) -> dict:
    """
    Conduct pay equity analysis controlling for legitimate pay factors.

    Returns raw gap, adjusted gap, model fit, and employees flagged for review.
    """
    # Raw gap
    avg_by_gender = employee_data.groupby('gender')['salary'].mean()
    raw_gap = (avg_by_gender['Female'] - avg_by_gender['Male']) / avg_by_gender['Male']

    # Adjusted gap (control for level, tenure, performance, location)
    controls = pd.get_dummies(
        employee_data[['job_level', 'tenure_years', 'performance_rating', 'department', 'location']],
        drop_first=True
    )
    controls = sm.add_constant(controls)
    controls['is_female'] = (employee_data['gender'] == 'Female').astype(int)

    model = sm.OLS(employee_data['salary'], controls).fit()
    adjusted_gap = model.params['is_female']

    # Flag outliers (residual > 2 std dev)
    employee_data['predicted'] = model.predict(controls)
    employee_data['residual'] = employee_data['salary'] - employee_data['predicted']
    threshold = 2 * employee_data['residual'].std()
    flagged = employee_data[abs(employee_data['residual']) > threshold]

    return {
        'raw_gap_pct': round(raw_gap * 100, 1),
        'adjusted_gap_usd': round(adjusted_gap, 0),
        'model_r_squared': round(model.rsquared, 3),
        'employees_flagged': len(flagged),
        'flagged_details': flagged[['employee_id', 'salary', 'predicted', 'residual']]
    }

Engagement Survey Analysis

  1. Calculate response rate -- Target 80%+ for statistical validity. Flag departments below 60%.
  2. Compute category scores -- Average Likert responses by category (Manager, Growth, Culture, Compensation). Compare to prior period.
  3. Run driver analysis -- Regress category scores against overall engagement to identify which categories have the highest impact on engagement.
  4. Segment -- Break results by department, level, tenure band, and location. Identify where scores diverge most from company average.
  5. Prioritize -- Plot categories on a 2x2 matrix (Impact vs Score). "High impact, low score" quadrant = priority action areas.

Checkpoint: Suppress results for any segment with fewer than 5 respondents to protect anonymity.

DEI Metrics Framework

DomainMetricsData Source
RepresentationGender / ethnicity distribution by levelHRIS
Pay equityRaw gap, adjusted gap (controlled regression)Payroll + HRIS
ProgressionPromotion rates by demographic groupHRIS
HiringOffer and accept rates by demographic groupATS
InclusionInclusion index, belonging score, psychological safetySurvey

Data Governance Checklist

Before starting any people analytics project:

  • Business question and purpose clearly documented
  • Data minimization applied (only collect what is needed)
  • Privacy impact assessment completed
  • Anonymization or aggregation applied where possible
  • Predictive models tested for bias across protected groups
  • Role-based access controls implemented
  • Data retention policy defined
  • Employee communication planned (transparency principle)

Scripts

bash
# Analyze engagement survey results with driver analysis
python scripts/survey_analyzer.py --file survey_results.csv
python scripts/survey_analyzer.py --file survey_results.csv --prior prior_survey.csv --json

# Score attrition risk from employee data
python scripts/attrition_predictor.py --file employees.csv
python scripts/attrition_predictor.py --file employees.csv --threshold 0.7 --json

# Workforce headcount planning calculations
python scripts/headcount_planner.py --file workforce.csv --growth 0.15 --attrition 0.12
python scripts/headcount_planner.py --file workforce.csv --growth 0.15 --attrition 0.12 --json

Troubleshooting

ProblemRoot CauseResolution
Low survey response rate (< 70%)Survey fatigue, lack of trust in anonymity, or no visible action from prior surveysShorten survey to 15-20 questions max; communicate anonymity safeguards clearly; publish and act on top 3 findings from prior survey before launching next one
Attrition model produces too many false positivesOverfitting on historical data, missing key features, or class imbalanceAdd regularization; use SMOTE or class weights to handle imbalance; validate with cross-validation not just train/test split; include manager quality and comp-ratio as features
Stakeholders distrust analytics findingsResults contradict lived experience, or methodology is opaquePresent methodology transparently; validate findings with HRBPs before publishing; use confidence intervals not point estimates; start with descriptive analytics to build trust before predictive
Data quality issues across HRIS sourcesInconsistent coding, missing fields, stale records, or duplicate entriesEstablish data governance council; define data owners per field; run quarterly data quality audits; build automated validation checks at ingestion
Privacy concerns block analysisInsufficient anonymization, no consent framework, or regulatory gapsApply k-anonymity (minimum group size of 5); conduct privacy impact assessment before each project; engage Legal early; use aggregated data when individual-level is not required
Engagement scores are flat despite interventionsMeasuring wrong drivers, action plans not executed, or survey is too genericRun driver analysis to identify high-impact low-score areas; assign action owners with quarterly check-ins; customize survey questions by department or function
Leadership does not act on insightsInsights are too academic, lack business framing, or arrive too lateLead with business impact (revenue, cost, risk); limit recommendations to 2-3 with clear owners and timelines; deliver insights within 2 weeks of data collection
Show full SKILL.md (544 more words)Show less

Success Criteria

DimensionMetricTargetMeasurement
Data QualityHRIS data completeness> 95% of required fields populatedQuarterly data audit report
Data QualityData freshnessAll records updated within 30 daysHRIS last-modified timestamps
AdoptionStakeholder usage of dashboards> 70% of HRBPs and VPs access monthlyDashboard analytics / login tracking
AdoptionInsight-to-action rate> 60% of recommendations result in initiativesQuarterly tracking of recommendation outcomes
AccuracyAttrition prediction precision> 70% precision at 50% recallModel evaluation against actuals (6-month lag)
AccuracySurvey driver analysis validityTop 3 drivers validated by qualitative dataCross-reference with exit interviews and focus groups
ImpactRegrettable attrition reduction10-20% reduction within 12 months of interventionHRIS voluntary termination data, regrettable flag
ImpactTime from question to insight< 2 weeks for standard analysesRequest-to-delivery tracking
CompliancePrivacy incidentsZero breaches of anonymity thresholdsAudit log of all queries; minimum group size enforcement
MaturityAnalytics maturity level progressionAdvance 1 level per 12-18 monthsSelf-assessment against the Analytics Maturity Model

Scope & Limitations

In Scope:

  • Workforce descriptive analytics: headcount, turnover, retention, demographics, tenure distribution
  • Engagement survey design, analysis, driver identification, and benchmarking
  • Attrition risk scoring using rule-based and statistical methods (standard library only)
  • Pay equity analysis: raw gap, controlled gap, outlier flagging
  • DEI metrics: representation, progression rates, hiring funnel equity
  • Workforce planning: headcount forecasting, scenario modeling, gap analysis
  • Dashboard design and KPI framework recommendations

Out of Scope:

  • Real-time predictive models requiring ML frameworks (scikit-learn, TensorFlow) -- scripts use rule-based scoring for portability
  • Sentiment analysis of free-text survey responses (requires NLP libraries)
  • Individual employee profiling or surveillance -- all analysis uses aggregated or anonymized data
  • HRIS system administration, data pipeline engineering, or ETL development
  • Legal interpretation of pay equity findings (requires Employment Law counsel)
  • Organizational network analysis requiring email/calendar metadata

Known Limitations:

  • Attrition risk scoring in scripts uses weighted heuristics, not trained ML models; accuracy depends on feature quality and weight calibration
  • Pay equity analysis in the SKILL.md examples requires statsmodels (external dependency); scripts use standard-library approximations
  • Survey analysis assumes Likert scale (1-5) responses; other formats require preprocessing
  • Small population segments (< 30) produce unreliable statistical results; flag these in reporting
  • Historical data biases (e.g., biased performance ratings) propagate into predictive models if not addressed

Integration Points

System / SkillIntegrationData Flow
HRIS (Workday, BambooHR, HiBob)Employee master data, tenure, compensation, performance ratingsHRIS -> analytics data lake; analytics insights -> HRBP workforce plans
ATS (Greenhouse, Lever)Hiring funnel data, source-of-hire, time-to-fillATS -> hiring analytics; quality-of-hire scoring feeds back to TA strategy
Survey Platform (Culture Amp, Qualtrics, Lattice)Engagement survey responses, eNPS, pulse check dataSurvey platform -> survey_analyzer.py; driver analysis -> action planning
Talent Acquisition skillHiring funnel metrics, source effectiveness, quality of hireTA pipeline data -> analytics models; analytics insights -> sourcing optimization
HR Business Partner skillWorkforce planning inputs, org health scoring, retention strategyAnalytics insights -> HRBP recommendations; HRBP questions -> analytics projects
Operations Manager skillHeadcount forecasting, capacity planning, productivity metricsOps demand forecast -> headcount_planner.py; workforce metrics -> ops capacity models
Finance skillCompensation budgets, cost modeling, headcount budget vs actualFinance comp data -> pay equity analysis; headcount plan -> Finance budget model
Payroll (ADP, Gusto)Compensation actuals, bonus payouts, overtime dataPayroll -> comp analysis; pay equity findings -> comp adjustment recommendations
BI Platform (Tableau, Looker, Power BI)Dashboard hosting, self-service analytics, scheduled reportingAnalytics outputs -> BI dashboards; BI usage metrics -> adoption tracking

© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts) in hr-operations/people-analytics of borghei/Claude-Skills.

  • SKILL.md
  • scripts/attrition_predictor.py
  • scripts/headcount_planner.py
  • scripts/survey_analyzer.py

Open the folder on GitHubat commit 4a698e8

Compare with similar skills

People Analytics 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.

People Analytics compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
People Analytics this skillborghei/Claude-Skills881—~4.7kAutomated safety check: PassMIT
Technical Analysttradermonty/claude-trading-skills3k5 repos~4.6kAutomated safety check: PassMIT
Creating Financial ModelsChen-zexi/open-ptc-agent7294 repos~1.3kAutomated safety check: PassMIT
Stock APIzhangxiangliang/stock-api2k—~507Automated safety check: PassMIT
Theme Detectortradermonty/claude-trading-skills3k2 repos~4.9kAutomated safety check: PassMIT
Itr Walakaranb192/itr-wala871—~3.6kAutomated safety check: PassMIT

Similar skills

  • Technical Analyst

    tradermonty/claude-trading-skills

    This skill should be used when analyzing weekly price charts for stocks, stock indices, cryptocurrencies, or forex pairs.

    3k GitHub starsUsed in 5 repos~4.6k tokens
    Business, Finance & HRAuto-check passed
  • Creating Financial Models

    Chen-zexi/open-ptc-agent

    This skill provides an advanced financial modeling suite with DCF analysis, sensitivity testing, Monte Carlo simulations, and scenario planning for investment decisions

    729 GitHub starsUsed in 4 repos~1.3k tokens
    Business, Finance & HRAuto-check passed
  • Stock API

    zhangxiangliang/stock-api

    Fetch real-time stock quotes, K-line (candlestick) history, and search symbols for China A-shares, Hong Kong, and US markets.

    2k GitHub stars~507 tokensUpdated today
    Business, Finance & HRAuto-check passed
  • Theme Detector

    tradermonty/claude-trading-skills

    Detect and analyze trending market themes across sectors. An agent skill from tradermonty/claude-trading-skills.

    3k GitHub starsUsed in 2 repos~4.9k tokens
    Business, Finance & HRAuto-check passed
  • Itr Wala

    karanb192/itr-wala

    File Indian income tax returns (ITR) for FY 2025-26 / AY 2026-27.

    871 GitHub stars~3.6k tokensUpdated 3 days ago
    Business, Finance & HRAuto-check passed
  • Tushare Data

    zillionare/zillionare

    面向中文自然语言的 Tushare 数据研究技能。用于把“看看这只股票最近怎么样”“帮我查财报趋势”“最近哪个板块最强”“北向资金在买什么”“给我导出一份行情数据”这类请求,转成可执行的数据获取、清洗、对比、筛选、导出与简要分析流程。适用于 A 股、指数、ETF/基金、财务、估值、资金流、公告新闻、板块概念与宏观数据等研究场景。

    319 GitHub starsUsed in 2 repos~2.3k tokens
    Business, Finance & HRAuto-check passed

More from borghei/Claude-Skills

All 349 skills in this repo
  • Agents In The Team

    borghei/Claude-Skills

    Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.

    881 GitHub stars~4.2k tokensUpdated today
    Auto-check passed
  • AI Content Disclosure

    borghei/Claude-Skills

    Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.

    881 GitHub stars~3.4k tokensUpdated today
    Auto-check passed
  • AI Prototyping

    borghei/Claude-Skills

    Idea to AI-generated prototype to customer validation to engineering handoff.

    881 GitHub stars~3.6k tokensUpdated today
    Auto-check passed
  • Analytics Engineer

    borghei/Claude-Skills

    Analytics engineering across data modeling, dbt, transformation, and semantic layers.

    881 GitHub stars~3.4k tokensUpdated today
    Auto-check passed
  • Ansoff Matrix

    borghei/Claude-Skills

    Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.

    881 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Brainstorm Okrs

    borghei/Claude-Skills

    OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.

    881 GitHub stars~1.4k tokensUpdated today
    Auto-check passed

Questions about People Analytics

What does People Analytics do?

People analytics across workforce metrics, predictive modeling, and employee insights. People Analytics is an agent skill from borghei/Claude-Skills. People analytics across workforce metrics, predictive modeling, and employee insights.

When should I use People Analytics?

People Analytics fits situations like: building turnover models; analyzing engagement surveys; running pay equity regressions; scoring flight risk.

How do I install People Analytics in Claude Code?

Run `npx skills add borghei/Claude-Skills --skill people-analytics -a claude-code`. Or copy the skill folder (hr-operations/people-analytics in borghei/Claude-Skills) into .claude/skills/people-analytics in your project. Claude Code loads it when a task matches its description.

How do I install People Analytics in Codex?

Run `npx skills add borghei/Claude-Skills --skill people-analytics -a codex`. Or copy the skill folder (hr-operations/people-analytics in borghei/Claude-Skills) into .agents/skills/people-analytics in your project. Codex loads it when a task matches its description.

Can I use People Analytics in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill people-analytics -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/people-analytics, .gemini/skills/people-analytics, .github/skills/people-analytics and .opencode/skills/people-analytics in your project.

What does People Analytics need to run?

Going by SKILL.md and its folder, People Analytics needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.

Does People Analytics access the network?

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.

Is People Analytics safe to install?

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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does People Analytics use?

People Analytics is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does People Analytics use?

About 4.7k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to People Analytics?

Skills that share tags, products or a category with People Analytics: Technical Analyst (tradermonty/claude-trading-skills, 3k stars), Creating Financial Models (Chen-zexi/open-ptc-agent, 729 stars), Stock API (zhangxiangliang/stock-api, 2k stars) and Theme Detector (tradermonty/claude-trading-skills, 3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains People Analytics?

borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 881 GitHub stars. The repository holds 349 skills in this directory. The repository was last updated on October 7, 2026.

Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.