Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Daily Commit Logbook

v1.0.0

Generate daily internship logbook drafts and weekly internship reports from GitHub and GitLab commit activity. Build Indonesian MIS-friendly summaries, prepa...

0· 64·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for mozaldy/daily-commit-logbook.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Daily Commit Logbook" (mozaldy/daily-commit-logbook) from ClawHub.
Skill page: https://clawhub.ai/mozaldy/daily-commit-logbook
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install daily-commit-logbook

ClawHub CLI

Package manager switcher

npx clawhub@latest install daily-commit-logbook
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the implementation: scripts collect GitHub/GitLab push events via the 'gh' and 'glab' CLIs, build Indonesian logbook text, save reports, and optionally schedule OpenClaw cron jobs and Telegram delivery. Required tools and repository-context files are coherent with the stated goals.
Instruction Scope
The scripts read repo diffs, workspace files (AGENTS.md, HEARTBEAT.md, reports/), write a local .env, create pending-report JSON files, and (when invoked) call a peer skill 'mis-logbook-submit' if present. This is within scope but significant: the cron payload causes an agent to run a workspace command and post its stdout to a Telegram chat exactly as-is, and some helper scripts can call a peer skill to perform live MIS submission. Review those behaviors before enabling automation.
Install Mechanism
Instruction-only skill (no remote downloads or package installs). It relies on existing CLIs (gh, glab, jq, openclaw) and Node.js; nothing is fetched from arbitrary URLs or written by an installer.
Credentials
The skill does not declare required secret env vars in the registry, but expects a GITHUB_USER, a Telegram chat id when setting up cron, and authenticated 'gh'/'glab' CLIs in the runtime environment. It will write a local .env containing GITHUB_USER. It does not itself request API tokens, but successful use requires authenticated CLI clients (which hold credentials outside the skill).
!
Persistence & Privilege
The setup scripts modify the user's crontab (removing specific legacy lines), write OpenClaw cron job entries to ~/.openclaw/cron/jobs.json, update HEARTBEAT.md in the workspace, and restart the OpenClaw gateway. These are expected for scheduler setup but are relatively privileged actions that change scheduler state and restart services — review and backup crontab and OpenClaw cron before running.
Assessment
This skill appears to do what it says: read commit activity (via authenticated 'gh'/'glab'), generate Indonesian logbook drafts and weekly LaTeX reports, and optionally schedule an OpenClaw cron job that will post the draft to a Telegram chat for approval. Before installing or running setup scripts you should: 1) ensure you have and trust the 'gh' and 'glab' CLI authentication (the skill relies on those credentials but doesn't ask for tokens directly), 2) pick and verify the Telegram chat id (the cron will cause an agent to post the script stdout verbatim to that chat), 3) back up your crontab and ~/.openclaw/cron/jobs.json because setup scripts modify them and restart the OpenClaw gateway, 4) inspect or provide (and audit) the peer skill mis-logbook-submit if you plan to enable automatic submission — that peer code actually performs MIS submissions, and 5) run setup scripts in test mode and review what they write (the skill writes a .env and HEARTBEAT.md in the workspace). If any of those changes are unacceptable (automatic posting to Telegram, restarting gateway, or altering cron), do not run the setup scripts — you can still run the report generation scripts manually.
scripts/generate-report.js:75
Shell command execution detected (child_process).
scripts/generate-weekly-report.js:345
Shell command execution detected (child_process).
Patterns worth reviewing
These patterns may indicate risky behavior. Check the VirusTotal and OpenClaw results above for context-aware analysis before installing.

Like a lobster shell, security has layers — review code before you run it.

latestvk974yszw2syx1rbk7291pc1q15850hns
64downloads
0stars
1versions
Updated 1w ago
v1.0.0
MIT-0

Daily Commit Logbook

Generate Indonesian internship logbook text from GitHub and GitLab activity, then optionally schedule Telegram approval flows and weekly LaTeX reports.

Quick start

Generate today's report:

GITHUB_USER="your-github-username" bash scripts/generate-report.sh

Or save reusable local config in daily-commit-logbook/.env:

GITHUB_USER=your-github-username
WEEKLY_REPORT_AUTHOR=Internship Student
WEEKLY_REPORT_WEEK_ONE_START=2026-01-05

Setup daily Telegram approval delivery:

bash scripts/setup-cron.sh \
  --time "18:00" \
  --timezone "WIB" \
  --github-user "your-github-username" \
  --telegram-chat "<telegram-chat-id>"

Setup the Monday weekly report delivery:

bash scripts/setup-weekly-cron.sh \
  --time "18:10" \
  --timezone "WIB" \
  --telegram-chat "<telegram-chat-id>"

Required environment

Install and authenticate:

  • gh for GitHub activity
  • glab for GitLab activity
  • jq for JSON processing
  • OpenClaw CLI for cron setup

If the scripts are not installed at the workspace root, set OPENCLAW_WORKSPACE=/path/to/workspace before running them.

Main scripts

  • scripts/generate-report.sh - build the daily dual-version report and save reports/commit-report-YYYY-MM-DD.md
  • scripts/extract-mis-activity.sh - extract the MIS-ready activity paragraph from the daily report
  • scripts/render-telegram-approval-request.sh - generate the daily report, save a pending draft, and print a Telegram-ready approval request
  • scripts/submit-pending-logbook.sh - submit the latest pending MIS draft after explicit user confirmation
  • scripts/render-whatsapp-message.sh - direct-submit helper for manual fallback/debugging
  • scripts/generate-weekly-report.sh - generate the previous week's LaTeX report
  • scripts/render-weekly-telegram-message.sh - print a Telegram-ready weekly summary message
  • scripts/setup-cron.sh - install the recurring daily OpenClaw cron job
  • scripts/setup-weekly-cron.sh - install the recurring Monday weekly report cron job

Behavior

  1. Fetch same-day push activity from GitHub and GitLab.
  2. Read changed files and diff hunks, not only commit titles.
  3. Apply repo-specific context from references/repo-contexts.json.
  4. Render Indonesian logbook text in two versions, standard and more natural for MIS.
  5. Save a pending MIS draft and wait for explicit confirmation before submission.
  6. Reuse the same diff-aware analysis for weekly internship reports.

References

  • Read references/format-guide.md for Indonesian phrasing and activity patterns.
  • Edit references/repo-contexts.json to describe your repos and mark personal repos as excluded from internship reports.

Notes

  • The daily setup script writes daily-commit-logbook/.env with the chosen GitHub username for later runs.
  • The weekly report author defaults to Internship Student unless WEEKLY_REPORT_AUTHOR is set.
  • The internship week number defaults to week 1 unless WEEKLY_REPORT_WEEK_ONE_START is configured.
  • The normal flow is Telegram approval first, MIS submission second.

Comments

Loading comments...