Site visits — 1 of 20 skills in the Architect & BTP pack
In a chat, Word or Excel files aren't always generated: you get the document as structured text instead.
CR-Chantier
Turns your site-meeting notes into a professional record.
Free, no account, no email — the command is all you need.
Already have it?
Nothing to install if it's already active
If this skill is already added in your Claude, there's no need to install it again. Just ask for what you want to do.
Not sure? Ask Claude: "which skills do you have available?"
“Use the site-meeting-minutes skill to write up the record for this meeting, based on my notes: …”
1 · The simplest way
Copy and paste into any AI chat
This button copies the whole skill. Paste it into Claude, ChatGPT, or Gemini, then describe what you need. No installation required.
In a chat, Word or Excel files can't always be generated: you'll receive the document as structured text instead, and Claude will flag it.
- This skill produces mandatory legal notices: review them before any professional use.
2 · Command line
/cr-chantier installs in 3 steps
For Claude Code. The skill installs on your computer and stays available across all your projects.
Prerequisites: Claude Code + Node.js
The skill runs inside Claude Code, Anthropic's AI assistant installed on your computer. Node.js is the engine that runs the install command. Both are free.
Open PowerShell
Click Start, type "PowerShell", then press Enter.
Paste the command
Right-click inside the PowerShell window (or press Ctrl + V) to paste the command below, then press Enter. Wait a few seconds.
npx educasium --skill cr-chantier --globalWhat you should see:
npx educasium --skill cr-chantier --global
Fetching https://raw.githubusercontent.com/Chappygo-OS/claude-meta-skills/main/dist/cr-chantier.zip
…
Installed "cr-chantier". Restart Claude Code to pick it up.
Restart Claude Code
In Claude Code, type /restart (or quit and relaunch Claude Code). The skill now appears in the command list.
Verify it's installed (30 seconds)
Write in Claude Code:
/cr-chantier Today's meeting, Martin project, structural work at 60%. Write the minutes.
If Claude runs the skill without an error message and produces the requested result, everything works. If not, the most likely causes are listed below.
Not working?
The most common causes
“npx” is not recognized
Your computer probably doesn't have Node.js. Download the LTS version from nodejs.org, run the installer, close and reopen PowerShell, then paste the command again.
The skill does not appear
Restart Claude Code (type /restart in the conversation, or quit and relaunch it). Check the command spelling: /cr-chantier. If needed, re-run the installation with --global at the end.
Describe the exact error message as it appears — the team will answer and guide you.
Contact the teamDon't use a terminal?
Using Claude.ai in your browser?
The assisted install works through a .zip file imported into Claude.ai. It takes longer and asks for your email.
What the skill does
View the source codeIn detail.
Hand it your site-meeting notes, even rough or dictated. Claude structures the record into 8 sections — attendance, per-lot progress, decisions, reserves, forward planning — and outputs a .docx that follows French professional practice. Stands as the record of record unless contested within 8 days.
When to use it
Every week, right after your site meeting, before the details fade.
Example usage
/cr-chantier Today's meeting, Martin project, structural work at 60%...In depth
How this skill really works
CR de Chantier produces the weekly construction-site meeting minutes — the document a project architect (maître d'œuvre) writes after every site meeting to formally record project progress. It turns raw notes, a dictated recap, or a loose list of points into a document structured across 8 sections, ready to distribute to the site's stakeholders (client, present and absent contractors, inspection body, safety coordinator where applicable).
This is not an informal recap: under French construction law, the site-meeting record stands as evidence of what was said and decided unless it is contested in writing within 8 days of receipt. Its structure — who attended, what was decided, what reserves (defects/issues) were noted, with which responsible party and deadline — carries evidentiary weight, not just organizational value.
The skill is built for the architect or project lead who has just left a site meeting and wants this document produced without rebuilding its structure every time, while strictly respecting what was actually said rather than filling gaps with invented information.
When to use it
- Right after each weekly site meeting, from raw notes or a dictated recap.
- When the project name, address, client, or permit number were already given earlier in the conversation and don't need to be asked again.
- When several lots (structural work, painting, etc.) need to be tracked separately with a progress percentage and an assessment against the schedule.
- When one or more reserves (defects, issues noted) need to be logged with their severity, a corrective action, a responsible party, and a deadline.
- When a decision made in the meeting needs to be recorded with an identified owner and due date.
- When today's reserves need to feed into the centralized tracker of open reserves afterward.
When not to use it
- Not for a one-off site visit outside a scheduled meeting — that's the role of /rapport-visite-chantier.
- Not for the formal handover of finished work — /pv-reception documents that act.
- Not for maintaining the standing tracker of open reserves — reserves logged in the CR feed /suivi-reserves, but that tool remains the central tracker.
The method
The CR-8 structure
The format documented in references/structure-cr.md splits the record into 8 fixed blocks. Each block corresponds to a legally or operationally necessary piece of information — it isn't a free-form outline, it's the skeleton any restructuring of raw notes must follow.
- 1. Identification
- Header block: project, site address, client, project architect, document reference, weather of the day, date of the next meeting.
- 2. Attendance
- Table of name / role / company, with present, absent, and excused marked distinctly.
- 3. Per-lot progress
- One subheading per lot (e.g. Lot 1 — Structural work: Dupont company), with a progress percentage, observations, and an assessment of ahead / on track / delayed against the schedule.
- 4. Decisions
- Numbered list: subject, discussion summary, decision reached, action owner, deadline.
- 5. Reserves
- Affected lot, description, severity (Minor / Major / Critical), corrective action, responsible party, deadline.
- 6. Forward planning
- Lot, planned task, planned date, observations — the next steps expected before the following meeting.
- 7. Photo references
- Number and description of each photo, affected lot — the photos themselves are not embedded in the docx, only referenced to the separately archived photo file.
- 8. Distribution
- List of recipients (client, present and absent contractors, inspection body, safety coordinator where applicable), followed by the 8-day legal mention.
Steps
Collect the information
Read the full list of fields to collect before generating anything. Ask questions conversationally, grouped by theme rather than all at once, and reuse project information already given earlier in the conversation without asking again.
Structure the record
Restructure the raw notes, dictated recap, or loose list into the 8 sections of the CR-8 structure. If information is missing and the user hasn't provided it, leave an explicit placeholder rather than inventing a value, and flag it after generation.
Generate the file
Default output is .docx (switch to .pdf only on explicit request). Name the file CR-[YYYY-MM-DD]-[ProjectName].docx, and close the document with the 8-day legal mention.
Report
Summarize which lots were covered, how many decisions and reserves were logged, and flag any field still left as a placeholder that still needs input from the user.
Rules
- Never invent a missing data point (attendance, progress percentage, date) — leave an explicit placeholder and flag it after generation.
- Always close the document with the legal mention: "This record stands as evidence unless contested in writing within 8 days of receipt."
- Name the file following the CR-[YYYY-MM-DD]-[ProjectName].docx format.
- Default output is .docx; only switch to .pdf on the user's explicit request.
- Mark absent and excused attendees distinctly in the attendance table — the two statuses are not interchangeable.
- Grade every logged reserve as Minor, Major, or Critical.
Mistakes to avoid
- Inventing an attendance record, a progress percentage, or a missing date instead of leaving an explicit placeholder.
- Using this skill for a visit outside a scheduled meeting — that's a mix-up with /rapport-visite-chantier.
- Embedding the photographs themselves in the docx instead of a simple numbered reference to the separately archived photo file.
- Omitting the 8-day contestation legal mention at the end of the document.
- Generating a record while skipping one of the 8 sections (e.g. distribution or reserves) instead of leaving a placeholder when information is missing.
What this skill doesn't do
- Does not embed the photographs in the document — only references (number, description) are listed; the photo file stays archived separately.
- Does not replace the one-off site visit report outside a scheduled meeting (/rapport-visite-chantier).
- Is not the centralized tracker of open reserves — it hands off today's reserves, to be forwarded to /suivi-reserves.
- Does not document the formal handover of finished work (/pv-reception).
- Does not verify the legal validity of the content nor replace legal counsel — it applies a standard format; responsibility for the content stays with its author.
- Does not recompute progress percentages from measurements — it takes the figure supplied by the user as given.
Skill contents — 2 fichiers · 7.5 KB(SKILL.md, references/structure-cr.md)
Download for free