About this skill

Problem Addressed

HR policies, hiring requirements, job responsibilities, and evaluation criteria are often scattered across separate documents. After a policy update, job descriptions may remain outdated; authority, reporting lines, and qualification wording can drift across roles. This skill is intended for consistency review of such documents, helping surface clause conflicts, missing responsibilities, and inconsistent wording before formal issuance or hiring.

How It Works

The skill runs as a protected workflow. It first performs a Python environment check, confirming that python3, py -3, or a user-specified path is available, so failures are not caused by a missing interpreter or Windows app execution alias issues. It then uses scripts/auth.py for authorization. If it returns AUTH_REQUIRED or local credentials are missing, it automatically continues the binding flow instead of immediately reporting an error. Only after authorization succeeds and scripts/protected.py returns protected instructions does it follow those instructions for the actual review logic. Public documentation does not promise fixed rules; the effective checks depend on the protected instructions.

Boundaries and Notes

It is suitable for reviewing existing textual materials where consistency is needed, not for inferring complete policies or job descriptions when source documents are missing. Business output is prohibited if authorization is not passed; secrets must not be exposed in plaintext; first-time binding issues should be distinguished from genuine authorization failures. It depends on a usable Python environment, network reachability, and platform authorization, so restricted or offline environments should confirm execution conditions first.

Screenshots

Use Cases

After an HR policy update, check whether new clauses remain consistent with job responsibilities, authority, and qualifications.
Across multiple job descriptions, locate wording differences in duties, reporting lines, or approval authority.
Before formal issuance, review whether job descriptions conflict with or omit payroll, attendance, or hiring policies.
During role-definition review, collect mismatches between policy requirements and job description requirements for follow-up.

Best For

HR policy owners who need to check whether job descriptions were updated after policy changes.
Hiring managers who need to confirm role requirements align with company policies.
Operations or admin leads who need to identify conflicts between policy and job documents before issuance.
OD leads who need to review responsibility boundaries during role-definition work.