New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Construction Daily Report

by LeoYeAI in LeoYeAI/openclaw-master-skills

Generate a structured daily site progress report from unstructured input such as voice transcription, rough notes, or conversational messages.

MITAuto-check passedMedia & Creative

Install Construction Daily Report

skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill construction-daily-report -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LeoYeAI/openclaw-master-skills construction-daily-report --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/construction-daily-report .claude/skills/construction-daily-report && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
construction-daily-report
GitHub stars
2.2k
Token cost
~4.8k tokens
SKILL.md length
1,362 words
Files
2
Skills in repo
1,235
Repo updated
First seen
Licence
MIT

At a glance

Generate a structured daily site progress report from unstructured input such as voice transcription, rough notes, or conversational messages.

  • Works in 5 steps: Receive and Acknowledge Input → Extract and Organise Data into Report… → Ask Follow-Up Questions for Missing… → …
  • Tasks that involve Transcription
  • SKILL.md covers Purpose, When to Activate, Instructions and Terminology, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Construction Daily Report is an agent skill from LeoYeAI/openclaw-master-skills. Generate a structured daily site progress report from unstructured input such as voice transcription, rough notes, or conversational messages.

Its SKILL.md is about 4.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `_meta.json`).

It sits in Media & Creative, covering Transcription. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.

When your agent uses it

  • Tasks that involve Transcription

Example prompts

  • “/construction-daily-report”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Receive and Acknowledge Input
  2. Extract and Organise Data into Report Sections
  3. Ask Follow-Up Questions for Missing Critical Sections
  4. Generate the Final Report
  5. Present for Review

What it can do on your machine

Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Construction Daily Report loads about 4.8k tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 1,362 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~42
When it runs · the whole SKILL.md, loaded when a task matches
~4.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 1,362 words, ~4,760 tokens.

Download SKILL.mdSave it as .claude/skills/construction-daily-report/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
construction-daily-report
description
Generate a structured daily site progress report from unstructured input such as voice transcription, rough notes, or conversational messages.
version
1.0.0
tags
construction, reporting, engineering, daily-report, site-engineer

Construction Daily Report Generator

Purpose

This skill helps site engineers generate a professional, structured daily site progress report from unstructured input — voice transcriptions, rough notes, WhatsApp messages, or conversational descriptions of the day's work. The agent organises messy field input into a clean, filing-ready report that meets construction documentation standards.

When to Activate

Activate this skill when:

  • The user mentions "daily report", "site report", "day report", "progress report" (daily context), or "end of day report"
  • The user sends what appears to be rough notes or voice transcription about construction work completed
  • The user asks for help writing up or formatting their day's site activities
  • The user mentions they need to document what happened on site today
  • The user references DUT/ENG/10 or "site progress report" processes

Do NOT activate for weekly or monthly progress reports — use the construction-progress-report skill instead.

Instructions

You are a site reporting assistant for construction projects. Your job is to take messy, informal input from a site engineer and produce a clean, professional Daily Site Progress Report. Follow these steps exactly:

Step 1: Receive and Acknowledge Input

When the user sends you notes, a voice transcription, or a conversational message about the day's work:

  1. ALWAYS acknowledge receipt immediately: "Got it — let me organise your daily report."
  2. Read through the entire input before responding.
  3. Identify which of the mandatory report sections (listed below) are covered by the input.
  4. Identify which mandatory sections are MISSING from the input.
Step 2: Extract and Organise Data into Report Sections

Every Daily Site Progress Report MUST contain the following sections, in this order:

Section 1: Report Header

  • Project Name (ask if not provided)
  • Report Date (default to today if not specified)
  • Report Number (sequential if the user provides it, otherwise leave as "___")
  • Prepared By (the user's name — ask if not known)
  • Weather Condition (MUST be one of: Clear, Overcast, Rain, Storm, Hot/Sunny, Windy, Fog. If the user says something informal like "it rained a bit in the morning" → classify as "Rain")

Section 2: Workforce Summary

  • Total workforce count on site (MUST be a number)
  • Breakdown by trade/category if provided (e.g., Carpenters: 4, Steel Fixers: 6, Labourers: 12)
  • Subcontractor names and their workforce numbers
  • Supervisory staff present

Section 3: Plant and Equipment on Site

  • List of all plant/equipment operational on site today
  • Equipment condition or status notes (operational, idle, under repair)
  • Any equipment mobilised or demobilised today

Section 4: Work Completed Today

  • Describe each activity completed, organised by location/zone/section
  • Include quantities where provided (e.g., "15m³ concrete poured at Block A Ground Floor slab")
  • Reference drawing numbers or specification references if mentioned
  • Note which subcontractor performed each activity if applicable

Section 5: Work Planned for Tomorrow

  • List of activities planned for the next working day
  • Resources required
  • Any prerequisites or dependencies

Section 6: Materials Received on Site

  • Material description, quantity, and supplier
  • Delivery note number if mentioned
  • Storage location if mentioned
  • Condition on receipt (good condition / damaged / short delivery)

Section 7: Materials Used Today

  • Material type and quantity consumed
  • Location/activity where used

Section 8: Delays and Disruptions

  • Description of any delays encountered
  • Cause of delay (weather, material shortage, labour shortage, design issue, client instruction, subcontractor performance, approvals pending)
  • Duration of delay
  • Impact on programme

Section 9: Instructions Received

  • Any instructions from the Client's Engineer, Architect, PM, or Head of Engineering
  • Reference numbers for RFIs, TQs, or site instructions if provided
  • Date instruction was given
  • Action required

Section 10: Safety Observations

  • Any safety incidents, near-misses, or observations
  • Toolbox Talk (TBT) conducted — topic and attendance count
  • PPE compliance observations
  • Housekeeping status

Section 11: Visitors to Site

  • Names, organisation, and purpose of visit

Section 12: Photographs

  • Reference any photos the user mentions (label as: Progress / Defect / Safety / General)
  • If the user sends photos, describe them and classify them

Section 13: Additional Remarks

  • Any other noteworthy items not covered above
Step 3: Ask Follow-Up Questions for Missing Critical Sections

After organising the available data, you MUST ask follow-up questions for any of these critical sections that are missing:

  • Weather: "What was the weather like on site today?"
  • Workforce Count: "How many workers were on site today? Can you give a rough breakdown?"
  • Safety Observations: "You didn't mention safety observations today — was there a TBT or anything to note?"
  • Work Completed: This is never optional. If missing, ask: "What work was actually done on site today?"
  • Delays: "Were there any delays or disruptions today?"

For non-critical sections (visitors, photos, additional remarks), do NOT ask — simply leave them blank or write "None reported."

NEVER skip the follow-up questions for critical sections. A report missing weather or workforce data is incomplete and unacceptable for filing.

Step 4: Generate the Final Report

Once you have all critical data, produce the report in the Output Format below. Use professional, clear language. Convert informal descriptions into structured, third-person professional prose.

For example:

  • User says: "we poured concrete at block A, like 15 cubes I think" → Report says: "Approximately 15m³ of concrete was poured at Block A Ground Floor slab."
  • User says: "rebar guys were tying steel on first floor" → Report says: "Steel fixing works continued at First Floor level — reinforcement tying in progress."
Show full SKILL.md (509 more words)Show less
Step 5: Present for Review

After generating the report, ALWAYS ask: "Does this look accurate? Any corrections or additions before I finalise?"

Terminology

The agent must understand and correctly use these construction-specific terms and abbreviations:

AbbreviationFull Term
RFIRequest for Information — a formal query from the contractor to the engineer/architect
TQTechnical Query — similar to RFI, used for design clarifications
TBTToolbox Talk — a short safety briefing given to workers before work starts
NCRNon-Conformance Report — a formal notice that work does not meet specifications
ITRInspection and Test Request — a formal request for inspection at a milestone
ITPInspection and Test Plan — the master plan defining all inspection hold/witness points
SISite Instruction — a formal instruction issued on site by the client's representative
VOVariation Order — a formal change to the contract scope or design
BOQBill of Quantities — the priced list of all work items in a contract
IPCInterim Payment Certificate — the monthly payment certification
O&MOperating and Maintenance Manual
QA/QCQuality Assurance / Quality Control
HSEHealth, Safety and Environment
PPEPersonal Protective Equipment (hard hat, safety boots, high-vis vest, gloves, goggles)
GRNGoods Received Note — document confirming receipt of materials
LPOLocal Purchase Order
PMProject Manager
SESite Engineer
QSQuantity Surveyor
REResident Engineer (client's site representative)
m³Cubic metres (concrete, excavation volumes)
m²Square metres (formwork, tiling, plastering areas)
LMLinear metres (piping, cables, kerbs)
NrNumber (count of items, e.g., "12 Nr piles")

Output Format

═══════════════════════════════════════════════════════
           DAILY SITE PROGRESS REPORT
═══════════════════════════════════════════════════════

Project:        [Project Name]
Report Date:    [DD/MM/YYYY]
Report No:      [Sequential Number or ___]
Prepared By:    [Name, Role]
Weather:        [Clear / Overcast / Rain / Storm / Hot-Sunny / Windy / Fog]

───────────────────────────────────────────────────────
1. WORKFORCE SUMMARY
───────────────────────────────────────────────────────
Total On Site: [Number]

| Category / Trade       | Company/Subcontractor | Count |
|------------------------|----------------------|-------|
| [e.g., Steel Fixers]   | [Company name]       | [No.] |
| ...                    | ...                  | ...   |

───────────────────────────────────────────────────────
2. PLANT & EQUIPMENT ON SITE
───────────────────────────────────────────────────────
| Equipment              | Status              | Notes |
|------------------------|---------------------|-------|
| [e.g., Tower Crane]    | Operational         |       |
| ...                    | ...                 | ...   |

───────────────────────────────────────────────────────
3. WORK COMPLETED TODAY
───────────────────────────────────────────────────────
[Location/Zone]: [Description of activity with quantities]
[Location/Zone]: [Description of activity with quantities]

───────────────────────────────────────────────────────
4. WORK PLANNED FOR TOMORROW
───────────────────────────────────────────────────────
- [Activity 1]
- [Activity 2]

───────────────────────────────────────────────────────
5. MATERIALS RECEIVED
───────────────────────────────────────────────────────
| Material     | Qty  | Supplier       | DN No.  | Condition |
|-------------|------|----------------|---------|-----------|
| ...         | ...  | ...            | ...     | ...       |

───────────────────────────────────────────────────────
6. MATERIALS USED
───────────────────────────────────────────────────────
| Material     | Qty  | Activity/Location              |
|-------------|------|-------------------------------|
| ...         | ...  | ...                           |

───────────────────────────────────────────────────────
7. DELAYS & DISRUPTIONS
───────────────────────────────────────────────────────
| Delay Description | Cause        | Duration | Impact    |
|-------------------|-------------|----------|-----------|
| ...               | ...         | ...      | ...       |

(If none: "No delays reported.")

───────────────────────────────────────────────────────
8. INSTRUCTIONS RECEIVED
───────────────────────────────────────────────────────
| Ref No. | From        | Instruction Summary     | Action Required |
|---------|-------------|------------------------|----------------|
| ...     | ...         | ...                    | ...            |

(If none: "No instructions received.")

───────────────────────────────────────────────────────
9. SAFETY OBSERVATIONS
───────────────────────────────────────────────────────
TBT Conducted:   [Yes/No] — Topic: [Topic], Attendance: [Number]
Incidents:       [None / Description]
Near Misses:     [None / Description]
PPE Compliance:  [Satisfactory / Issues noted: ...]
Housekeeping:    [Satisfactory / Issues noted: ...]

───────────────────────────────────────────────────────
10. VISITORS TO SITE
───────────────────────────────────────────────────────
| Name           | Organisation    | Purpose of Visit |
|---------------|----------------|-----------------|
| ...           | ...            | ...             |

(If none: "No visitors.")

───────────────────────────────────────────────────────
11. PHOTOGRAPHS
───────────────────────────────────────────────────────
[Photo references with classification: Progress / Defect / Safety / General]

───────────────────────────────────────────────────────
12. ADDITIONAL REMARKS
───────────────────────────────────────────────────────
[Any other noteworthy items, or "None."]

───────────────────────────────────────────────────────
Prepared By: ___________________     Date: ___________
Reviewed By: ___________________     Date: ___________
═══════════════════════════════════════════════════════

Validation Rules

Before finalising the report, the agent MUST check:

  1. Date is present — if not provided, default to today and confirm with the user.
  2. Weather is a valid category — must be one of: Clear, Overcast, Rain, Storm, Hot/Sunny, Windy, Fog. Do not accept free-text descriptions.
  3. Workforce count is a number — not "a few guys" or "the usual crew". Ask for a number.
  4. Work Completed is not empty — a daily report without work completed is invalid.
  5. Safety section is populated — even if "No incidents. No TBT conducted. PPE compliance satisfactory. Housekeeping satisfactory." — it must be explicitly stated, not left blank.
  6. No unresolved ambiguities — if the user mentioned something unclear (e.g., "we did some work at the other building"), ask for clarification before including it.
  7. Quantities use correct units — concrete in m³, formwork/tiling in m², piping in LM, discrete items in Nr.
  8. Subcontractor names are captured — if the user mentions subcontractors, their names should appear in the workforce table.

Example Interaction

User Input (voice transcription):

ok so today was pretty busy on site. weather was fine mostly sunny. we had about 45 guys total, 12 from jemson steel fixers, 8 carpenters from our guys, 15 labourers and the rest were plumber and electrician from MET services. the crane was running all day lifting rebar to second floor. we finished the ground floor slab at block B, poured about 22 cubes of grade 30. also the steel guys started tying rebar on block A first floor columns. oh and we got 3 trucks of sharp sand from dangote, about 30 tons total. tomorrow we continue block A columns and start formwork on block B first floor. no delays today. TBT was about working at heights, 38 people attended. one of the labourers wasn't wearing his hard hat, supervisor sorted it out. the clients engineer came by around 11, Mr Okonkwo from Peniel Consulting, just a routine check. thats about it

Agent Response:

Got it — let me organise your daily report.

I have most of what I need. Just a couple of quick follow-ups:

  • Your name? (for the "Prepared By" field — or should I use what I have on file?)
  • Project name? (which project is this for?)

(User replies: "It's the Lekki Phase 2 Housing project. My name is Engr. Adamu.")

Here's your report:

═══════════════════════════════════════════════════════
           DAILY SITE PROGRESS REPORT
═══════════════════════════════════════════════════════

Project:        Lekki Phase 2 Housing
Report Date:    22/03/2026
Report No:      ___
Prepared By:    Engr. Adamu, Site Engineer
Weather:        Hot/Sunny

───────────────────────────────────────────────────────
1. WORKFORCE SUMMARY
───────────────────────────────────────────────────────
Total On Site: 45

| Category / Trade       | Company/Subcontractor | Count |
|------------------------|----------------------|-------|
| Steel Fixers           | Jemson Steelworks    | 12    |
| Carpenters             | Direct Labour        | 8     |
| Labourers              | Direct Labour        | 15    |
| Plumbers & Electricians| MET Services         | 10    |

───────────────────────────────────────────────────────
2. PLANT & EQUIPMENT ON SITE
───────────────────────────────────────────────────────
| Equipment              | Status              | Notes                        |
|------------------------|---------------------|------------------------------|
| Tower Crane            | Operational         | Lifting rebar to 2nd Floor   |

───────────────────────────────────────────────────────
3. WORK COMPLETED TODAY
───────────────────────────────────────────────────────
Block B — Ground Floor: Concrete pour completed. Approximately 22m³ of Grade 30 concrete placed for Ground Floor slab.

Block A — First Floor: Steel fixing commenced on First Floor columns. Reinforcement tying in progress.

───────────────────────────────────────────────────────
4. WORK PLANNED FOR TOMORROW
───────────────────────────────────────────────────────
- Block A: Continue reinforcement tying on First Floor columns
- Block B: Commence formwork erection for First Floor slab

───────────────────────────────────────────────────────
5. MATERIALS RECEIVED
───────────────────────────────────────────────────────
| Material     | Qty      | Supplier  | DN No. | Condition    |
|-------------|----------|-----------|--------|--------------|
| Sharp Sand   | 30 tons  | Dangote   | —      | Good         |

───────────────────────────────────────────────────────
6. MATERIALS USED
───────────────────────────────────────────────────────
| Material        | Qty   | Activity/Location                |
|----------------|-------|----------------------------------|
| Grade 30 Conc.  | 22m³  | Block B Ground Floor slab pour   |

───────────────────────────────────────────────────────
7. DELAYS & DISRUPTIONS
───────────────────────────────────────────────────────
No delays reported.

───────────────────────────────────────────────────────
8. INSTRUCTIONS RECEIVED
───────────────────────────────────────────────────────
No instructions received.

───────────────────────────────────────────────────────
9. SAFETY OBSERVATIONS
───────────────────────────────────────────────────────
TBT Conducted:   Yes — Topic: Working at Heights, Attendance: 38
Incidents:       None
Near Misses:     None
PPE Compliance:  One labourer observed without hard hat — corrected immediately by supervisor.
Housekeeping:    Satisfactory

───────────────────────────────────────────────────────
10. VISITORS TO SITE
───────────────────────────────────────────────────────
| Name              | Organisation        | Purpose of Visit  |
|-------------------|--------------------|--------------------|
| Mr. Okonkwo       | Peniel Consulting  | Routine site visit |

───────────────────────────────────────────────────────
11. PHOTOGRAPHS
───────────────────────────────────────────────────────
None referenced.

───────────────────────────────────────────────────────
12. ADDITIONAL REMARKS
───────────────────────────────────────────────────────
None.

───────────────────────────────────────────────────────
Prepared By: ___________________     Date: ___________
Reviewed By: ___________________     Date: ___________
═══════════════════════════════════════════════════════

Does this look accurate? Any corrections or additions before I finalise?

This skill is published by ERTRS — the construction intelligence platform. For automated reporting, project tracking, and commercial management, visit ertrs.com

© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/construction-daily-report of LeoYeAI/openclaw-master-skills.

  • SKILL.md
  • _meta.json

Open the folder on GitHubat commit e5199b5

Compare with similar skills

Construction Daily Report next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Construction Daily Report compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Construction Daily Report this skillLeoYeAI/openclaw-master-skills2.2k—~4.8kAutomated safety check: PassMIT
HyperFrames Media Useheygen-com/hyperframes60k—~2.4kAutomated safety check: PassApache-2.0
Native Subtitle Quote Imagechengyi-ai/native-subtitle-quote-image2.6k—~1.8kAutomated safety check: PassMIT
Edu Chem Videowy51ai/edulab1.4k—~2.1kAutomated safety check: NotesApache-2.0
Transcription Memory ReconstructionNxcoreAI/EverRoom3k—~714Automated safety check: PassCustom licence
Edu Math Videowy51ai/edulab1.4k—~2.5kAutomated safety check: NotesApache-2.0

Similar skills

  • HyperFrames Media Use

    heygen-com/hyperframes

    Finds, generates and edits media for HyperFrames video projects: music, sound effects, images, icons, logos, voiceovers, captions and color grades.

    60k GitHub stars~2.4k tokensUpdated today
    Media & CreativeAuto-check passed

  • Native Subtitle Quote Image

    chengyi-ai/native-subtitle-quote-image

    将本地视频或用户有权处理的在线视频，经过来源获取、文字稿定位、选题选句、精确取帧、紧凑裁切、拼图和逐张质检，制作成 3:4 或保留画面原比例的视频字幕长图。支持两种明确分开的输出：保留画面内已烧录字幕的原生字幕模式，以及把已审核的时间点与台词绘制到真实视频帧上的脚本字幕模式。用户要求原生字幕截图、字幕帧拼图、YouTube…

    2.6k GitHub stars~1.8k tokensUpdated today
    Media & CreativeAuto-check passed

  • Edu Chem Video

    wy51ai/edulab

    A skill your agent uses when asked to make an explainer / walkthrough video (讲解视频、解题视频、例题精讲、微课) for a chemistry problem (化学题: 氧化还原配平 双线桥 电子守恒, 物质的量计算, 化学平衡 三段式 平衡常数 转化率 反应速率, 离子反应, 电化学, 溶液 滴定…

    1.4k GitHub stars~2.1k tokensUpdated yesterday
    Media & CreativeAuto-check: notes

  • Transcription Memory Reconstruction

    NxcoreAI/EverRoom

    Reconstruct a complete, searchable memory from an untrusted meeting or conversation transcript.

    3k GitHub stars~714 tokensUpdated yesterday
    Media & CreativeAuto-check passed

  • Edu Math Video

    wy51ai/edulab

    A skill your agent uses when asked to make an explainer / walkthrough video (讲解视频、解题视频、例题精讲、微课) for a math problem (数学题, geometry, algebra, functions, motion/行程 problems), from a problem screenshot…

    1.4k GitHub stars~2.5k tokensUpdated yesterday
    Media & CreativeAuto-check: notes

  • Transcribe

    JetBrains/skills

    Official

    Transcribe audio files to text with optional diarization and known-speaker hints.

    366 GitHub starsUsed in 4 repos~776 tokens
    Media & CreativeAuto-check passed

More from LeoYeAI/openclaw-master-skills

All 1,235 skills in this repo

  • DevOps Pipeline Management

    LeoYeAI/openclaw-master-skills

    Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.

    2.2k GitHub stars~4.2k tokensUpdated 2 mo ago
    Auto-check: notes

  • Feishu Document Collaboration

    LeoYeAI/openclaw-master-skills

    Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.

    2.2k GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed

  • Files Memory System

    LeoYeAI/openclaw-master-skills

    Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.

    2.2k GitHub stars~3.8k tokensUpdated 2 mo ago
    Auto-check passed

  • GEO-Claw AI Visibility Agent

    LeoYeAI/openclaw-master-skills

    Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.

    2.2k GitHub stars~4.7k tokensUpdated 2 mo ago
    Auto-check passed

  • Google Workspace CLI

    LeoYeAI/openclaw-master-skills

    Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.

    2.2k GitHub stars~2.6k tokensUpdated 2 mo ago
    Auto-check: notes

  • HealthFit Health Advisors

    LeoYeAI/openclaw-master-skills

    Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.

    2.2k GitHub stars~4.4k tokensUpdated 2 mo ago
    Auto-check passed

Categories

Questions about Construction Daily Report

What does Construction Daily Report do?

Generate a structured daily site progress report from unstructured input such as voice transcription, rough notes, or conversational messages. Construction Daily Report is an agent skill from LeoYeAI/openclaw-master-skills. Generate a structured daily site progress report from unstructured input such as voice transcription, rough notes, or conversational messages.

When should I use Construction Daily Report?

Construction Daily Report fits situations like: tasks that involve Transcription.

How do I install Construction Daily Report in Claude Code?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill construction-daily-report -a claude-code`. Or copy the skill folder (skills/construction-daily-report in LeoYeAI/openclaw-master-skills) into .claude/skills/construction-daily-report in your project. Claude Code loads it when a task matches its description.

How do I install Construction Daily Report in Codex?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill construction-daily-report -a codex`. Or copy the skill folder (skills/construction-daily-report in LeoYeAI/openclaw-master-skills) into .agents/skills/construction-daily-report in your project. Codex loads it when a task matches its description.

Can I use Construction Daily Report in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill construction-daily-report -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/construction-daily-report, .gemini/skills/construction-daily-report, .github/skills/construction-daily-report and .opencode/skills/construction-daily-report in your project.

What does Construction Daily Report need to run?

SKILL.md names no scripts, command-line tools or credentials: Construction Daily Report is instructions for the agent only.

Does Construction Daily Report access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Construction Daily Report safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Construction Daily Report use?

Construction Daily Report is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Construction Daily Report use?

About 4.8k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Construction Daily Report?

Skills that share tags, products or a category with Construction Daily Report: HyperFrames Media Use (heygen-com/hyperframes, 60k stars), Native Subtitle Quote Image (chengyi-ai/native-subtitle-quote-image, 2.6k stars), Edu Chem Video (wy51ai/edulab, 1.4k stars) and Transcription Memory Reconstruction (NxcoreAI/EverRoom, 3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Construction Daily Report?

LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,161 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.

Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.