CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

weekly-rollup

Use when the work-journal app asks to roll up a week of daily journal entries into themes, time trends, outcomes, and a draft status update.

76

Quality

95%

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

The canonical home for this skill is weekly-rollup in chandler767/WorkJournal

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 an exemplary lean headless-skill spec: exact input format, exact output contract with a JSON schema, precise empty/edge-case behavior, and no filler. Nothing is missing that Claude would need to execute it correctly in one pass.

DimensionReasoningScore

Conciseness

Every line is a non-obvious constraint (read only the named file, 900-byte line-continuation rule, exact heading set, JSON-only reply, empty-input behavior) with zero concept explanations or padding — lean and every token earns its place.

5 / 5

Actionability

For an instruction-only skill the guidance is fully executable: exact headings and order ('## Themes', '## Time trends', '## Key outcomes', '## Draft status update'), explicit comparison semantics for totals vs prior_totals, defined empty-case output ('None.'), and a complete output JSON schema.

5 / 5

Workflow Clarity

A simple single-purpose skill under 50 lines whose single action is unambiguous: read the entire named input file (in offset/limit parts if long), then reply with one JSON object matching the schema. The simple-skill exception applies, and it is not a destructive or batch operation requiring validation checkpoints.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references, and no bundle files exist; its four well-organized sections (Rules, Input, skill-specific rules, Output schema) fully cover the task, so the no-references exception for a 5 applies.

5 / 5

Total

20

/

20

Passed

Description

88%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.

A strong description: third-person, concise, with an explicit 'Use when' trigger and a complete, concrete inventory of the skill's outputs. Its only weaknesses are a few missing natural trigger synonyms and slight overlap risk with generic summarization/status-update phrasing.

Suggestions

Add natural trigger variations users might say, e.g. '...or when the user asks for a weekly summary, recap, or digest of their journal entries'.

Sharpen distinctiveness by making the trigger unmistakably tied to the app context, e.g. 'Use when the work-journal app asks for a weekly rollup, weekly summary, or digest of daily entries' — reducing overlap with generic status-update skills.

DimensionReasoningScore

Specificity

The description names the domain ("work-journal app", "week of daily journal entries") and comprehensively lists the concrete outputs: "themes, time trends, outcomes, and a draft status update" — no coverage gaps within its niche, matching the comprehensive-coverage anchor rather than the minor-gaps anchor below it.

5 / 5

Completeness

Explicitly answers both: what ("roll up a week of daily journal entries into themes, time trends, outcomes, and a draft status update") and when ("Use when the work-journal app asks to roll up a week…") with concrete trigger phrases — a clear anchor-5 match; anchor 4 would require a weaker or less explicit 'when'.

5 / 5

Trigger Term Quality

Good natural keyword coverage ("roll up", "week", "journal entries", "status update") but missing common user variations like "weekly summary", "recap", or "digest". It fits the good-coverage-with-a-few-missing-terms anchor, not the comprehensive-synonyms anchor above.

4 / 5

Distinctiveness Conflict Risk

The "work-journal app" gating gives it a clear niche with minimal conflict risk, but generic-sounding deliverables ("themes", "outcomes", "status update") create minor overlap risk with general summarization or status-update-drafting skills. It sits between the mostly-distinct and clear-niche anchors, noticeably above the midpoint.

4 / 5

Total

18

/

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

chandler767/WorkJournal

Path

.tessl/plugins/local/work-journal/skills/weekly-rollup/SKILL.md

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.