菜单
Generate and synchronize the canonical daily work report index. Use when updating WORK_REPORT/index.md, adding diary/report navigation, maintaining collapsible archives, or checking that daily work report links are current.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | work-report-index |
| repo | LIghtJUNction/LIghtJUNction |
| description | Generate and synchronize the canonical daily work report index. Use when updating WORK_REPORT/index.md, adding diary/report navigation, maintaining collapsible archives, or checking that daily work report links are current. |
Use this skill when a task involves the canonical daily diary/work report index for the assistant home workspace.
The canonical report directory is:
/root/.kimaki/projects/lightjunction/WORK_REPORT
The index file is:
/root/.kimaki/projects/lightjunction/WORK_REPORT/index.md
Keep WORK_REPORT/index.md generated from actual YYYY/MM/DD.md files instead
of hand-maintaining links. As the diary history grows, keep the newest entries
easy to scan and fold older entries with Markdown/HTML <details> blocks.
From the lightjunction project root, run:
uv run scripts/sync-work-report-index.py
This scans the canonical WORK_REPORT tree and rewrites the index.
After syncing, check that the index is current:
uv run scripts/sync-work-report-index.py --check
To preview the generated Markdown without writing:
uv run scripts/sync-work-report-index.py --dry-run
Recent Reports.Archived Reports.--recent-count N when a smaller or larger expanded section is useful.workspace/reports/; only canonical
daily reports under WORK_REPORT/YYYY/MM/DD.md belong in this index.uv run scripts/sanitize-work-reports.py and then
uv run scripts/sanitize-work-reports.py --check to redact local paths, email
addresses, raw social record URIs, wallet addresses, and transaction hashes.Bilibili social workflow for the assistant. Use when reading Bilibili comments, posting Bilibili comments or replies, or reading/sending Bilibili private messages with the user's cookie-backed session.
Low-star open-source contribution workflow. Use this when preparing or doing small, low-risk PRs/issues, candidate queues, or maintainer follow-up for early-stage active repositories.
Low-star open-source contribution workflow. Use this skill when exploring small, recently active GitHub repositories, preparing local candidate queues, doing tiny docs fixes, typo fixes, broken-link fixes, small tests, obvious low-risk bugs, light code review, or following up on previously opened PRs.
AgentMail mailbox workflow for the assistant email lightjunction@agentmail.to. Use when reading, sending, configuring, or documenting the assistant's AgentMail email address, mailbox identity, CLI usage, or email safety rules.
Automatic cleanup workflow for Kimaki/OpenCode operations. Use when archiving completed sessions, reducing Discord thread noise, cleaning local workspace scratch areas, pruning temporary files, checking stale local state, or closing no-op scheduled runs safely.
Use for scheduled or user-triggered maintenance of the owner's own GitHub projects: triaging notifications, reading issues/mentions, checking Actions and releases, making small fixes, and leaving clean handoff notes.