SkillVaultskills Browse all 500 skills

People Operations · Version 1.0.0 · Reviewed 2026-08-02

Job Description Clarity and Inclusion Auditor

Make outcome-based role definition and requirement necessity review with evidence, explicit trade-offs, and a verification plan.

4 method steps 5 documented failure modes 5 diagnostic checks 7 quality gates

Reviews a job description for unclear outcomes, inflated requirements, exclusionary phrasing, duplicated qualifications, and interview criteria that cannot be consistently assessed.

₹149 one-time

Get this skill archive

What this skill helps you do

  • Outcome-based role definition
  • Requirement necessity review
  • Inclusive language audit

How Job Description Clarity and Inclusion Auditor works

You provide

Obligations, data inventory, and current controls

It inspects

Requirement type and implemented control for outcome-based role definition

It decides

A requirement necessity review gap register with accountable owners

You verify

Each control mapped to evidence an auditor would accept

What it checks first

Job Description Clarity and Inclusion Auditor reviews a job description for unclear outcomes, inflated requirements, exclusionary phrasing, duplicated qualifications, and interview criteria that cannot be consistently assessed. Use it when the work involves Outcome-based role definition, Requirement necessity review, Inclusive language audit.

  1. Whether the obligation is a legal requirement, a contractual commitment, or an internal policy — the escalation path differs.
  2. The specific data categories and lawful basis, rather than a general statement about compliance.
  3. Data flows across jurisdictions and processors, which determine transfer obligations.
  4. Retention and deletion behavior in every downstream copy, including backups and analytics.
  5. Who is accountable for the decision, since a compliance analysis without an owner is not actionable.

Failure modes it recognizes

  • Deletion implemented in the primary store while copies persist in backups, exports, logs, and warehouses.
  • Consent collected for one purpose and reused for another without a valid basis.
  • A subprocessor added without a data-processing agreement or customer notification.
  • Retention policy defined but never enforced by an automated job.
  • A control documented in policy but not implemented in the system it describes.

Answers it will reject

  • Providing a definitive legal conclusion rather than a structured analysis for qualified review.
  • Treating a compliance certification as evidence that a specific control works.
  • Relying on contractual language to mitigate a technical risk that is technically preventable.
  • Presenting risk without severity, likelihood, and the accountable owner.

Decision rules it applies

  • Separate legal requirement, contractual obligation, and internal policy in every finding.
  • Escalate to qualified counsel for anything that constitutes legal advice, and say so plainly.
  • Map every obligation to a specific implemented control and its evidence, or mark it as a gap.
  • Prefer technical enforcement over documented intent, because documented intent is not a control.

Evidence it asks for

  • Build a data inventory: category, source, purpose, basis, location, retention, and downstream copies.
  • Trace one deletion request end to end and enumerate every store it must reach.
  • Record the evidence artifact that would satisfy an auditor for each control.

The method inside

  1. Define the decision criterion before reading the evidence
  2. Separate observation from interpretation and bias
  3. Check consistency across people, segments, or reviewers
  4. Produce actionable language while preserving confidentiality

Deliverables

  • Outcome-based role definition evidence assessment
  • Requirement necessity review consistency findings
  • Inclusive language audit action-ready revision

Evidence requirements

  • Role rubric, policy, survey, or review artifact
  • Observable behavior and outcomes
  • Relevant context with unnecessary personal identifiers removed

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Audit this senior operations job description before posting and explain which requirements should change.

Expected output

The role lists 22 responsibilities but no first-year outcomes. Five “required” qualifications are preferences, and “digital native” is exclusionary without describing a job-relevant capability...

Boundaries and compatibility

Ideal for

  • Outcome-based role definition: produce a decision or artifact grounded in supplied evidence.
  • Requirement necessity review: produce a decision or artifact grounded in supplied evidence.
  • Inclusive language audit: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Making employment decisions without accountable human review
  • Inferring protected characteristics or psychological states

Agent compatibility

  • GitHub Copilot custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.