CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deep-research-notebooklm

Deep research skill powered by NotebookLM MCP. Conducts structured multi-source research (market analysis, competitive intel, trend analysis, prospect research) using Google NotebookLM as the research engine, then delivers formatted briefs and optional studio artifacts (slides, audio podcasts, videos, infographics, reports, mind maps).

Quality

76%

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 ./cli-tool/components/skills/ai-research/deep-research-notebooklm/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, tool-specific workflow that is concrete and easy to follow end-to-end, with strong error-recovery detail around polling and status quirks. The dominant defect is the dangling research-brief-template.md reference — the primary deliverable's structure is undefined — plus minor redundancy in the Notes section.

Suggestions

Add research-brief-template.md to the bundle (or inline the brief structure in Step 7) so the primary deliverable is fully specified.

Delete or merge the Notes section, which repeats Step 4's fast/deep mode guidance and Step 1's scope-confirmation instruction.

Include one example research_start call with its query and mode arguments to make Step 4 copy-paste ready.

DimensionReasoningScore

Conciseness

The body is efficient: tables carry the research types and artifact parameters, tool names are given without explaining what MCP or research is, and every step earns its tokens. It misses level 5 because the "Notes" section largely duplicates earlier step content ("Fast mode is recommended as the default. Deep mode... can take 10+ minutes and occasionally stalls" restates Step 4; "Always confirm the research scope... before starting" restates Step 1).

4 / 5

Actionability

Highly actionable: exact MCP tool names (notebook_create, source_add, research_start, research_status, research_import, notebook_query, studio_create, studio_status, download_artifact), a notebook naming convention, a file-path convention, sample notebook_query questions, and concrete parameter tables with timings. Not level 5 because Step 7's core deliverable depends on "the template from [research-brief-template.md](research-brief-template.md)" which does not exist in the bundle, and no example research_start query arguments are shown.

4 / 5

Workflow Clarity

The 9 steps are clearly sequenced with named tools per step, polling checkpoints (research_status, studio_status), an error-recovery fallback ("Use the query parameter as fallback matching -- task IDs can change"), a status quirk workaround (check audio_url instead of waiting for "completed"), and a user-confirmation gate. It falls short of level 5 because Step 7 cannot be executed as written: the referenced research-brief-template.md is missing, so the brief structure is undefined at that checkpoint.

4 / 5

Progressive Disclosure

Inline structure is good (clear sections, tables, step headers), but scored against the actual bundle: no references/, scripts/, or assets/ directories exist, and the sole external reference, research-brief-template.md (linked twice), is not present. Navigation breaks at the point of use, leaving the reference clearly signaled but dangling, which fits the 'references present but organization incomplete' middle anchor rather than the level-4 'references mostly clear and working' anchor.

3 / 5

Total

15

/

20

Passed

Description

71%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 specific, concrete description that clearly states capabilities in third person with strong domain coverage. Its main weakness is the absent 'Use when...' trigger clause, which caps completeness and leaves activation conditions implied rather than explicit.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for deep research, market analysis, competitive intel, or prospect research on a topic."

Include natural synonym phrasings users would say, such as "competitor analysis", "due diligence", or "research a company".

Tighten the artifact list so the trigger phrase portion of the description leads rather than trails the capability list.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with comprehensive coverage: "Conducts structured multi-source research (market analysis, competitive intel, trend analysis, prospect research)", "delivers formatted briefs", and "optional studio artifacts (slides, audio podcasts, videos, infographics, reports, mind maps)". It enumerates both the research types and output artifact types exhaustively, matching the level-5 anchor rather than the level-4 'minor gaps' anchor.

5 / 5

Completeness

The "what" is clear and detailed (multi-source research via NotebookLM, briefs, studio artifacts), but there is no "Use when..." clause or equivalent explicit trigger guidance — the parenthetical research types only weakly imply when to use it. Per the guideline, a missing 'Use when...' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural-keyword coverage: "deep research", "market analysis", "competitive intel", "trend analysis", "prospect research", "podcasts", "infographics" are phrases users would naturally say. It falls short of level 5 because common variations like "competitor analysis", "due diligence", or "research a company/topic" are absent.

4 / 5

Distinctiveness Conflict Risk

"Deep research skill powered by NotebookLM MCP" carves out a clear niche tied to a specific engine, so overlap risk is low. It stops short of level 5 because "deep research" still overlaps generic research/web-search skills and no distinct trigger phrases separate it from those.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

davila7/claude-code-templates

Path

cli-tool/components/skills/ai-research/deep-research-notebooklm/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.