CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

daily-brief

Generate personalized news intelligence with verified sources (7-day freshness requirement)

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

62%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 delivers an exceptionally well-engineered workflow: deterministic verification, dedup logic, a retry loop with layered termination conditions, and a complete output template. Its weaknesses are token efficiency — three sections of aspirational metrics/philosophy padding plus a five-times-repeated template structure — and the absence of any bundle structure, with all ~500 lines inlined where a references/ split would keep the overview lean.

Suggestions

Cut the "Performance Metrics", "Learning and Adaptation", and "Philosophy" sections (or compress them to 2-3 lines each) — they state aspirations Claude cannot act on and add ~60 lines of context-load for no behavioral gain.

State the brief item structure once and note "repeat per section with the section-specific implications block" instead of spelling out the full structure five times across High Impact / Strategic / Market / Technology / Competitive sections.

Move the ~200-line brief template to references/brief-template.md and the source-tier methodology to references/verification.md, keeping SKILL.md as a lean overview with clearly signaled one-level-deep references — this would also let progressive_disclosure score higher.

DimensionReasoningScore

Conciseness

The ~500-line body contains several non-instructional padded sections — "Performance Metrics" ("Fact Accuracy Rate: Percentage of facts that remain accurate over time"), "Learning and Adaptation" ("Improve ability to predict news impact"), and "Philosophy" ("No AI hallucinations - everything sourced and verified") — that tell Claude nothing it can execute, and the output template repeats the same item structure five times across section types instead of stating it once. This matches anchor 2 ("noticeably verbose; several unnecessary explanations or padded sections") rather than anchor 3, where padding would be occasional rather than three full sections; the core process (dedup, verification tiers, loop termination) is genuinely dense and valuable, keeping it above anchor 1.

2 / 5

Actionability

The guidance is overwhelmingly concrete and executable: the exact command `date '+%Y-%m-%d %H:%M'`, explicit vault paths (`00-inbox/MY-INTERESTS.md`, `01-daily/briefs/`), a copy-paste-ready brief template with full frontmatter, precise dedup matching rules, and special-case templates for unverified/conflicting news. It falls just short of anchor 5 due to minor gaps: the "Budget guard: overall fetch budget across all areas" names no number, and a few bullets like "Diversify sources for balanced perspective" and "Identify emerging patterns" are abstract directives rather than executable steps.

4 / 5

Workflow Clarity

The process is clearly sequenced (pre-flight profile check → context gathering with prior-brief dedup scan → verified research loop → structured generation → special cases → completion confirmation) with explicit validation checkpoints: the required `date` command before any file creation, a deterministic per-candidate verifier (7-day date check, 2 independent sources, tier identification, dedup), and layered termination conditions including a no-progress fallback. This matches anchor 5 exactly — clear sequence, explicit validation, and feedback loops ("a failed search informs the next query", "A candidate that fails any check is discarded, not softened") for a batch research operation.

5 / 5

Progressive Disclosure

The body is well-organized with clear section headers, but everything lives inline in one ~500-line file with no bundle files present; the ~200-line output template and the verification-tier methodology are natural candidates for a references/ file that the SKILL.md could point to. This matches anchor 3 ("some structure but could be better organized; content that should be separate is inline") — above anchor 2 because navigation via headers is easy and the one cross-skill reference (`.claude/skills/loop-engineering/SKILL.md`) is clearly signaled at one level, but short of anchor 4 because the file is monolithic at this length.

3 / 5

Total

14

/

20

Passed

Description

46%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 communicates a clear, moderately specific purpose but omits any "when to use" guidance and carries almost no natural trigger terms — the phrases users actually say ("daily brief", "what's happening") live only in the body, so the description alone would rarely be matched to a request. It is distinct from other skills but reads more like a capability label than a triggerable description.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases, e.g., "Use when the user asks for their daily brief, morning news briefing, or what's happening in their interest areas."

Include the natural keywords users say — "daily brief", "news briefing", "what's happening" — directly in the description, not just in the body.

Name 1-2 more concrete actions to round out coverage, e.g., "...deduplicates against previous briefs and saves a dated briefing note to the vault."

DimensionReasoningScore

Specificity

The description "Generate personalized news intelligence with verified sources (7-day freshness requirement)" names the domain (news intelligence) and 1-2 concrete actions (generate personalized briefings, verify sources) with one specific constraint, but stops short of the comprehensive multi-action coverage of anchor 5 (e.g., it omits dedup against prior briefs, relevance analysis, or briefing-file generation). It is above anchor 2 because the actions are more than a bare domain label — 'verified sources' and the 7-day window are concrete, not generic.

3 / 5

Completeness

There is a clear "what" (generate personalized, verified news intelligence) but no "when"/"Use when..." clause or equivalent trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. It is not a 4 because the "when" is entirely absent rather than merely implicit; not a 2 because the "what" is clear and specific.

3 / 5

Trigger Term Quality

The only natural keyword a user might say is "news"; the phrases users would actually use — "daily brief", "briefing", "morning brief", "what's happening" — appear only in the body, not the description. This matches anchor 2 ("one or two generic keywords; missing the natural phrases users say") and falls well short of anchor 4's good keyword coverage with synonyms.

2 / 5

Distinctiveness Conflict Risk

"Personalized news intelligence with verified sources" carves out a recognizable niche (personal news briefing) with minor overlap risk against closely related skills (e.g., general web research or weekly-checkin). It is not a 5 because the description lacks distinct trigger phrases and "news intelligence" is abstract enough to overlap with broader research/summarization skills.

4 / 5

Total

12

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (506 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

huytieu/COG-second-brain

Path

.claude/skills/daily-brief/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.