Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub Β· Developer Tools
Dev Chronicle
Generate narrative chronicles of developer work from git history, session transcripts, and memory files. Use when the user asks "what did I do today/this wee...
skill openclawclawhub Free
Generate narrative chronicles of developer work from git history, session transcripts, and memory files. Use when the user asks "what did I do today/this wee...
β¬ 0 downloads β
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- README.md, SKILL.md, config.json, references/voice-profile.md, scripts/gather.sh
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- 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.
New install
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
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.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.1
Provenance
- Publisher
- sssamuelll
- Source page
- View original listing
- Canonical URL
- Open canonical page
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 (<workspace>/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.
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
3 Docs1 Scripts1 Config
- SKILL.md
- README.md
- references/voice-profile.md
- scripts/gather.sh
- config.json