# Send Dev Chronicle to your agent Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually. ## Fast path - Download the package from Yavira. - Extract it into a folder your agent can access. - Paste one of the prompts below and point your agent at the extracted folder. ## Suggested prompts ### New install ```text I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete. ``` ### Upgrade existing ```text I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run. ``` ## Machine-readable fields ```json { "schemaVersion": "1.0", "item": { "slug": "dev-chronicle", "name": "Dev Chronicle", "source": "tencent", "type": "skill", "category": "开发工具", "sourceUrl": "https://clawhub.ai/sssamuelll/dev-chronicle", "canonicalUrl": "https://clawhub.ai/sssamuelll/dev-chronicle", "targetPlatform": "OpenClaw" }, "install": { "downloadUrl": "/downloads/dev-chronicle", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=dev-chronicle", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "packageFormat": "ZIP package", "primaryDoc": "SKILL.md", "includedAssets": [ "README.md", "SKILL.md", "config.json", "references/voice-profile.md", "scripts/gather.sh" ], "downloadMode": "redirect", "sourceHealth": { "source": "tencent", "slug": "dev-chronicle", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-05-02T12:00:58.320Z", "expiresAt": "2026-05-09T12:00:58.320Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=dev-chronicle", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=dev-chronicle", "contentDisposition": "attachment; filename=\"dev-chronicle-1.0.1.zip\"", "redirectLocation": null, "bodySnippet": null, "slug": "dev-chronicle" }, "scope": "item", "summary": "Item download looks usable.", "detail": "Yavira can redirect you to the upstream package for this item.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/dev-chronicle" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] } }, "links": { "detailUrl": "https://openagent3.xyz/skills/dev-chronicle", "downloadUrl": "https://openagent3.xyz/downloads/dev-chronicle", "agentUrl": "https://openagent3.xyz/skills/dev-chronicle/agent", "manifestUrl": "https://openagent3.xyz/skills/dev-chronicle/agent.json", "briefUrl": "https://openagent3.xyz/skills/dev-chronicle/agent.md" } } ``` ## Documentation ### DevChronicle — Narrative Engineering Journal DevChronicle generates prose chronicles of developer work — not dashboards, not metrics, not bullet lists. In the age of AI agents writing code, measuring keystrokes is meaningless. What matters is what you decided, what you killed, and where you're going. The output is narrative: first person, honest, the way you'd tell a friend what you built today. ### Setup On first use, check for {baseDir}/config.json. If it doesn't exist, create it by asking the user: { "projectDirs": ["~/Projects"], "projectDepth": 3, "memoryDir": null, "sessionsDir": null } projectDirs: directories to scan for git repos (array, supports ~) projectDepth: how deep to search for .git folders (default: 3) memoryDir: path to OpenClaw memory files, or null to auto-detect (/memory) sessionsDir: path to session transcripts, or null to auto-detect (~/.openclaw/agents/main/sessions) ### Gathering Data Run the gather script to collect raw data for a period: bash {baseDir}/scripts/gather.sh [YYYY-MM-DD] [days] Examples: bash {baseDir}/scripts/gather.sh — today only bash {baseDir}/scripts/gather.sh 2026-02-19 7 — week ending Feb 19 The script reads {baseDir}/config.json for paths. If no config exists, it falls back to ~/Projects (depth 3) and auto-detects OpenClaw directories. After gathering, read the output and generate a chronicle. ### Data Sources (priority order) Git History (primary signal) — commits across all repos in configured directories Memory Files — memory/YYYY-MM-DD.md files contain decisions, context, things worth remembering Session Transcripts — JSONL files from OpenClaw sessions; richest context but heavy. Scan metadata line first, only read relevant sessions. External Tools (optional) — Trello, Notion, calendar, etc. Enrichment, not primary. ### Voice Critical: Read {baseDir}/references/voice-profile.md before generating any chronicle. The voice IS the product. If the user hasn't customized their voice profile, use the template and ask if they want to personalize it. A chronicle without voice is just a changelog. Core rules (regardless of voice profile): Decisions > tasks. What got rejected matters as much as what shipped. No corporate speak. No "leveraged", "synergized", "deliverables", "open threads", "action items". Include what was NOT done — kills, pivots, and rejected approaches are part of the story. Emotional beats matter — the satisfaction, frustration, surprise. These are human signals. Be personal. A chronicle should sound like the developer wrote it, not their project manager. If it reads like a status report, rewrite it. Structure is a suggestion, not a cage. If the day had one big theme, write one section. If it was chaos, let it be chaotic. Don't force headers. ### Formats Daily Chronicle (default — aim for ~500-800 words, not a novel) # Chronicle — [Date] [Opening: set the scene in 1-2 punchy sentences] ## [Theme 1] [Narrative: what happened, why, what got killed or rejected, how it felt] ## [Theme 2] [...] [Weave metrics naturally: "12 commits later..." not a stats block at the end] [End with what's unfinished — but as narrative, not a TODO list] Rules: Daily = tight. One screen of text. Save the epic for weekly. No "Metrics" section. If commit count matters, weave it in. "67 commits across two days" belongs in a sentence, not a table. No "Open Threads" or "Next Steps". If something's unfinished, say it where it fits: "El Press Kit sigue esperando que Angélica suba el PDF." Done. Numbers without story are noise. "5 deploys" means nothing. "Deployed 5 times because the server kept OOM-killing on a 914MB box" means something. Weekly Chronicle — roll up daily themes into arcs. This one CAN be long. Emphasize direction and pivots over individual tasks. Standup — telegraphic: yesterday / today / blockers. Three bullets max each. Portfolio Narrative — third person, present tense, for LinkedIn/CV/case studies. Punchy and honest, not marketing-speak. ### Direction/Execution Ratio When enough data exists (weekly+), calculate and mention: Spec lines vs code lines — are you building or planning? Commits vs decisions — activity vs impact Kills — what got cut and why (kills show taste) Pivots — direction changes and their reasoning This is not a KPI. It's a mirror. ## Trust - Source: tencent - Verification: Indexed source record - Publisher: sssamuelll - Version: 1.0.1 ## Source health - Status: healthy - Item download looks usable. - Yavira can redirect you to the upstream package for this item. - Health scope: item - Reason: direct_download_ok - Checked at: 2026-05-02T12:00:58.320Z - Expires at: 2026-05-09T12:00:58.320Z - Recommended action: Download for OpenClaw ## Links - [Detail page](https://openagent3.xyz/skills/dev-chronicle) - [Send to Agent page](https://openagent3.xyz/skills/dev-chronicle/agent) - [JSON manifest](https://openagent3.xyz/skills/dev-chronicle/agent.json) - [Markdown brief](https://openagent3.xyz/skills/dev-chronicle/agent.md) - [Download page](https://openagent3.xyz/downloads/dev-chronicle)