CtrlK
BlogDocsLog inGet started
Tessl Logo

daily

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

61

Quality

77%

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

68%Weight 40%Scale 1-5

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

The body is well-structured, actionable, and token-efficient with concrete commands and a clear two-mode workflow, but the batch backfill loop lacks an explicit output-validation feedback loop, capping workflow clarity.

Suggestions

Add a post-generation verification step (e.g. re-read logs/daily/D.md and confirm the 微信群通知 block and 改动意义 are present and well-formed) with a fix-and-regenerate retry path to satisfy the batch-operation feedback-loop expectation.

Format the '相关资源' entries as markdown links and consider moving the full notification template into a referenced file to tighten the overview.

Replace the 'D+1' placeholder with a concrete date-substitution note or an executable snippet so the stats commands are copy-paste ready.

DimensionReasoningScore

Conciseness

The body is mostly lean — bash snippets, numbered steps, and a '铁律' list — and delegates full detail to SKILL_10b rather than duplicating; minor trim opportunities exist in the '数据统计参考命令' and '插入格式' template sections.

4 / 5

Actionability

Executable commands are provided throughout (ls/grep scan, a real git-log+awk pipeline, 'python logs/daily/generate_log.py D', git --since/--until stats) plus a concrete output template; minor gaps are the 'D+1' placeholder notation that needs substitution.

4 / 5

Workflow Clarity

The no-arg flow is clearly sequenced (steps 1–6 with a step-4 confirmation gate and per-day/summary reporting), but as a batch operation it lacks a validate→fix→retry feedback loop on the generated logs, which caps workflow clarity at 3 per the batch-operation guideline.

3 / 5

Progressive Disclosure

Structure is good with clearly labeled sections and a '相关资源' list pointing one level deep to generate_log.py, SKILL_10b, and sima-qian-style/SKILL.md; minor gaps are that references are backtick paths rather than clickable links and the inline notification template is somewhat lengthy.

4 / 5

Total

15

/

20

Passed

Description

75%Weight 40%Scale 1-5

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 highly specific and distinct, naming concrete actions, tools, and project-specific rules, but it omits an explicit 'Use when...' trigger clause, leaving the invocation condition only implied.

Suggestions

Append an explicit trigger clause such as 'Use when the user asks to backfill missing daily work logs or invokes /daily' to satisfy the 'when' half of completeness.

Add a couple of natural synonyms (e.g. '补齐日志', '缺日志') to broaden trigger-term coverage.

Optionally note the two invocation modes (no-arg scan vs. '/daily YYYY-MM-DD') in the description so users know both entry points.

DimensionReasoningScore

Specificity

Multiple concrete actions are named — '扫描并补齐缺失的每日工作日志', '对比 logs/daily/ 已有日志与 git 有提交的日期', '逐日调用 generate_log.py 生成骨架', '按 SKILL_10b 补写微信通知和改动意义' — with specific tools and the 07:00 boundary rule, giving comprehensive coverage.

5 / 5

Completeness

The 'what' is clear and detailed, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so 'when' is only weakly implied — capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Natural terms a user would say are present ('每日工作日志', '补齐缺失', 'git commit', '微信通知'), giving good keyword coverage, though synonym/extension variety is limited.

4 / 5

Distinctiveness Conflict Risk

A very specific niche tied to concrete project artifacts (generate_log.py, SKILL_10b, 07:00 boundary, 史记知识库) gives a clear trigger surface with minimal conflict risk.

5 / 5

Total

17

/

20

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.

Validation — 16 / 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.