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 Diary Creation

by GAIK-project in GAIK-project/gaik-toolkit

Extracts structured data from Finnish construction site daily diary audio recordings (Työmaapäiväkirja) and creates a formatted Word document with extracted fields.

MITAuto-check passedKnowledge Management

Install Construction Diary Creation

skills CLI
$ npx skills add GAIK-project/gaik-toolkit --skill construction-diary-creation -a claude-code

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

GitHub CLI
$ gh skill install GAIK-project/gaik-toolkit construction-diary-creation --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/GAIK-project/gaik-toolkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/implementation_layer/no-code-assets/agent-skills/construction-diary-creation/construction-diary-creation .claude/skills/construction-diary-creation && 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-diary-creation
GitHub stars
100
Token cost
~3.6k tokens
SKILL.md length
1,672 words
Files
1
Skills in repo
15
Repo updated
First seen
Licence
MIT

At a glance

Extracts structured data from Finnish construction site daily diary audio recordings (Työmaapäiväkirja) and creates a formatted Word document with extracted fields.

  • Works in 5 steps: Get Audio File Path → Transcribe Audio (gaik-transcriber MCP… → Extract Structured Fields → …
  • The user needs to process construction site managers audio diary recordings into standardized documentation
  • SKILL.md covers When to Use, Input, Tooling Rules (Windows vs… and Workflow, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Construction Diary Creation is an agent skill from GAIK-project/gaik-toolkit. Extracts structured data from Finnish construction site daily diary audio recordings (Työmaapäiväkirja) and creates a formatted Word document with extracted fields. Use when the user needs to process construction site manager's audio diary recordings into standardized documentation.

Its SKILL.md is about 3.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Knowledge Management, covering Journaling and reflection and Word documents. It works with Microsoft Word. The repository describes itself as: Python toolkit providing reusable AI/ML utilities: schema extraction, structured outputs, and production-ready components. The licence is MIT.

When your agent uses it

  • The user needs to process construction site managers audio diary recordings into standardized documentation
  • Tasks that involve Journaling and reflection
  • Tasks that involve Word documents

Example prompts

  • “Use the construction-diary-creation skill to extract structured data from Finnish construction site daily diary audio recordings (Työmaapäiväkirja)…”
  • “/construction-diary-creation”

Requirements

  • Python 3

Workflow steps

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

  1. Get Audio File Path
  2. Transcribe Audio (gaik-transcriber MCP tool)
  3. Extract Structured Fields
  4. Generate Word Document
  5. Save and Present

What it can do on your machine

Read from SKILL.md and the folder at commit e516ece. 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 Diary Creation loads about 3.6k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 1,672 words of instructions outside code blocks.

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

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 GAIK-project/gaik-toolkit at commit e516ece, republished under its MIT licence (© GAIK-project). 1,672 words, ~3,649 tokens.

Download SKILL.mdSave it as .claude/skills/construction-diary-creation/SKILL.md (or your agent's skills folder).
name
construction-diary-creation
description
Extracts structured data from Finnish construction site daily diary audio recordings (Työmaapäiväkirja) and creates a formatted Word document with extracted fields. Use when the user needs to process construction site manager's audio diary recordings into standardized documentation.

Construction Diary Creation (Työmaapäiväkirja)

Transcribes audio recordings from construction site managers and extracts structured information required for official daily construction site diaries (Työmaapäiväkirja). Outputs a clean MS Word document with a 2-column table containing all extracted fields.

This skill is designed to run in Claude Desktop with:

  • An MCP gaik-transcriber server (for transcribing audio/video recordings)

When to Use

Use this skill when:

  • User needs to process a construction site diary audio recording
  • User mentions "työmaapäiväkirja", "construction diary", or "site diary"
  • User wants to extract structured information from site manager's audio notes
  • User asks to process or transcribe a construction site recording
  • User provides an audio file from a Finnish construction site

Input

Required:

  • Audio/video recording file path (e.g., .mp3, .m4a, .wav, .mp4, etc.)
  • The recording should contain a construction site manager verbally describing the day's events

Required parameter:

  • audio_file_path: Full path to the audio/video recording. If not provided, ask the user to specify it.

Tooling Rules (Windows vs Linux Path Safety)

Why this matters

On Windows, Claude Desktop + toolchains sometimes behave like they are in a POSIX shell, producing paths like /mnt/c/.... Meanwhile, your MCP servers may run native Windows Python, expecting C:\.... This mismatch can cause "file not found" or failing shell commands.

Strict rules

  1. Prefer Windows drive-letter paths on Windows Pass file paths like C:\Users\...\recording.m4a to the gaik-transcriber.

  2. Avoid bash commands on Windows If you must run a command on Windows, prefer PowerShell.

  3. When calling gaik-transcriber, use Windows drive-letter paths Pass file paths like C:\Users\...\recording.m4a. If you only have a POSIX/WSL path (e.g., /mnt/c/...), convert it to a Windows path before calling the transcriber.

  4. Never assume the environment is Linux Treat the runtime as OS-ambiguous and enforce the above rules to stay stable.

  5. Never do the following:

  • NEVER run pip install, python -c, or any ad-hoc parsing code
  • NEVER use /mnt/user-data/uploads/... paths unless explicitly provided by the environment

Workflow

Step 1 — Get Audio File Path

If the user has not specified an audio file path, ask for it:

  • Request the full path to the audio recording
  • Verify the path uses Windows format (e.g., C:\Users\...) on Windows systems
  • Confirm the file exists before proceeding
Step 2 — Transcribe Audio (gaik-transcriber MCP tool)

Call the transcription MCP tool:

gaik-transcriber:transcribe_audio
  file_path: <full_path_to_audio_file>
  enhanced: false

Parameters:

  • file_path: Full Windows path to the recording
  • enhanced: Always use false (standard transcription is sufficient)

If transcription fails:

  • Check the path format (ensure Windows drive-letter paths on Windows)
  • Report the error clearly to the user
  • Do NOT proceed with extraction if transcription fails

Important: Preserve the entire transcription text for the extraction step.

Step 3 — Extract Structured Fields

From the transcription, extract the following 20 fields exactly as specified.

CRITICAL EXTRACTION RULES:

  1. Use Finnish field names exactly as listed below
  2. If a field is not mentioned in the transcript, return an empty string ("")
  3. Keep extracted values BRIEF - use only tight keywords, not full sentences
  4. Do NOT hallucinate or invent information
  5. For fields with predefined lists, ONLY select from those lists
  6. Follow the specified format for each field exactly
Fields to Extract (Finnish):

1. Kohde

  • Description: Address or subject of the diary
  • Format: Do not write numbers in words
  • Example: 3285-00 Komeetankuja 6, 02210 Espoo
  • If not mentioned: return ""

2. Laatija

  • Description: Name of the author recording the diary
  • Format: Full name as mentioned
  • If not mentioned: return ""

3. Sää

  • Description: Weather conditions
  • Format: Temperature, wind speed, humidity, ground temperature
  • Example: 3 °C, 2 m/s, 78 % suht. kosteus, Kp: -1.4 C
  • If not mentioned: return ""

4. Päivämäärä

  • Description: Date of the diary entry
  • Format: dd.mm.yyyy or dd.mm if year not mentioned
  • Example: If audio says "20.5", return 20.05
  • If not mentioned: return ""

5. Resurssit - Henkilöstö

  • Description: Personnel resources for the day
  • Format: Työnjohtajat: X hlö, Työntekijät: Y hlö, Alihankkijat: Z hlö, Yhteensä: W hlö
  • Note: Use 0 for categories with no information
  • Example: Työnjohtajat: 2 hlö, Työntekijät: 1 hlö, Alihankkijat: 4 hlö, Yhteensä: 7 hlö
  • If not mentioned: return ""

6. Työviikko

  • Description: Work week number
  • Format: Number only (e.g., 2, 15)
  • If not mentioned: return ""

7. Päivän työt

  • Description: List all tasks of today
  • Include: Completed, partially completed, incomplete, ongoing, and newly started work
  • Format: Brief bullet points or comma-separated list
  • If not mentioned: return ""

8. Päivän tapahtumat

  • Description: Unusual events that were not anticipated
  • Format: ONLY tight keywords
  • If no unusual events: return Ei tapahtumia
  • If not mentioned: return Ei tapahtumia

9. Liitteet

  • Description: Number and type of attachments
  • Format: Count and type (e.g., 4 kuvaa, 1 sähköpostin liite, 1 muistiinpano)
  • Example: 4 photos, 1 email attachment, 1 note
  • If not mentioned: return ""

10. Valvojan huomiot

  • Description: Supervisor's general notes about the day
  • Format: ONLY tight keywords
  • Only if explicitly mentioned
  • If not mentioned: return ""

11. Päivän poikkeamat

  • Description: Issues or deviations in work
  • Format: ONLY tight keywords
  • Examples: delay, damage, unplanned finding
  • Only if mentioned
  • If not mentioned: return ""

12. Aloitetut työvaiheet

  • Description: Work phases started today
  • MUST CHOOSE ONLY FROM THIS LIST:
    • Asbestipurku
    • sisäpurku
    • rungon purku
    • lajittelu
    • työmaan aitaus
    • pölynhallinta
    • massojen ajo
    • romun ajo
    • perusten purku
    • pulverointi
    • timanttityöt
    • suojaustyöt
    • metalli- ja putkipurku työt
    • polttoleikkaus
  • If no match or not mentioned: return ""

13. Käynnissä olevat työvaiheet

  • Description: Work phases currently ongoing
  • MUST CHOOSE ONLY FROM THIS LIST:
    • Asbestipurku
    • sisäpurku
    • rungon purku
    • lajittelu
    • työmaan aitaus
    • pölynhallinta
    • massojen ajo
    • romun ajo
    • perusten purku
    • pulverointi
    • timanttityöt
    • suojaustyöt
    • metalli- ja putkipurku työt
    • polttoleikkaus
  • If no match or not mentioned: return ""

14. Päättyneet työvaiheet

  • Description: Work phases completed today
  • MUST CHOOSE ONLY FROM THIS LIST:
    • Asbestipurku
    • sisäpurku
    • rungon purku
    • lajittelu
    • työmaan aitaus
    • pölynhallinta
    • massojen ajo
    • romun ajo
    • perusten purku
    • pulverointi
    • timanttityöt
    • suojaustyöt
    • metalli- ja putkipurku työt
    • polttoleikkaus
  • If no match or not mentioned: return ""

15. Keskeytyneet työvaiheet

  • Description: Work phases interrupted
  • MUST CHOOSE ONLY FROM THIS LIST:
    • Asbestipurku
    • sisäpurku
    • rungon purku
    • lajittelu
    • työmaan aitaus
    • pölynhallinta
    • massojen ajo
    • romun ajo
    • perusten purku
    • pulverointi
    • timanttityöt
    • suojaustyöt
    • metalli- ja putkipurku työt
    • polttoleikkaus
  • If no match or not mentioned: return ""

16. Pyydetyt lisäajat

  • Description: Requested additional time/extensions
  • Format: ONLY tight keywords
  • Only if mentioned
  • If not mentioned: return ""

17. Tehdyt katselmukset

  • Description: Inspections performed
  • Format: ONLY tight keywords
  • Only if mentioned
  • If not mentioned: return ""

18. Valvojan huomautukset

  • Description: Supervisor's remarks/warnings
  • Format: ONLY tight keywords
  • Only if mentioned
  • If not mentioned: return ""

19. Valvojan allekirjoitus

  • Description: Supervisor's signature
  • Only if explicitly stated
  • If not mentioned: return ""

20. Vastaavan allekirjoitus

  • Description: Responsible person's signature
  • Only if explicitly stated
  • If not mentioned: return ""
Show full SKILL.md (610 more words)Show less
Step 4 — Generate Word Document

Before creating the document, view the docx skill:

view /mnt/skills/public/docx/SKILL.md

Then create a new Word document using the docx skill's "Creating a new Word document" workflow.

Document Structure:

  1. Title: TYÖMAAPÄIVÄKIRJA (centered, bold, large font)

  2. 2-Column Table:

    • Column 1: Field name (Finnish)
    • Column 2: Extracted value
    • Include all 20 fields in order, even if value is empty string

Table Format:

| Kenttä                      | Arvo                           |
|-----------------------------|--------------------------------|
| Kohde                       | [extracted value or ""]        |
| Laatija                     | [extracted value or ""]        |
| Sää                         | [extracted value or ""]        |
| Päivämäärä                  | [extracted value or ""]        |
| Resurssit - Henkilöstö      | [extracted value or ""]        |
| Työviikko                   | [extracted value or ""]        |
| Päivän työt                 | [extracted value or ""]        |
| Päivän tapahtumat           | [extracted value or "Ei tapahtumia"] |
| Liitteet                    | [extracted value or ""]        |
| Valvojan huomiot            | [extracted value or ""]        |
| Päivän poikkeamat           | [extracted value or ""]        |
| Aloitetut työvaiheet        | [extracted value or ""]        |
| Käynnissä olevat työvaiheet | [extracted value or ""]        |
| Päättyneet työvaiheet       | [extracted value or ""]        |
| Keskeytyneet työvaiheet     | [extracted value or ""]        |
| Pyydetyt lisäajat           | [extracted value or ""]        |
| Tehdyt katselmukset         | [extracted value or ""]        |
| Valvojan huomautukset       | [extracted value or ""]        |
| Valvojan allekirjoitus      | [extracted value or ""]        |
| Vastaavan allekirjoitus     | [extracted value or ""]        |

Document Formatting:

  • Use clean, professional formatting
  • Table should have borders
  • First column (field names) should be slightly bold
  • Keep the document simple and readable
Step 5 — Save and Present
  1. Save the document with a descriptive filename, e.g., Tyomaapaivakirja_[Date].docx
  2. Use present_files to share the document with the user

Guardrails

Critical Rules to Prevent Hallucination:

MUST DO:

  • Extract ONLY information explicitly mentioned in the transcript
  • Use exact Finnish field names as specified
  • Keep extracted values BRIEF (tight keywords only)
  • Return empty string ("") if field not mentioned in transcript
  • For work phases (fields 12-15), ONLY select from the predefined lists
  • For date fields, follow the exact format specified
  • Preserve numbers as numbers, not words (e.g., "3285" not "kolmetuhatta...")

MUST NOT DO:

  • NEVER invent or hallucinate information not in the transcript
  • NEVER add assumptions or interpretations
  • NEVER use values outside predefined lists for work phase fields
  • NEVER create full sentences when "tight keywords" are requested
  • NEVER leave out fields from the table (include all 20 fields)
  • NEVER change Finnish field names
  • NEVER guess dates, numbers, or names
Field-Specific Validation:

Date (Päivämäärä):

  • Must be in format dd.mm.yyyy or dd.mm
  • If transcript says "twentieth of May", extract as 20.05

Resources (Resurssit - Henkilöstö):

  • Must follow exact format with categories and counts
  • Use 0 for categories with no information
  • Must include "Yhteensä" (total) if any category has data

Work Phases (Fields 12-15):

  • STRICT: Only use values from the predefined list
  • If transcript mentions a work type not in the list, return ""
  • Multiple values can be comma-separated if multiple phases apply

Päivän tapahtumat:

  • Special case: If nothing unusual mentioned, return Ei tapahtumia
  • Otherwise use tight keywords only
Error Handling:

If transcription fails:

  • Report error clearly to user
  • Do NOT attempt extraction without transcript
  • Provide troubleshooting steps (check file path, file format, etc.)

If transcript is unclear or ambiguous:

  • Extract what is clear
  • Return "" for unclear fields
  • Do NOT guess or make assumptions

If transcript is in wrong language:

  • Attempt extraction anyway
  • Note to user that transcript may not match expected Finnish format

Examples

Example 1: Standard Daily Diary

User prompt: "Process this construction diary recording: C:\Sites\diary-2024-05-20.mp3"

Expected behavior:

  1. Transcribe audio using gaik-transcriber
  2. Extract all 20 fields from transcript
  3. Create Word document with 2-column table
  4. Save as Tyomaapaivakirja_20.05.2024.docx
  5. Present file to user
Example 2: Minimal Information

User prompt: "Extract diary data from C:\Audio\site-note.m4a"

Expected behavior:

  1. Transcribe audio
  2. Extract available fields
  3. Return "" for fields not mentioned
  4. Return Ei tapahtumia for Päivän tapahtumat if nothing unusual
  5. Create document with all 20 fields (including empty ones)
  6. Present file to user
Example 3: Missing File Path

User prompt: "Create a construction diary from my recording"

Expected behavior:

  1. Ask user for the audio file path
  2. Explain format needed (e.g., C:\path\to\file.mp3)
  3. Wait for user to provide path
  4. Proceed with transcription and extraction once path is provided

Notes

  • The skill focuses on accurate extraction over fancy formatting
  • Never hallucinate - empty fields are acceptable and expected
  • The transcript may contain casual speech, filler words, and unclear audio - extract what is clear
  • Work phase lists are closed sets - do not add values not in the lists
  • All Finnish terminology must be preserved exactly as specified
  • The output document should be simple and professional, suitable for official construction documentation

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

Files

Just SKILL.md in implementation_layer/no-code-assets/agent-skills/construction-diary-creation/construction-diary-creation of GAIK-project/gaik-toolkit.

Open the folder on GitHubat commit e516ece

Compare with similar skills

Construction Diary Creation 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 Diary Creation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Construction Diary Creation this skillGAIK-project/gaik-toolkit100—~3.6kAutomated safety check: PassMIT
Dev Diary MdxMillenniumDawn/Millennium-Dawn139—~958Automated safety check: PassCC-BY-SA-4.0
Biomedical PaperLeoYeAI/openclaw-master-skills2.2k—~3.3kAutomated safety check: PassMIT
Article Format Adjustmentaipoch/medical-research-skills2k—~2.4kAutomated safety check: PassMIT
Academic Paper ComposerAAASS554/codex-academic-paper-skills5391 repos~3.2kAutomated safety check: PassMIT
Journal Copyeditor DOCXmikemikeqqq/copyeditor-skill292—~3.9kAutomated safety check: PassMIT

Similar skills

  • Dev Diary Mdx

    MillenniumDawn/Millennium-Dawn

    Convert a Millennium Dawn dev diary .docx into a publish-ready .mdx for the docs site: frontmatter, headers, and images placed in reading order, with the author's voice preserved.

    139 GitHub stars~958 tokensUpdated today
    Documents & OfficeAuto-check passed

  • Biomedical Paper

    LeoYeAI/openclaw-master-skills

    AI-powered biomedical manuscript generation with docx output.

    2.2k GitHub stars~3.3k tokensUpdated 2 mo ago
    Documents & OfficeAuto-check passed

  • Article Format Adjustment

    aipoch/medical-research-skills

    Adjust academic paper formatting and convert between DOCX/LaTeX/Markdown when you need to meet a journal or school template requirement.

    2k GitHub stars~2.4k tokensUpdated 22 days ago
    Documents & OfficeAuto-check passed

  • Academic Paper Composer

    AAASS554/codex-academic-paper-skills

    A skill your agent uses when the user needs to turn a real software engineering / computer science project and an existing thesis draft into a submission-ready undergraduate thesis manuscript.

    539 GitHub starsUsed in 1 repo~3.2k tokens
    Documents & OfficeAuto-check passed

  • Journal Copyeditor DOCX

    mikemikeqqq/copyeditor-skill

    Comprehensive academic journal copyediting and manuscript review for Microsoft Word (.docx) files across disciplines and target journals.

    292 GitHub stars~3.9k tokensUpdated 2 mo ago
    Documents & OfficeAuto-check passed

  • Mineru Document Explorer

    opendatalab/MinerU-Document-Explorer

    MinerU Document Explorer — Agent-native knowledge engine. An agent skill from opendatalab/MinerU-Document-Explorer.

    638 GitHub stars~6.2k tokensUpdated 5 mo ago
    Documents & OfficeAuto-check: notes

More from GAIK-project/gaik-toolkit

All 15 skills in this repo

  • Brief To Slides

    GAIK-project/gaik-toolkit

    Builds a visual, editable PowerPoint (.pptx) deck with speaker-ready notes, exact timing, citations and a layout-checked design from a topic, an audience and a length, using only the user's own…

    100 GitHub stars~2.8k tokensUpdated today
    Auto-check passed

  • Gaik Toolkit

    GAIK-project/gaik-toolkit

    GAIK toolkit overview and reference. An agent skill from GAIK-project/gaik-toolkit.

    100 GitHub stars~5.7k tokensUpdated today
    Auto-check passed

  • Extracting Structured Data

    GAIK-project/gaik-toolkit

    Extracts structured data — fields, tables, line items — out of documents into a validated schema using the gaik toolkit, and designs schemas that stay inside provider limits and produce checkable…

    100 GitHub stars~3.2k tokensUpdated today
    Auto-check passed

  • Parsing Documents

    GAIK-project/gaik-toolkit

    Converts PDFs, scans, and Word documents into text or markdown with the gaik toolkit's parsers, choosing the parser that will not silently destroy the structure the downstream task depends on.

    100 GitHub stars~2.3k tokensUpdated today
    Auto-check passed

  • Searching Documents

    GAIK-project/gaik-toolkit

    Builds and debugs retrieval with the gaik toolkit — PgVectorStore, Ranker, FinnishTextProcessor, RelevanceGate — as hybrid search: pgvector similarity plus Postgres full-text, fused by rank, and the…

    100 GitHub stars~4.2k tokensUpdated today
    Auto-check passed

  • Gaik Add Examples

    GAIK-project/gaik-toolkit

    Adds or updates working code examples for GAIK toolkit components and pipelines in implementationlayer/examples/.

    100 GitHub stars~2.4k tokensUpdated today
    Auto-check: notes

Works with

Categories

Questions about Construction Diary Creation

What does Construction Diary Creation do?

Extracts structured data from Finnish construction site daily diary audio recordings (Työmaapäiväkirja) and creates a formatted Word document with extracted fields. Construction Diary Creation is an agent skill from GAIK-project/gaik-toolkit. Extracts structured data from Finnish construction site daily diary audio recordings (Työmaapäiväkirja) and creates a formatted Word document with extracted fields.

When should I use Construction Diary Creation?

Construction Diary Creation fits situations like: the user needs to process construction site managers audio diary recordings into standardized documentation; tasks that involve Journaling and reflection; tasks that involve Word documents.

How do I install Construction Diary Creation in Claude Code?

Run `npx skills add GAIK-project/gaik-toolkit --skill construction-diary-creation -a claude-code`. Or copy the skill folder (implementation_layer/no-code-assets/agent-skills/construction-diary-creation/construction-diary-creation in GAIK-project/gaik-toolkit) into .claude/skills/construction-diary-creation in your project. Claude Code loads it when a task matches its description.

How do I install Construction Diary Creation in Codex?

Run `npx skills add GAIK-project/gaik-toolkit --skill construction-diary-creation -a codex`. Or copy the skill folder (implementation_layer/no-code-assets/agent-skills/construction-diary-creation/construction-diary-creation in GAIK-project/gaik-toolkit) into .agents/skills/construction-diary-creation in your project. Codex loads it when a task matches its description.

Can I use Construction Diary Creation 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 GAIK-project/gaik-toolkit --skill construction-diary-creation -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-diary-creation, .gemini/skills/construction-diary-creation, .github/skills/construction-diary-creation and .opencode/skills/construction-diary-creation in your project.

What does Construction Diary Creation need to run?

SKILL.md names no scripts, command-line tools or credentials: Construction Diary Creation is instructions for the agent only. Our summary lists: Python 3.

Does Construction Diary Creation 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 Diary Creation 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 Diary Creation use?

Construction Diary Creation 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 Diary Creation use?

About 3.6k tokens (SKILL.md is roughly 15k 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 Diary Creation?

Skills that share tags, products or a category with Construction Diary Creation: Dev Diary Mdx (MillenniumDawn/Millennium-Dawn, 139 stars), Biomedical Paper (LeoYeAI/openclaw-master-skills, 2.2k stars), Article Format Adjustment (aipoch/medical-research-skills, 2k stars) and Academic Paper Composer (AAASS554/codex-academic-paper-skills, 539 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Construction Diary Creation?

GAIK-project (a GitHub organization) maintains it in GAIK-project/gaik-toolkit, which has 100 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 9, 2026.

Source: GAIK-project/gaik-toolkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.