nlm-skill

Gemini Notebook CLI & MCP Expert

This skill provides comprehensive guidance for using Gemini Notebook via both the nlm CLI and MCP tools.

Tool Detection (CRITICAL - Read First!)

ALWAYS check which tools are available before proceeding:

1. Check for MCP tools: Look for tools starting with mcp__gemini-notebook-mcp__* or mcp_gemini_notebook_mcp_*
2. If BOTH MCP tools AND CLI are available: ASK the user which they prefer to use before proceeding
3. If only MCP tools are available: Use them directly (refer to tool docstrings for parameters)
4. If only CLI is available: Use nlm CLI commands via Bash

Decision Logic:

has_mcp_tools = check_available_tools()  # Look for mcp__gemini-notebook-mcp__* or mcp_gemini_notebook_mcp_*
has_cli = check_bash_available()  # Can run nlm commands

if has_mcp_tools and has_cli:
    # ASK USER: "I can use either MCP tools or the nlm CLI. Which do you prefer?"
    user_preference = ask_user()
else if has_mcp_tools:
    # Use MCP tools directly
    mcp__gemini-notebook-mcp__notebook_list()
else:
    # Use CLI via Bash
    bash("nlm notebook list")

This skill documents BOTH approaches. Choose the appropriate one based on tool availability and user preference.

Quick Reference

Run nlm --ai to get comprehensive AI-optimized documentation - this provides a complete view of all CLI capabilities.

nlm --help              # List all commands
nlm <command> --help    # Help for specific command
nlm --ai                # Full AI-optimized documentation (RECOMMENDED)
nlm --version           # Check installed version

Critical Rules (Read First!)

1. Authenticate when needed: Run nlm login for first-time setup or confirmed stale/missing credentials. Saved cookies often remain usable for weeks.
2. Do not confuse network failures with expired auth: auth_status="unverified" means the probe was inconclusive. Check connectivity or try an API call before asking the user to log in again.
3. Auto-Authentication Recovery: The CLI includes automatic 3-layer auth recovery (CSRF refresh -> Token reload -> Headless Auth) and 3x server error retries. Most errors are handled automatically. You only need to manually run nlm login if all recovery layers fail.
4. ⚠️ ALWAYS ASK USER BEFORE DELETE: Before executing ANY delete command, ask the user for explicit confirmation. Deletions are irreversible. Show what will be deleted and warn about permanent data loss.
5. Always obtain approval before generation or deletion: Direct studio_create and delete operations enforce --confirm / confirm=True. The current MCP batch Studio path does not enforce its confirm parameter, so the agent must preserve the approval gate.
6. Research needs a destination: Pass --notebook-id <id> for an existing notebook or --title <title> to create one.
7. Capture IDs from output: Create/start commands return IDs needed for subsequent operations
8. Use aliases: Simplify long UUIDs with nlm alias set <name> <uuid>
9. Check aliases before creating: Run nlm alias list before creating a new alias to avoid conflicts with existing names.
10. DO NOT launch REPL: Never use nlm chat start - it opens an interactive REPL that AI tools cannot control. Use nlm notebook query for one-shot Q&A instead.
11. Choose output format wisely: Default output (no flags) is compact and token-efficient—use it for status checks. Use --quiet to capture IDs for piping. Only use --json when you need to parse specific fields programmatically.
12. Use --help when unsure: Run nlm <command> --help to see available options and flags for any command.
13. Studio: fast track by default: Infer format/style/prompt silently—one compact line, then studio_create(confirm=True). No intake questionnaires. Fast track reduces clarifying questions, not the confirm gate. Cinematic video is always guided (quota-limited). Full preview only when vague, high-stakes, cinematic, or user asks. See references/studio-prompting-guide.md.