AB notebooklm-ops
Operate Google NotebookLM MCP authentication lifecycle on Linux host. Use for NotebookLM MCP (`notebooklm-mcp` via `mcporter`) when cookies expire frequently and auth must be refreshed often. Handles on/off, auth refresh, status, and smoke test. Triggers: "Включи NotebookLM", "Выключи NotebookLM", "обнови авторизацию NotebookLM", "проверь NotebookLM".
Operate Google NotebookLM MCP authentication lifecycle on Linux host.
As a process B 68/100 · Nearly there — weak spots: result and completion, when it triggers
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 68/100
- 0Result and completion. Does not say what the result is
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 21 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 554 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 353: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 21 items
- +4Has examples (4 code blocks)
- +3All 4 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.