What problem does it solve?
Generic AI-generated dropped-objects prevention paperwork is often rejected by regulators: it is vague, defaults to PPE-only controls like "wear hard hats below" with no reliable securing or exclusion zones, includes unvetted consequence bands, and may leak personal or health data. This Skill eliminates those failures by forcing task specificity, applying the hierarchy of controls, de-identifying sensitive data, and requiring domain-expert review before any output is produced.
Core Features & Use Cases
- Reliable-securing-led DROPS artifacts: Produces DROPS surveys, dropped-object registers with static/dynamic object taxonomy, reliable-securing controls (primary fixing + secondary retention), and exclusion zones per DROPS Recommended Practice 2017, IADC HSE Guidelines Section 16, and API RP 2D/54. PPE is treated only as a residual control, never the headline.
- Structured intake for absolute specificity: Refuses vague requests like "the platform" or "looks secured" by forcing users to provide a named installation/area, survey scope, at-height items, and existing securing status before any drafting begins.
- Compliant, defensible output: Uses the public m·g·h impact energy method with user-supplied mass and fall height for consequence banding (never reproduces licensed DROPS Calculator thresholds), includes mandatory de-identification of all personal and health data, and requires SME sign-off prior to delivery.
- Use Case: For an offshore drilling operator, use this Skill to run a DROPS survey for a drilling derrick, build a register of static and dynamic dropped objects, set reliable-securing standards for at-height fittings, and define exclusion zones for tripping operations.
Quick Start
Use the dropped-objects-prevention skill to run a DROPS survey for the Platform Bravo drilling derrick, build a dropped-object register for the monkeyboard fingerboard latch pin and racking-board light fittings, set reliable-securing controls, and define exclusion zones for at-height work.