Devlog Skill

A standardized journaling skill for OpenClaw agents to track progress, tasks, and project status using dev-log-cli.

Security Scan

The skill's requirements and instructions are consistent with a CLI-based developer journaling tool; it installs dev-log-cli via pipx from PyPI and contains no obvious attempts to access unrelated secrets or system resources.

Purpose & Capability

The skill is a journaling/devlog helper and only requires the dev-log-cli tool. The SKILL.md, usage examples, and the setup.sh all align with that purpose — there are no unrelated credentials, binaries, or configuration paths requested.

Instruction Scope

Runtime instructions are limited to using the devlog CLI to add, list, view, edit, search, and show stats. The included setup.sh only ensures pipx and the dev-log-cli tool are installed; there are no instructions to read unrelated files, exfiltrate data, or contact unexpected endpoints.

Install Mechanism

There is no platform install spec, but the bundled setup.sh installs pipx via pip and then installs dev-log-cli using pipx (pulling packages from PyPI). Pulling packages from PyPI is expected for a Python CLI but carries the usual supply-chain risk of installing third-party code at user level. The script uses well-known tools (python3/pip/pipx) and does not download from obscure URLs or run obfuscated commands.

Credentials

The skill requests no environment variables, credentials, or config paths. The install script modifies the user's PATH (via pipx ensurepath and an exported PATH) which is reasonable for making a CLI available, but there are no demands for secrets or unrelated tokens.

Persistence & Privilege

The skill is not always-enabled and does not request elevated or cross-skill configuration changes. It can be invoked autonomously (platform default), which is normal; there is no evidence it attempts to persist beyond installing the CLI and creating a local SQLite DB (as described).

Assessment

This skill appears coherent for its stated purpose, but before installing: (1) review the dev-log-cli project on PyPI/GitHub to confirm you trust its maintainer and to check for network calls/telemetry or surprising behaviors; (2) run setup.sh manually (inspect it first) rather than granting automated execution — it will install pipx and the package into your user environment; (3) be careful not to log secrets into the devlog (entries go into a local SQLite DB by design); (4) if you prefer isolation, install the CLI into a controlled virtual environment or container rather than your global user environment.

A standardized journaling skill for OpenClaw agents to track progress, tasks, and project status using dev-log-cli.

Description

This skill enables agents to maintain a professional developer log. It's designed to capture context, project milestones, and task statuses in a structured SQLite database.

Requirements

• dev-log-cli (installed via pipx)

Links

• GitHub: https://github.com/CrimsonDevil333333/dev-log-cli
• PyPI: https://pypi.org/project/dev-log-cli/
• ClawHub: https://clawhub.com/skills/devlog-skill (Pending Publication)

Usage

📝 Adding Entries

Agents should use this to log significant progress or blockers.

devlog add "Finished implementing the auth module" --project "Project Alpha" --status "completed" --tags "auth,feature"

📋 Listing Logs

View recent activity for context.

devlog list --project "Project Alpha" --limit 5

📊 Viewing Stats

Check project health and activity.

devlog stats --project "Project Alpha"

🔍 Searching

Find historical context on specific topics.

devlog search "infinite loop"

🛠️ Editing/Viewing

Detailed inspection or correction of entries.

devlog view <id>
devlog edit <id>

Internal Setup

The skill includes a setup.sh to ensure the CLI is available.