comprehensive-analysis

Deep-dive 7-day analysis across all data sources for weekly reviews, board prep, and strategic planning

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/comprehensive-analysis/SKILL.md

Quality

Content

70%

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

The skill delivers highly actionable, well-sequenced execution guidance with concrete commands and clear phases. Its weakness is organization: it is a monolithic single file that references non-bundled external files (daily-brief.md) and inlines large reusable agent prompts instead of separating them.

Suggestions

Move the large per-agent prompt blocks into separate bundled files (e.g., scripts/github-deep.md) referenced one level deep, instead of inlining all five prompts in SKILL.md.

Bundle or inline the '23 cross-reference patterns from the daily brief' rather than referencing an external daily-brief.md that is not in the bundle, to avoid a broken/deep reference.

Trim the DEEP ANALYSIS bullet lists to the highest-signal items to reduce token weight while preserving actionability.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands and structured agent prompts, but the verbose DEEP ANALYSIS bullet lists and restated 'same as daily brief' explanations add length that could be tightened; it respects Claude's competence only partially.	2 / 3
Actionability	Each agent prompt includes specific, executable commands (gh pr list, gh api stats/contributors, HogQL queries, ToolSearch loads) plus concrete analysis steps, making the guidance copy-paste ready and actionable.	3 / 3
Workflow Clarity	A clear three-phase sequence (Collection → Synthesis → Output) with parallel agent launching, explicit context-overflow protection/error handling checkpoints, and defined output documents; feedback loops and validation are present.	3 / 3
Progressive Disclosure	This is a single monolithic SKILL.md with no bundle files; references like 'see daily-brief.md' and '[CUSTOMIZE: path/to/briefs/]' point to external files that are not bundled, and large agent prompt blocks that could be separate scripts are inlined, giving poor file-level organization.	1 / 3
	Total	9 / 12 Passed

Description

60%

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 action-oriented, naming the analysis scope and target outputs in proper third person. It is missing an explicit 'Use when...' trigger clause and uses broad use-case terms that risk overlap with sibling briefing skills.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks for a weekly review, board prep, strategic planning, or a deep-dive across all data sources for a 7+ day period.'

Sharpen distinctiveness by contrasting with the daily brief, e.g. 'Use for 7+ day deep dives (not daily intel — use /daily-brief for that).'

Include natural user phrasings like 'comprehensive review', 'retro prep', or 'monthly/quarterly health check' as trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Deep-dive 7-day analysis across all data sources' plus the named outputs 'weekly reviews, board prep, and strategic planning' — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	It states what the skill does (deep-dive 7-day analysis) but the 'when' is only implied through use-case nouns; there is no explicit 'Use when...' clause, which the guidelines cap at 2.	2 / 3
Trigger Term Quality	Includes relevant natural phrases a user might say ('weekly reviews', 'board prep', 'strategic planning', 'deep dive') but omits common variations and explicit command-style triggers; coverage is decent but incomplete.	2 / 3
Distinctiveness Conflict Risk	The '7-day across all data sources' framing is a niche but 'weekly reviews, board prep, strategic planning' is broad enough to overlap with a daily-brief or team-brief skill, so it could conflict with similar skills.	2 / 3
	Total	9 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: huytieu/COG-second-brain
Path: .claude/skills/comprehensive-analysis/SKILL.md
Commit: dfbf9e9

Reviewed: 2 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.