CtrlK
BlogDocsLog inGet started
Tessl Logo

notebooklm

Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio/Video Overviews, Mind Maps, Reports incl. Briefing Doc/Study Guide/FAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 browser-automation skill with clear sequencing, explicit validation, and clean progressive disclosure into real bundle files. Its main weakness is repetition of the Studio inventory and the 'defaults are mediocre' point, which inflates token cost without adding information.

Suggestions

State the Studio output inventory once (in the Action 3 section) and have Q3 and the description reference it, instead of repeating the full list three times.

Consolidate the 'default Studio prompts produce mediocre output — always write custom' guidance into a single location (e.g., the custom-prompts reference) and link to it, rather than restating it in Q3, Q4, Action 3, and the anti-patterns.

Tighten the per-action 'Why I'm asking' rationales — they are useful for the grill-me pattern but several can be trimmed to one line without losing the forcing effect.

DimensionReasoningScore

Conciseness

Largely efficient operational guidance that earns its place, but the Studio inventory list recurs three times (description, Q3, Action 3) and the 'default prompts produce mediocre output' line is repeated across Q3, Q4, Action 3, and the anti-patterns — minor over-explanation that could be trimmed. Not a 5 because not every token earns its place; not a 3 because it does not explain concepts Claude already knows.

4 / 5

Actionability

Provides concrete executable guidance — exact UI sub-flows ('Add Source → Link → paste URL'), a copy-paste script call ('python3 scripts/async_action_classifier.py --action "video overview"'), and explicit output paths ('${WORKSPACE}/notebooklm/<notebook-slug>-<action>-<date>.md'). The tool-agnostic UI steps (semantic find(), screenshot) are necessarily abstract but justified; minor gaps keep it just below fully copy-paste ready.

4 / 5

Workflow Clarity

Clearly sequenced multi-step process with explicit validation checkpoints: mandatory Step 0 browser/login checks, dependency-ordered Q1–Q4 intake with a stop condition, per-action numbered workflows, screenshot-before-every-action discipline, and feedback loops (retry once on chat failure, re-ask Q1 on ambiguous input, error-handling table). The destructive/batch cap does not apply — this is interactive single-action automation.

5 / 5

Progressive Disclosure

Well-signaled one-level-deep references: a References section lists all three reference files with one-line descriptions, inline 'See references/... for the canon' pointers sit at the right moments, and a Tooling table maps the three scripts to roles. All referenced paths resolve to real files in references/ and scripts/. Easy navigation, content appropriately split.

5 / 5

Total

18

/

20

Passed

Description

100%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, third-person description that explicitly states both capabilities and trigger conditions with concrete example phrases. It is comprehensive and distinct without relying on vague fluff.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions across the full surface area — 'reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio/Video Overviews, Mind Maps, Reports incl. Briefing Doc/Study Guide/FAQ, Flashcards, Quiz, slide decks, infographics), and creating new notebooks' — matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers both 'what' (controls NotebookLM; handles the four action families) and 'when' ('Use when the user wants anything done in NotebookLM (e.g., ...)') with concrete trigger phrases, hitting the top anchor.

5 / 5

Trigger Term Quality

Embeds natural phrases a user would actually say — 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview', 'use NotebookLM Studio' — covering synonyms and product-specific terms comprehensively.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (browser automation of a single Google product) with product-distinct triggers ('ask my notebook about X', 'use NotebookLM Studio'), giving minimal overlap risk with other skills.

5 / 5

Total

20

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
alirezarezvani/claude-skills
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.