ops-manual-acknowledgement
Drafts an enforceable Operations Manual Acknowledgement form recording an employee's or franchisee's receipt, understanding, and agreement to comply with company policies. Produces a litigation-ready record with affirmative statements, at-will disclaimers, policy cross-references, and signature blocks. Use when onboarding employees, onboarding franchisees, creating policy acknowledgement forms, or documenting manual receipt (trigger keywords: operations manual, policy acknowledgement, employee handbook receipt, onboarding form, manual compliance).
Best use case
ops-manual-acknowledgement is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Drafts an enforceable Operations Manual Acknowledgement form recording an employee's or franchisee's receipt, understanding, and agreement to comply with company policies. Produces a litigation-ready record with affirmative statements, at-will disclaimers, policy cross-references, and signature blocks. Use when onboarding employees, onboarding franchisees, creating policy acknowledgement forms, or documenting manual receipt (trigger keywords: operations manual, policy acknowledgement, employee handbook receipt, onboarding form, manual compliance).
Teams using ops-manual-acknowledgement should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ops-manual-acknowledgement/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ops-manual-acknowledgement Compares
| Feature / Agent | ops-manual-acknowledgement | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Drafts an enforceable Operations Manual Acknowledgement form recording an employee's or franchisee's receipt, understanding, and agreement to comply with company policies. Produces a litigation-ready record with affirmative statements, at-will disclaimers, policy cross-references, and signature blocks. Use when onboarding employees, onboarding franchisees, creating policy acknowledgement forms, or documenting manual receipt (trigger keywords: operations manual, policy acknowledgement, employee handbook receipt, onboarding form, manual compliance).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Operations Manual Acknowledgement Drafts an enforceable acknowledgement form recording receipt, understanding, and agreement to comply with an operations manual — built to withstand scrutiny in termination proceedings, unemployment claims, or litigation. ## Prerequisites 1. **Company legal name** and any d/b/a 2. **Manual version** — title, effective date, revision number 3. **Relationship type** — employee (at-will or contract) or franchisee 4. **Jurisdiction** — state/territory for employment law compliance 5. **Key policies requiring express reference** — e.g., anti-discrimination, harassment, safety, confidentiality 6. **Witness/countersignature requirements** — whether HR or supervisor must co-sign 7. **Multilingual requirements** — whether translation is needed under applicable law ## Output Structure ### 1. Document Header | Field | Content | |---|---| | Title | **OPERATIONS MANUAL ACKNOWLEDGEMENT** | | Company | Full legal entity name | | Manual reference | Title, version/edition, effective date | | Document date | Date of execution | | Reference no. | Internal tracking number (if used) | ### 2. Preamble One paragraph establishing: - Employee/franchisee acknowledges receipt of the identified manual - Specific version/edition and effective date - Whether this version supersedes prior versions - Relationship to employment/franchise agreement (supplements vs. incorporates) ### 3. Affirmative Acknowledgement Statements Draft as numbered first-person affirmations: 1. I have received a complete copy of the Operations Manual (version _____, effective _____) 2. I have read and understand its contents 3. I agree to comply with all policies and procedures contained therein 4. I understand violations may result in disciplinary action up to and including termination 5. I will seek clarification from [designated contact] on any policy I do not fully understand 6. I will stay informed of updates and amendments to the Manual 7. I will return all company property, including the Manual, upon separation ### 4. Key Policy Cross-References If provided, include express acknowledgement of heightened-significance policies as an initialed checklist: - Anti-discrimination and equal opportunity - Harassment prevention - Workplace safety / OSHA compliance - Confidentiality and trade secrets - Data privacy - Drug and alcohol - Social media / acceptable use ### 5. Disclaimers Include all three; each is legally critical: ```text AT-WILL DISCLAIMER (employment context): This Acknowledgement and the Operations Manual do not constitute a contract of employment. Unless a separate written agreement provides otherwise, employment is at-will and may be terminated by either party at any time, with or without cause or notice. MODIFICATION RESERVATION: The Company reserves the right to modify, amend, supplement, or rescind any policy in the Operations Manual at any time, with or without notice. NO CONTRACTUAL RIGHTS: Nothing in the Operations Manual or this Acknowledgement creates contractual rights or entitlements beyond those required by applicable law. ``` For **franchisee** context, replace the at-will disclaimer with language preserving the franchise agreement as the governing instrument; do not inadvertently create an employment relationship. ### 6. Employee/Franchisee Information Block | Field | Entry | |---|---| | Full legal name (print) | _________________________ | | Title / Position | _________________________ | | Department / Division | _________________________ | | Employee/Franchisee ID | _________________________ | | Start date | _________________________ | ### 7. Signature Block ```text By signing below, I acknowledge that I have received, read, and understood the Operations Manual and agree to comply with all policies contained therein. ______________________________ ______________ Employee/Franchisee Signature Date ______________________________ Printed Name WITNESS / COMPANY REPRESENTATIVE (if required): ______________________________ ______________ Signature Date ______________________________ ______________ Printed Name Title ``` ## Guidelines - **Plain language** — accessible to all education levels while remaining legally precise; ambiguous terms are construed against the drafter (contra proferentem) - **Version control** — always tie acknowledgement to a specific manual version; never use open-ended references - **Multilingual compliance** — some jurisdictions (e.g., California for certain industries) require translated versions; flag when applicable `[VERIFY]` - **Electronic signatures** — if e-signature is used, confirm compliance with ESIGN Act / UETA and state equivalents `[VERIFY]` - **Retention** — signed originals must be maintained in personnel files per applicable record-retention schedules - **Franchisee variant** — cross-reference the franchise agreement and FDD; do not create language that could be construed as an employment relationship `[VERIFY]` - Keep to 1–2 pages for immediate use in HR/onboarding systems - **All outputs require attorney review** in the applicable jurisdiction
Related Skills
policy-manual
Generates structured policy manual summaries that distill complex legal policies and compliance guidelines into employee-facing reference documents organized by functional area. Use when creating compliance manuals, employee policy guides, regulatory summaries, onboarding compliance materials, or organizational procedure handbooks.
import-compliance-manual
Drafts a U.S. import compliance manual demonstrating reasonable care under 19 U.S.C. § 1484. Covers HTS classification, customs valuation (19 U.S.C. § 1401a), country of origin, recordkeeping (19 C.F.R. Part 163), PGA compliance, internal audit, training, and corrective action. Use when creating or overhauling an importer-of-record compliance program, preparing for a CBP focused assessment, or establishing written reasonable-care procedures. Trigger keywords: import compliance manual, customs compliance program, CBP audit preparation, reasonable care, IOR compliance.
ecp-manual
Drafts an audit-ready Export Compliance Program manual covering EAR, ITAR, and OFAC requirements. Use when creating or updating an export compliance policy, international trade compliance program, or preparing enforcement defense documentation for regulatory review.
skill-name
Replace with a specific description of what this skill does and when to use it. Include keywords that help agents identify relevant tasks.
writing-surgical-consultation-notes
Creates structured surgical consultation responses with assessment and surgical candidacy determination. Use when responding to surgical consults, evaluating surgical candidates, or documenting surgical recommendations.
writing-operative-reports
Creates structured operative notes with findings, technique, specimens, and estimated blood loss. Use when dictating operative reports, documenting surgical procedures, or recording intraoperative findings.
writing-irb-submissions
Creates IRB submission packages with protocol summaries, consent forms, and risk-benefit analysis. Use when submitting to IRB, preparing ethics applications, or writing consent documents.
writing-grant-applications-research
Structures NIH/foundation grant applications with specific aims, significance, and innovation sections. Use when writing research grants, preparing NIH applications, or structuring grant proposals.
writing-admission-orders
Generates structured admission order sets with diagnosis-specific protocols and safety checks. Use when admitting patients, creating admission orders, or setting up inpatient care plans.
validating-new-laboratory-tests
Structures test validation with precision, accuracy, linearity, and reference range establishment. Use when validating new assays, documenting method comparisons, or establishing reference ranges.
validating-clinical-data-quality
Structures data quality assessment with completeness, accuracy, and consistency validation. Use when auditing clinical data, assessing data quality, or validating data integrity.
triaging-emergency-presentations
Applies ESI triage methodology to assign acuity levels based on presenting complaints, vital signs, and resource needs. Use when triaging ED patients, assigning acuity scores, or prioritizing emergency cases.