agentsclimarketplace

Sf recruiting offer approval audit

Skill SahirVhora/sf-agent-skills/skills/sf-recruiting-offer-approval-audit

AI skills for SAP SuccessFactors consultants: configuration health, migration readiness, and HR transformation workflows

Install
npx -y skills add SahirVhora/sf-agent-skills --skill sf-recruiting-offer-approval-audit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when you need to check rcm requisition templates, offer approvals, and handoff logic before hiring stalls.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

4.4 KB, 820 tokens by cl100k_base, as published. Nobody here has run it

Recruiting Requisition and Offer Approval Audit

Audits SAP SuccessFactors Recruiting configuration across requisition templates, offer approvals, route maps, candidate status transitions, field permissions, and Recruiting-to-Onboarding handoff. Flags inconsistent template fields, missing approvers, approval loops, offer fields not mapped to onboarding, candidate status dead-ends, and country-specific compliance gaps.

When to Use

  • Check RCM requisition templates, offer approvals, and handoff logic before hiring stalls.
  • Client needs a practical review in the Recruiting area
  • Preparing a release, audit, workshop, UAT pack, or remediation plan
  • Translating SF configuration risk into business language

Prerequisites

  • Inputs: RCM requisition templates, offer approval rules, route maps, field permissions, onboarding handoff config
  • Expected outputs: Template health report, approval path gaps, candidate handoff risks, hiring process UAT pack
  • Confirm tenant/snapshot date and audience before analysis
  • Do not store credentials, employee-sensitive data, or tenant exports in the repo

Workflow

  1. Template Inventory - gather evidence, assess impact, and produce the client-safe artefact.
  2. Approval Map - gather evidence, assess impact, and produce the client-safe artefact.
  3. Handoff Check - gather evidence, assess impact, and produce the client-safe artefact.
  4. UAT Pack - gather evidence, assess impact, and produce the client-safe artefact.

Analysis Checklist

  • Capture configuration evidence and source date
  • Separate expected variation from defects
  • Link every finding to business impact: payroll, compliance, hiring, reporting, integration, or employee experience
  • Group repeated findings into themes
  • Produce remediation actions with owner, effort, dependency, and validation step
  • Flag internal-only observations separately from client-ready narrative

Edge Cases

  • Internal candidate follows different route map: validate explicitly and decide whether it is expected design or defect
  • Offer approval differs by compensation threshold: validate explicitly and decide whether it is expected design or defect
  • Hiring manager changes during requisition approval: validate explicitly and decide whether it is expected design or defect
  • Candidate accepts offer after requisition is closed: validate explicitly and decide whether it is expected design or defect
  • Country-specific offer letter fields missing: validate explicitly and decide whether it is expected design or defect
  • Recruiting-to-Onboarding handoff fails for rehire: validate explicitly and decide whether it is expected design or defect

Example Prompt

Audit our recruiting requisition templates and offer approval routing and show what could stall hiring or break onboarding handoff.

Example Output Shape

23 requisition templates and 11 offer routes reviewed. HIGH: 8 issues. Top risk: UK senior role offer approval skips Finance when salary exceeds threshold because compensation field differs across templates. Handoff gap: 4 offer fields required by Onboarding are blank for internal candidates.

Common Pitfalls

  1. Treating all mismatches as defects: Some differences are intentional by country, worker type, or process design.
  2. Ignoring effective dates: Many SF issues only appear when future-dated and retroactive changes are included.
  3. Missing downstream systems: Check payroll, onboarding, reporting, integrations, and approvals before recommending a fix.
  4. No owner or success metric: A finding without owner, effort, and validation is not actionable.
  5. Using technical language with business stakeholders: Translate every issue into risk, cost, time, or compliance impact.

Verification Checklist

  • Source evidence and snapshot date captured
  • Edge cases reviewed explicitly
  • Findings scored by severity and business impact
  • Remediation plan includes owner, effort, dependency, and validation step
  • Client-safe summary produced
  • Internal-only notes separated
  • UAT or follow-up validation pack included

Gives 0 of the 12 instructions most audit compliance skills give in 820 tokens

Counted across 936 of the 1,487 authors here whose files we hold, read 2026-08-06

  • group findings by severityin 44 of 936
  • Fetch latest guidelines before each reviewin 43 of 936, across 3 files
  • Check files against all fetched rulesin 42 of 936, across 2 files
  • Output findings in terse file:line formatin 41 of 936, across 3 files
  • Ask user which files to review if none specifiedin 41 of 936, across 3 files
  • Read specified files or prompt user for filesin 39 of 936, across 1 file
  • generate the audit reportin 39 of 936, across 36 files
  • assign a severity to every findingin 25 of 936
  • run automated accessibility scansin 23 of 936, across 13 files
  • map findings to WCAG criteriain 20 of 936, across 10 files
  • confirm audit scopein 19 of 936, across 9 files
  • check title tags and meta descriptions for uniquenessin 19 of 936, across 5 files

Said here and by no other author read

  • capture configuration evidence and source date
  • separate expected variation from defects
  • link every finding to business impact
  • group repeated findings into themes
  • produce remediation actions with owner, effort, dependency, and validation step
  • flag internal-only observations separately

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.