Agent skill

Estimate Layoff Risk

by kelvinfkr in kelvinfkr/company_skill

Estimate an employee, intern, contractor, or role group's 3/6/12-month involuntary job-loss risk from public company evidence and an adaptive candidate interview.

MITAuto-check passedSales & Support

Install Estimate Layoff Risk

skills CLI
$ npx skills add kelvinfkr/company_skill --skill estimate-layoff-risk -a claude-code

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

GitHub CLI
$ gh skill install kelvinfkr/company_skill estimate-layoff-risk --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/kelvinfkr/company_skill.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/estimate-layoff-risk .claude/skills/estimate-layoff-risk && 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
estimate-layoff-risk
GitHub stars
241
Token cost
~2.8k tokens
SKILL.md length
1,188 words
Files
40 (incl. scripts, references, assets)
Skills in repo
2
Repo updated
First seen
Licence
MIT

At a glance

Estimate an employee, intern, contractor, or role group's 3/6/12-month involuntary job-loss risk from public company evidence and an adaptive candidate interview.

  • Works in 9 steps: Define scope and competing outcomes → Run the adaptive interview → Route the company and economic model → …
  • Questions about layoff probability
  • SKILL.md covers Non-negotiable boundaries, Default deliverables, Workflow and Reporting rules, plus 1 more section
  • Calls python

What it does

Estimate Layoff Risk is an agent skill from kelvinfkr/company_skill. Estimate an employee, intern, contractor, or role group's 3/6/12-month involuntary job-loss risk from public company evidence and an adaptive candidate interview. Use for questions about layoff probability, role redundancy, business-unit closure, contract non-renewal, performance exits, reorganization exposure, or which jobs are safer during cost cuts. Reconstruct business economics and profit pools first, trace them through critical processes and roles, model leadership's observable allocation regime, and…

Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 44 other files, including scripts, reference files and assets (for example `README.md`, `agents/openai.yaml` and `assets/fonts/README.md`).

It sits in Sales & Support. The licence is MIT.

When your agent uses it

  • Questions about layoff probability
  • Role redundancy
  • Business-unit closure
  • Contract non-renewal

Example prompts

  • “/estimate-layoff-risk”

Requirements

  • Python 3

Workflow steps

9 steps, taken from the step headings in SKILL.md.

  1. Define scope and competing outcomes
  2. Run the adaptive interview
  3. Route the company and economic model
  4. Search in eight evidence passes
  5. Reconstruct profit pools and cost pressure
  6. Build the dependency graph
  7. Model leadership as an allocation regime
  8. Estimate risk and uncertainty
  9. Produce and validate the report

What it can do on your machine

Read from SKILL.md and the folder at commit c99f8b2. 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 1 file in scripts/, 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

Estimate Layoff Risk loads about 2.8k tokens when it runs, and up to ~9.1k if it reads all its reference files. Until then it costs about 153 tokens; SKILL.md has 1,188 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~153
When it runs · the whole SKILL.md, loaded when a task matches
~2.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~9.1k

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 kelvinfkr/company_skill at commit c99f8b2, republished under its MIT licence (© kelvinfkr). 1,188 words, ~2,840 tokens.

Download SKILL.mdSave it as .claude/skills/estimate-layoff-risk/SKILL.md (or your agent's skills folder). This skill also uses 39 other files; get the full folder from GitHub.
name
estimate-layoff-risk
description
Estimate an employee, intern, contractor, or role group's 3/6/12-month involuntary job-loss risk from public company evidence and an adaptive candidate interview. Use for questions about layoff probability, role redundancy, business-unit closure, contract non-renewal, performance exits, reorganization exposure, or which jobs are safer during cost cuts. Reconstruct business economics and profit pools first, trace them through critical processes and roles, model leadership's observable allocation regime, and produce an auditable probability range rather than a false-precision verdict.

Estimate Layoff Risk

Treat job-loss risk as a causal resource-allocation problem, not sentiment analysis.

Use this chain:

business model -> profit pools -> cash/margin pressure -> allocation decision -> business unit -> critical process -> role family -> employment mechanism -> individual exposure

Non-negotiable boundaries

  1. Define the outcome before estimating it. Separate mass layoff, unit closure, role redundancy, performance termination, site closure, contract non-renewal, internship ending, and redeployment.
  2. Use only public, legally accessible external information plus facts the candidate voluntarily provides. Never request confidential documents, credentials, private coworker data, or access-controlled material.
  3. Do not ask for or use protected or highly sensitive traits such as race, ethnicity, sex, pregnancy, disability, health, religion, political affiliation, union membership, family status, or age except a legally necessary age-of-majority check. Do not use proxies for them.
  4. Do not infer a private person's performance, compensation, health, relationships, or legal status. Treat self-reported performance evidence as optional and uncertain.
  5. Distinguish observed_fact, candidate_report, derived_metric, model_assumption, and inference in the evidence ledger.
  6. Give probability intervals and confidence. If calibration evidence is insufficient, report an ordinal risk band with a scenario range, not a pseudo-statistical percentage.
  7. Analyze leadership through observable allocation behavior and governance incentives, never personality diagnosis or cultural stereotype.
  8. This is decision support, not a guarantee or legal opinion. Search current jurisdiction-specific law when legal consequences matter.

Default deliverables

Create a case directory containing:

  • case.json - scope, entity, role, employment type, location, horizons;
  • candidate_answers.json - voluntary answers with date, provenance, and confidence;
  • public_evidence.jsonl - claim-level evidence;
  • source_manifest.csv - every source searched or used;
  • profit_pools.json - segment/product/channel economics and strategic-option assessment;
  • dependency_graph.json - profit pool to process to team to role mapping;
  • model.json - risk-layer assumptions and sensitivity;
  • report.json - structured report source;
  • report.pdf - default user-facing report.

Initialize with:

python scripts/init_case.py --company "Company" --role "Role" --country "Country" --employment-type employee --out runs/company-role-YYYY-MM-DD

Workflow

Phase 0 - Define scope and competing outcomes

Identify the legal employer, parent/subsidiary, business unit, product, geography, worksite, role family, employment type, reference date, and 3/6/12-month horizons.

Treat these as competing risks:

  • enterprise-wide workforce action;
  • BU/product/site closure or material contraction;
  • process redesign, outsourcing, automation, or location transfer;
  • role-family reduction;
  • person selection within a reduced role family;
  • performance process;
  • contract, internship, probation, or vendor non-renewal;
  • redeployment instead of separation.

Do not equate non-renewal with a statutory layoff. Report them separately and optionally combine them as any_involuntary_exit.

Phase 1 - Run the adaptive interview

Read references/interview_protocol.md and references/role_playbooks.md.

Ask the 12 core questions in two short rounds, then only the relevant employment-type and role-family branches. Ask 12-25 questions total in normal cases. Ask follow-ups only when they can materially change the risk interval.

Generate a question set when useful:

python scripts/questionnaire.py case.json -o questionnaire.json

For every answer record the answer, observation date, provenance, candidate confidence, and whether the candidate consents to include it in the report.

Prefer objective signals over anxiety labels. Ask what changed in budget, roadmap, workload, hiring, reporting lines, customer commitments, and future tasks.

Phase 2 - Route the company and economic model

Read references/profit_pool_model.md.

Classify the company before searching: public/private, startup, founder-controlled, diversified, PE-owned/highly leveraged, manufacturing/hardware, software/platform, project/services, regulated finance/utility, biotech/long-cycle R&D, or public/nonprofit/state-owned.

Select the correct economic denominator. Prefer contribution profit, gross profit, cash generation, backlog, utilization, plant load, funding runway, or regulatory mandate over raw revenue when appropriate.

Phase 3 - Search in eight evidence passes

Read references/research_and_evidence.md and references/jurisdiction_playbooks.md.

Generate the initial plan:

python scripts/search_plan.py case.json -o search_plan.json

Run distinct passes for:

  1. entity, legal employer, parent, subsidiaries, BU, product, and worksite;
  2. solvency, cash runway, debt, covenants, financing, and working capital;
  3. company/segment revenue, gross profit, contribution, operating profit, and guidance;
  4. margin targets, restructuring charges, synergy commitments, and capital allocation;
  5. BU/product lifecycle, customers, orders, roadmap, launches, cancellations, and strategic priority;
  6. workforce, payroll, job postings, hiring freezes, location moves, outsourcing, and automation;
  7. governance and leadership allocation history;
  8. contrary evidence and comparable-company base rates.

Prefer primary sources. Deduplicate syndicated stories by underlying claim and origin. Record unavailable but decision-relevant sources.

Phase 4 - Reconstruct profit pools and cost pressure

Build a profit-pool table by material product x geography x channel x customer type x lifecycle combinations.

For each pool estimate ranges for revenue, gross/contribution profit, cash conversion, growth, orders/retention, inventory, customer concentration, incremental investment, avoidable cost, shared-platform dependency, strategic option, regulatory value, and management commitment.

Classify the action regime as survival, margin_reset, capital_reallocation, integration, demand_capacity, performance_system, or mixed.

Do not assume a currently loss-making business is disposable. Estimate future contribution, option value, synergy, required follow-on investment, and probability management still funds the next milestone.

Show full SKILL.md (444 more words)Show less
Phase 5 - Build the dependency graph

Map:

profit pool -> critical process -> product/project/customer/site -> team -> role family -> employment bucket

For each node assess value at risk, time until damage, redundancy, automation/outsourcing/transfer feasibility, minimum viable staffing, recovery time, knowledge loss, regulatory/safety/security obligations, and whether headcount cost is actually avoidable.

Estimate the role's layoff net benefit conceptually:

PV(avoidable loaded cost) - PV(lost contribution + execution risk + rehiring + knowledge + option value)

Use ranges. Never fabricate individual contribution numbers.

Phase 6 - Model leadership as an allocation regime

Read references/leadership_regimes.md.

Infer weights from repeated decisions, governance, compensation metrics, budget allocation, executive turnover, and responses to prior misses. Assess centralization, strategic stability, cash/margin discipline, tolerance for long-cycle options, performance mechanism, redeployment propensity, and communication predictability.

Use leadership only to update how and when cuts propagate. Operational evidence, formal targets, and product decisions dominate leadership-language evidence.

Phase 7 - Estimate risk and uncertainty

Read references/modeling_and_calibration.md.

For each horizon estimate:

P(company action) x P(unit affected | action) x P(role reduced | unit affected) x P(person selected | role reduced)

Then combine structural risk with contract/non-renewal and performance-exit hazards without double counting. Run:

python scripts/estimate_risk.py model.json -o risk_results.json

Report component probabilities, any_involuntary_exit, redeployment likelihood, evidence coverage, confidence, and the variables that drive interval width.

Numeric output requires a defined outcome/horizon, an appropriate economic model, company-pressure evidence, BU/product and role-dependency assessments, enough candidate answers to locate the role, an explicit prior/base rate, and contradictory evidence. Otherwise provide a provisional map and the next evidence needed.

Phase 8 - Produce and validate the report

Read references/report_contract.md and references/privacy_and_boundaries.md.

Populate report.json, then render:

python scripts/render_report.py report.json -o report.pdf

Render the PDF to images and inspect every page for clipping, broken CJK glyphs, poor pagination, and unreadable tables. Validate the complete bundle:

python scripts/validate_bundle.py runs/case-directory

Reporting rules

  • Lead with the 3/6/12-month outcome table and one-sentence diagnosis.
  • Show public evidence and candidate-reported evidence separately.
  • Explain why the company may cut while profitable, or retain a role inside a loss-making business.
  • Include favorable, base, and adverse scenarios.
  • State what observable developments would move the estimate up or down.
  • Include a candidate-controlled redaction note. Do not expose names or unnecessary personal detail in filenames or report metadata.
  • Never advise deception, sabotage, data extraction, or concealment from an employer.

Packaged resources

  • references/interview_protocol.md - adaptive question sequence and answer provenance.
  • references/role_playbooks.md - branch questions and economics by role family and employment type.
  • references/profit_pool_model.md - Profit-to-Headcount model and company-type routing.
  • references/leadership_regimes.md - observable leadership allocation regimes.
  • references/research_and_evidence.md - search passes, evidence grading, and contradiction checks.
  • references/jurisdiction_playbooks.md - local notice sources and search terms.
  • references/modeling_and_calibration.md - competing-risk estimation and leakage prevention.
  • references/privacy_and_boundaries.md - sensitive-data and candidate-control rules.
  • references/report_contract.md - structured report specification.
  • assets/question_bank.json and assets/report_spec.json - reusable templates.
  • schemas/*.schema.json - case, evidence, model, and report schemas.
  • scripts/*.py - initialization, routing, planning, estimation, rendering, and validation.

© kelvinfkr, 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 39 other files (scripts, references, assets) in skills/estimate-layoff-risk of kelvinfkr/company_skill.

  • SKILL.md
  • README.md
  • agents/openai.yaml
  • assets/fonts/README.md
  • assets/icon.svg
  • assets/question_bank.json
  • assets/report_spec.json
  • examples/fictional_robotics_intern/candidate_answers.json
  • examples/fictional_robotics_intern/case.json
  • examples/fictional_robotics_intern/dependency_graph.json
  • examples/fictional_robotics_intern/model.json
  • examples/fictional_robotics_intern/profit_pools.json
  • examples/fictional_robotics_intern/public_evidence.jsonl
  • examples/fictional_robotics_intern/questionnaire.json
  • examples/fictional_robotics_intern/report.json
  • examples/fictional_robotics_intern/risk_results.json
  • … and 24 more

Open the folder on GitHubat commit c99f8b2

Compare with similar skills

Estimate Layoff Risk 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.

Estimate Layoff Risk compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Estimate Layoff Risk this skillkelvinfkr/company_skill241—~2.8kAutomated safety check: PassMIT
Cold Outbound Optimizerericosiu/ai-marketing-skills3.6k1 repos~1.7kAutomated safety check: PassMIT
Doc Coauthoringaws-samples/sample-strands-agent-with-agentcore19540 repos~3.2kAutomated safety check: PassMIT
Amazon Buy Box Monitorbrowser-act/skills6.1k1 repos~1.6kAutomated safety check: PassMIT
Review Analysisliangdabiao/amazon-sorftime-research-MCP-skill9591 repos~2.5kAutomated safety check: PassNone
Deskcomm Extensaomelgarafael/DeskcommCRM4.5k—~2.7kAutomated safety check: PassMIT

Similar skills

  • Cold Outbound Optimizer

    ericosiu/ai-marketing-skills

    Design, analyze, and optimize cold outbound email campaigns for Instantly.

    3.6k GitHub starsUsed in 1 repo~1.7k tokens
    Sales & SupportAuto-check passed
  • Doc Coauthoring

    aws-samples/sample-strands-agent-with-agentcore

    Official

    Guide users through a structured workflow for co-authoring documentation.

    195 GitHub starsUsed in 40 repos~3.2k tokens
    Sales & SupportAuto-check passed
  • Amazon Buy Box Monitor

    browser-act/skills

    Pulls Amazon product details, competing seller prices and seller ratings for a given ASIN through the BrowserAct API, without browser automation.

    6.1k GitHub starsUsed in 1 repo~1.6k tokens
    Sales & SupportAuto-check passed
  • Review Analysis

    liangdabiao/amazon-sorftime-research-MCP-skill

    对亚马逊商品评论进行深度分析,自动识别产品痛点、分析退货原因,生成改进建议和客服回复模板。Invoke when user uses /review-analysis command with a product ASIN.

    959 GitHub starsUsed in 1 repo~2.5k tokens
    Sales & SupportAuto-check passed
  • Deskcomm Extensao

    melgarafael/DeskcommCRM

    Guia para criar uma extensão do DeskcommCRM — o pacote declarativo — em vez de abrir um PR no núcleo.

    4.5k GitHub stars~2.7k tokensUpdated today
    Sales & SupportAuto-check passed
  • Tourmind Booking

    tourmind-com/Tourmind-Booking-Skills

    MUST USE for any hotel or accommodation intent in any language, including hotel search, hotel recommendations, nearby accommodation, hostels, guesthouses, resorts, where-to-stay questions, room…

    1.8k GitHub stars~13k tokensUpdated yesterday
    Sales & SupportAuto-check passed

More from kelvinfkr/company_skill

  • Company Talent Economics

    kelvinfkr/company_skill

    Reconstruct a company's compensation distribution, high-compensation population, promotion/hiring paths, and role-specific pay bands from public filings and other public data, and deliver a typeset…

    241 GitHub stars~8.4k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Estimate Layoff Risk

What does Estimate Layoff Risk do?

Estimate an employee, intern, contractor, or role group's 3/6/12-month involuntary job-loss risk from public company evidence and an adaptive candidate interview. Estimate Layoff Risk is an agent skill from kelvinfkr/company_skill. Estimate an employee, intern, contractor, or role group's 3/6/12-month involuntary job-loss risk from public company evidence and an adaptive candidate interview.

When should I use Estimate Layoff Risk?

Estimate Layoff Risk fits situations like: questions about layoff probability; role redundancy; business-unit closure; contract non-renewal.

How do I install Estimate Layoff Risk in Claude Code?

Run `npx skills add kelvinfkr/company_skill --skill estimate-layoff-risk -a claude-code`. Or copy the skill folder (skills/estimate-layoff-risk in kelvinfkr/company_skill) into .claude/skills/estimate-layoff-risk in your project. Claude Code loads it when a task matches its description.

How do I install Estimate Layoff Risk in Codex?

Run `npx skills add kelvinfkr/company_skill --skill estimate-layoff-risk -a codex`. Or copy the skill folder (skills/estimate-layoff-risk in kelvinfkr/company_skill) into .agents/skills/estimate-layoff-risk in your project. Codex loads it when a task matches its description.

Can I use Estimate Layoff Risk 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 kelvinfkr/company_skill --skill estimate-layoff-risk -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/estimate-layoff-risk, .gemini/skills/estimate-layoff-risk, .github/skills/estimate-layoff-risk and .opencode/skills/estimate-layoff-risk in your project.

What does Estimate Layoff Risk need to run?

Going by SKILL.md and its folder, Estimate Layoff Risk needs the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Estimate Layoff Risk 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 Estimate Layoff Risk 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 Estimate Layoff Risk use?

Estimate Layoff Risk is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Estimate Layoff Risk use?

About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.3k tokens, read only when the agent opens those files.

What are the alternatives to Estimate Layoff Risk?

Skills that share tags, products or a category with Estimate Layoff Risk: Cold Outbound Optimizer (ericosiu/ai-marketing-skills, 3.6k stars), Doc Coauthoring (aws-samples/sample-strands-agent-with-agentcore, 195 stars), Amazon Buy Box Monitor (browser-act/skills, 6.1k stars) and Review Analysis (liangdabiao/amazon-sorftime-research-MCP-skill, 959 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Estimate Layoff Risk?

kelvinfkr (a GitHub user) maintains it in kelvinfkr/company_skill, which has 241 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on August 25, 2026.

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