CtrlK
BlogDocsLog inGet started
Tessl Logo

daily

扫描并补齐缺失的每日工作日志。对比 logs/daily/ 已有日志与 git 有提交的日期(按 07:00 边界归属),列出「昨天及之前、有 commit 但无日志」的日期,逐日调用 generate_log.py 生成骨架,再按 SKILL_10b 补写微信通知和改动意义。不执行 git add/commit,不补齐今天。

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/daily/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and well-sequenced with confirmation checkpoints and clear one-level references, scoring at the top on those dimensions; its only weakness is mild redundancy between the inline format/statistics sections and the step descriptions.

Suggestions

Consolidate the '插入格式' template with step 5.2 to remove the duplicated notification-format block.

Reduce '数据统计参考命令' to a pointer to SKILL_10b §5 unless the inline copy is essential for quick reference.

Consider moving the full notification template into SKILL_10b and keeping only a short example inline.

DimensionReasoningScore

Conciseness

Mostly lean and command-dense without explaining concepts Claude already knows, but the '插入格式' template and '数据统计参考命令' sections partly duplicate step 5 and SKILL_10b §5, so some tokens could be tightened; matches the 'mostly efficient but includes some unnecessary explanation or could be tightened' anchor.

2 / 3

Actionability

Provides fully executable bash commands (ls/grep, git log --date=iso with awk, python generate_log.py) plus exact notification-format templates, making guidance copy-paste ready.

3 / 3

Workflow Clarity

Clear numbered 1–6 sequence with an explicit user-confirmation checkpoint (step 4) before the batch backfill, per-day reporting, and explicit edge-case handling (无提交日 → 太史公曰), satisfying the validation-checkpoint requirement for batch operations.

3 / 3

Progressive Disclosure

Self-contained overview that defers detail to one-level-deep, clearly signaled references (generate_log.py, SKILL_10b, sima-qian-style) listed in a '相关资源' section; no nested/deep references.

3 / 3

Total

11

/

12

Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinctive, naming concrete actions and a clear niche, but it lacks an explicit 'Use when...' trigger clause and natural trigger-term coverage, capping completeness and trigger quality at 2.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when the user asks to fill in or backfill missing daily work logs, or mentions 日志缺口/补齐日志'.

Broaden trigger terms with natural variations users might say (e.g. '工作日志', '日志补齐', 'daily log') to improve trigger coverage.

Lead with a concise capability summary before the procedural detail so the 'what' is scannable at a glance.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — '扫描并补齐缺失的每日工作日志', '对比 logs/daily/ 已有日志与 git 有提交的日期', '逐日调用 generate_log.py 生成骨架', '补写微信通知和改动意义' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly answers 'what' (scan and backfill missing daily logs via git comparison), but 'when' is only implied with no explicit 'Use when...' trigger clause, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Contains the natural term '每日工作日志' and '补齐缺失', but reads as a process description rather than natural trigger phrasing and lacks common variations or an explicit 'Use when...' trigger; matches the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

Highly specific niche — daily work logs, git commit dates with 07:00 boundary, WeChat notifications, SKILL_10b — making it clearly distinguishable and unlikely to trigger for the wrong skill.

3 / 3

Total

10

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
baojie/shiji-kb
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.