daily-report

Compile timestamped conversation logs, agent sessions, IM messages, collaborative documents, meeting notes, task records, and similar OpenViking materials into concise, evidence-grounded daily reports. Use with ov compile when the user asks for a daily work report, end-of-day digest, 日报, or reports for one or more dates, especially when activities must be reconstructed across heterogeneous sources without treating plans or agent suggestions as completed work.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

73%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 a well-structured, actionable instruction set with a clear phased workflow and an explicit validation gate. Its main weakness is redundancy across the Evidence rules, Workflow, and Quality gate sections, which hurts conciseness.

Suggestions

Consolidate the repeated "do not treat plans/agent claims as completed" and "do not report carrier metadata" rules so they appear once, then cross-reference from the Quality gate instead of restating them.

Add a short worked-example report (frontmatter plus one or two outcome-first bullets with nearby citations) to make the output format copy-paste concrete.

Consider moving the detailed Quality-gate checklist into a reference file and signaling it once, to reduce the main file's length and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and does not explain concepts Claude already knows, but the same rules (do not treat plans as completed; do not report carrier metadata) are restated across the Evidence rules, Workflow survey, and Quality gate sections, so it could be tightened.	3 / 5
Actionability	It provides concrete, executable guidance for an instruction-only skill: exact OKF frontmatter fields, a fixed section list, the `<YYYY-MM-DD>.md` filename pattern, and a date-resolution order; a worked example report would make it fully concrete.	4 / 5
Workflow Clarity	The workflow is clearly sequenced (Establish scope, Survey and reconstruct, Synthesize, Integrate) with an explicit Quality-gate checklist and an extraction-failed feedback loop that revises interpretation before drafting, so validation is present rather than missing.	5 / 5
Progressive Disclosure	The content is well-organized into clearly headed sections in a single self-contained file with no nested references, which is appropriate given no bundle files exist; the substantial length is the only minor gap keeping it from the top anchor.	4 / 5
	Total	16 / 20 Passed

Description

87%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 strong: it explicitly states both capability and trigger conditions with concrete, natural trigger phrases and a distinctive OpenViking niche. Its only weakness is that the capability is framed as a single compile action rather than a list of distinct operations.

Dimension	Reasoning	Score
Specificity	It names a concrete action ("Compile ... into ... daily reports") and comprehensively enumerates specific input material types (conversation logs, agent sessions, IM messages, meeting notes, task records), but it is essentially a single action rather than multiple distinct ones, so it falls just below the top anchor.	4 / 5
Completeness	It clearly answers what ("Compile ... materials into concise, evidence-grounded daily reports") and when ("Use with ov compile when the user asks for a daily work report, end-of-day digest, 日报...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	It includes natural phrases users would say ("daily work report", "end-of-day digest", "日报", "reports for one or more dates", "ov compile") with multilingual synonyms, but a few common variants are absent and there are no file-extension triggers relevant to this domain.	4 / 5
Distinctiveness Conflict Risk	The OpenViking-specific scope, the "ov compile" command, and the multilingual daily-report triggers carve a clear niche with minimal overlap risk against generic summarization skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

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: volcengine/OpenViking
Path: examples/compile/ov-compile-skills/daily-report/SKILL.md
Commit: b2f1f9d

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.