factories-act-returns

Assemble state-specific Indian Factories Act statutory returns with mandatory state detection.

1|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/ashley-eyekyam/hse-leadership-skills --skill factories-act-returns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: factories-act-returns
Source: https://github.com/ashley-eyekyam/hse-leadership-skills/tree/main/skills/factories-act-returns
Command: npx skills add https://github.com/ashley-eyekyam/hse-leadership-skills --skill factories-act-returns

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Generic AI generates non-compliant, regulator-rejected safety paperwork: vague tasks, incorrect state-specific Factories Act forms, fabricated form values, and leaked personal/health data. This Skill eliminates those failures by enforcing mandatory state detection, strict no-fabrication rules, and mandatory de-identification before drafting any return.

Core Features & Use Cases

  • Mandatory State Detection: Blocks assembly until the correct Indian state is confirmed, ensuring the right state-specific statutory form (TN Form 22, KA Form 20, DL Form 21, etc.) is used, with unverified forms marked [GAP] instead of fabricated.
  • Compliance-First Assembly: Assembles annual/half-yearly Factories Act returns and statutory registers, appends OSH-Code transition notes, and cites exact rules, due dates, and filing portals from the official knowledge base.
  • Use Case: A safety manager in Maharashtra needs to file their annual Factories Act return. This Skill walks them through structured intake, de-identifies all worker/occupier PII, aggregates small accident cells, and produces a compliant, regulator-ready return with all unverified fields clearly marked [GAP].

Quick Start

Use the factories-act-returns skill to assemble the annual Factories Act return for your Tamil Nadu factory, providing the state, establishment details, worker figures, and accident tally when prompted.

Frequently Asked Questions about factories-act-returns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I file state-specific Factories Act returns without selecting the wrong statutory form?

To file state-specific Factories Act returns safely, the workflow enforces mandatory state detection before assembly, ensuring the correct statutory form is selected. Unverified form values are marked as gaps rather than fabricated, preventing regulator rejection.

What is the process for de-identifying personal data in HSE returns?

De-identifying personal data in HSE returns involves removing or masking worker and occupier PII before drafting any statutory forms. This compliance-first approach ensures personal health data is protected during the assembly of Factories Act annual returns.

Can I use this Factories Act compliance workflow for multiple Indian states?

Yes, you can use this workflow for multiple Indian states as it supports state-specific statutory forms and rules. It requires confirming the exact Indian state to route the assembly logic to the correct regional filing portal and due dates.

How to assemble annual Factories Act returns with OSH-Code transition notes?

To assemble annual Factories Act returns with OSH-Code transition notes, the system aggregates worker figures, tallies accidents, and appends the necessary transition notes. It cites exact state-specific rules and filing portals from its official knowledge base.

Why does generic AI generate non-compliant India Factories Act statutory forms?

Generic AI generates non-compliant India Factories Act statutory forms because it lacks strict state detection, fabricates unverified values, and leaks personal data. This workflow eliminates those failures by enforcing no-fabrication rules and mandatory de-identification.