How do I install the Oce Field Ops skill?

Run npx skillmds@latest add gabrielmoreira/oce-field-ops in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Oce Field Ops safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Oce Field Ops?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Oce Field Ops free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Oce Field Ops?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Oce Field Ops by gabrielmoreira — Agent Skill

Name: Oce Field Ops
Rating: 4.5 (4 reviews)
Author: gabrielmoreira

File contents

Field Operations in OpenConstructionERP

Modules for the site

Module	Purpose	Typical flow
`punch_list`	Deficiencies / snag items	create item → assign → verify → close
`daily_diary`	Daily site reports	weather, workforce, progress, incidents
`hse`	Health, safety, environment	observations, incidents, checklists
`tasks`	Site task board	Kanban, issues linked to BIM elements

Punch list workflow

Inspector (or a photo) creates a punch item: location, trade, priority, due date, photo attachment.
Item auto-assigns to the responsible trade (routing rules).
Contractor marks fixed → inspector verifies → item closes.
Closeout report: open vs closed per trade/zone, aging.

Daily diary automation

Prefill from the schedule: planned activities of the day.
Inputs: weather (integrated), workforce counts, deliveries, issues, photos.
Auto-summary to the weekly progress report (see oce-scheduling-4d5d roll-ups).

HSE

Safety observations: classify (PPE, fall protection, housekeeping…), severity, follow-up.
Incident reports with photo evidence and root-cause fields.
Checklists per trade and per regulation (OSHA / local).

API patterns

POST /api/v1/punch-list/          # create punch item
PATCH /api/v1/punch-list/{id}     # status/assignee
POST /api/v1/daily-diary/         # diary entry
GET  /api/v1/tasks/?project=...   # site tasks

(Endpoint names may vary by module version — check backend/app/modules/*/router.py for the authoritative surface.)

Best practices

Link punch items to BIM elements — the 3D view shows open deficiencies in place.
Make the daily diary the single source of actuals (it feeds variance reports).
Photos on every issue: evidence beats memory in disputes.
Close the loop — every observation ends in an action, not a note.

---name: oce-field-opsdescription: Field operations in OpenConstructionERP: punch list, daily diary, HSE observations and task tracking on site. Use when automating construction site workflows (deficiencies, diaries, safety, site tasks).--- # Field Operations in OpenConstructionERP ## Modules for the site | Module | Purpose | Typical flow | |---|---|---| | `punch_list` | Deficiencies / snag items | create item → assign → verify → close | | `daily_diary` | Daily site reports | weather, workforce, progress, incidents | | `hse` | Health, safety, environment | observations, incidents, checklists | | `tasks` | Site task board | Kanban, issues linked to BIM elements | ## Punch list workflow 1. Inspector (or a photo) creates a punch item: location, trade, priority, due date, photo attachment. 2. Item auto-assigns to the responsible trade (routing rules). 3. Contractor marks fixed → inspector verifies → item closes. 4. Closeout report: open vs closed per trade/zone, aging. ## Daily diary automation - Prefill from the schedule: planned activities of the day. - Inputs: weather (integrated), workforce counts, deliveries, issues, photos. - Auto-summary to the weekly progress report (see `oce-scheduling-4d5d` roll-ups). ## HSE - Safety observations: classify (PPE, fall protection, housekeeping…), severity, follow-up. - Incident reports with photo evidence and root-cause fields. - Checklists per trade and per regulation (OSHA / local). ## API patterns ```http POST /api/v1/punch-list/ # create punch item PATCH /api/v1/punch-list/{id} # status/assignee POST /api/v1/daily-diary/ # diary entry GET /api/v1/tasks/?project=... # site tasks ``` (Endpoint names may vary by module version — check `backend/app/modules/*/router.py` for the authoritative surface.) ## Best practices 1. Link punch items to BIM elements — the 3D view shows open deficiencies in place. 2. Make the daily diary the single source of actuals (it feeds variance reports). 3. Photos on every issue: evidence beats memory in disputes. 4. Close the loop — every observation ends in an action, not a note.

Frequently asked questions

Oce Field Ops