CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cli-anything-notebooklm

Experimental NotebookLM harness for listing notebooks, managing sources, asking questions, generating artifacts, and downloading outputs through an installed notebooklm CLI.

Quality

75%

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 ./notebooklm/agent-harness/cli_anything/notebooklm/skills/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 lean, well-structured CLI-harness skill with executable install and usage commands and a sensible agent workflow. Its weaknesses are repeated --json/unofficial disclaimers and the lack of concrete example invocations for most command groups or error-recovery steps.

Suggestions

Consolidate the --json guidance into a single statement and merge the duplicated experimental/unofficial disclaimers into one line.

Add one concrete example invocation per command group (e.g. `source add <url>`, `artifact generate`, `download <id>`) instead of one-line purpose descriptions.

Include a brief error-recovery path, such as running `auth login` when `auth status` fails, to close the workflow validation gap.

DimensionReasoningScore

Conciseness

Mostly efficient, but the --json guidance is repeated three times ("# Prefer JSON for agent use", "Prefer --json only where the upstream notebooklm command supports it", "Use --json for machine-readable output only on commands that support it upstream") and the experimental/unofficial disclaimer appears twice, which could be tightened.

3 / 5

Actionability

Install and usage commands are concrete and executable, and workflow steps carry real commands, but the command groups (chat, artifact, download, share) get only one-line purposes with no example invocations, leaving minor gaps.

4 / 5

Workflow Clarity

The 4-step agent workflow is a clear, concrete sequence that opens with an explicit auth checkpoint ("cli-anything-notebooklm auth status"), but no error-recovery guidance exists for auth failure, a minor validation gap.

4 / 5

Progressive Disclosure

No bundle files exist, and the single-file body is well-organized into clearly labeled sections with an explicit References list of external URLs; the ~73-line body and un-expanded per-command detail keep it just short of the clean-overview ideal.

4 / 5

Total

15

/

20

Passed

Description

70%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, distinctive description that names five concrete capabilities in a niche domain. Its main weakness is the absence of any 'when to use' trigger clause and limited synonym coverage for common NotebookLM feature names.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions NotebookLM, wants to add sources to a notebook, or asks for audio overviews or other artifacts.'

Name concrete artifact types (e.g. audio overviews, mind maps, study guides) instead of the generic 'generating artifacts'.

Include natural synonyms such as 'chat with sources' or 'query notebooks' to broaden trigger term coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions ("listing notebooks, managing sources, asking questions, generating artifacts, and downloading outputs") but some are generic ("managing sources") and artifact types are unnamed, leaving minor gaps in coverage.

4 / 5

Completeness

The "what" is clearly stated via a list of concrete capabilities, but there is no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Good natural keyword coverage ("NotebookLM", "notebooks", "sources", "questions", "artifacts", "download"), but misses common user phrasings like "audio overview", "mind map", or "chat with sources".

4 / 5

Distinctiveness Conflict Risk

The description claims a clear niche ("NotebookLM harness ... through an installed notebooklm CLI") with distinct domain-specific triggers, so conflict with other skills is minimal.

5 / 5

Total

16

/

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

HKUDS/CLI-Anything

Path

notebooklm/agent-harness/cli_anything/notebooklm/skills/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.