Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

notebooklm-skills

Transform files and folders into learning materials using NotebookLM. Actions: transform, convert, generate, create from files. Outputs: audio podcast, video explainer, slide deck, study guide, quiz, flashcards, infographic, mind map, briefing doc, report. Sources: PDF, text files, URLs, folders, subfolders. Features: batch processing, watermark removal, progress tracking, configurable granularity.

In Manus ausführen

Überblick

Installationsbefehl

npx skills add https://github.com/SutanuNandigrami/claude-titan-setup --skill notebooklm-skills

Kopieren Sie diesen Befehl und fügen Sie ihn in Claude Code ein, um den Skill zu installieren

Quelle

SutanuNandigrami/claude-titan-setup

Sterne9

Forks2

Aktualisiert19. März 2026 um 11:44

SKILL.md

readonly

name	notebooklm-skills
description	Transform files and folders into learning materials using NotebookLM. Actions: transform, convert, generate, create from files. Outputs: audio podcast, video explainer, slide deck, study guide, quiz, flashcards, infographic, mind map, briefing doc, report. Sources: PDF, text files, URLs, folders, subfolders. Features: batch processing, watermark removal, progress tracking, configurable granularity.
paths	*/.notebook-decks,/notebooks/,*/.ipynb,*/notebooklm

Notebook Decks

Transform user files and folders into rich learning materials (podcasts, videos, slide decks, quizzes, etc.) using the NotebookLM MCP, with automatic watermark removal for slide decks.

Rules (apply to ALL phases)

MCP Only: Use notebooklm-mcp MCP tool calls for ALL NotebookLM operations. NEVER use nlm CLI via Bash (except nlm login for auth). NEVER create automation script files (.js, .py, .sh, .bat).
No Skipping: Every question in every phase must be asked and answered before proceeding. Do not assume defaults.
State First: State files (.notebook-decks-meta.json, tasks.md, generation-config.jsonl) must be written to disk before any notebook_create call.

Start Here

Check if .notebook-decks-meta.json exists in the project root, then follow the appropriate path:

Path A: Fresh Start (no state file)

Read phases/01-configure.md — collect all user configuration (8 steps)
When Phase 1 complete, read phases/02-confirm.md — save state files and get user confirmation
When Phase 2 complete, read phases/03-process.md — process batches

Path B: Resume (state exists with incomplete batches)

Read phases/03-process.md directly. Resume from the first batch with status != "downloaded" or "cleaned".

Path C: Complete (all batches done)

Tell user: "All N batches were completed. Start a new session (clear state) or modify configuration?"

IMPORTANT: Read ONE phase file at a time. Complete ALL steps before reading the next. This skill controls routing — phase files do NOT chain to each other.

Mehr aus diesem Repository

gleiches Repository

cli-tools

SutanuNandigrami/claude-titan-setup

Reference for 100+ installed CLI tools. Use when working with any CLI tool, searching files, processing data, managing containers, infrastructure, security scanning, or system monitoring.

2026-03-229

security-scan

SutanuNandigrami/claude-titan-setup

Security scanning and vulnerability assessment workflows. Use when performing security audits, scanning for vulnerabilities, checking dependencies, or hardening systems.

2026-03-229

add-cli-tool

SutanuNandigrami/claude-titan-setup

Add a new CLI tool to the titan setup and make it usable immediately. Use when installing a new CLI tool, registering a tool in the setup script, updating the tool inventory, or when the user says "add tool", "new CLI tool", "register tool", "install X to titan". Also triggers on "I installed X", "add X to the setup", or any request to add a CLI tool to the workstation.

2026-03-199

docker-security

SutanuNandigrami/claude-titan-setup

Container hardening, image security, and Docker best practices. Use when building, scanning, or securing containers and images.

2026-03-199

git-workflow

SutanuNandigrami/claude-titan-setup

Git branching, commit, and PR conventions. Use when creating branches, making commits, or opening PRs.

2026-03-199

infra-deploy

SutanuNandigrami/claude-titan-setup

Infrastructure as Code workflows with Terraform, Ansible, Docker, and Kubernetes. Use when provisioning, configuring, deploying, or managing infrastructure.

2026-03-199

Quelle

SutanuNandigrami

SutanuNandigrami/claude-titan-setup

GitHub-Repository öffnen Creator-Repositorys ansehen

Installationsbefehl

Download

In Manus ausführen

Nützlich fürSOC

SoftwareentwicklerInformatik- und Mathematikberufe15-1252L4

name	notebooklm-skills
description	Transform files and folders into learning materials using NotebookLM. Actions: transform, convert, generate, create from files. Outputs: audio podcast, video explainer, slide deck, study guide, quiz, flashcards, infographic, mind map, briefing doc, report. Sources: PDF, text files, URLs, folders, subfolders. Features: batch processing, watermark removal, progress tracking, configurable granularity.
paths	*/.notebook-decks,/notebooks/,*/.ipynb,*/notebooklm

Notebook Decks

Transform user files and folders into rich learning materials (podcasts, videos, slide decks, quizzes, etc.) using the NotebookLM MCP, with automatic watermark removal for slide decks.

Rules (apply to ALL phases)

MCP Only: Use notebooklm-mcp MCP tool calls for ALL NotebookLM operations. NEVER use nlm CLI via Bash (except nlm login for auth). NEVER create automation script files (.js, .py, .sh, .bat).
No Skipping: Every question in every phase must be asked and answered before proceeding. Do not assume defaults.
State First: State files (.notebook-decks-meta.json, tasks.md, generation-config.jsonl) must be written to disk before any notebook_create call.

Start Here

Check if .notebook-decks-meta.json exists in the project root, then follow the appropriate path:

Path A: Fresh Start (no state file)

Read phases/01-configure.md — collect all user configuration (8 steps)
When Phase 1 complete, read phases/02-confirm.md — save state files and get user confirmation
When Phase 2 complete, read phases/03-process.md — process batches

Path B: Resume (state exists with incomplete batches)

Read phases/03-process.md directly. Resume from the first batch with status != "downloaded" or "cleaned".

Path C: Complete (all batches done)

Tell user: "All N batches were completed. Start a new session (clear state) or modify configuration?"

IMPORTANT: Read ONE phase file at a time. Complete ALL steps before reading the next. This skill controls routing — phase files do NOT chain to each other.