nebari-dev

Convert documents and files to Markdown using markitdown. Use when converting PDF, Word (.docx), PowerPoint (.pptx), Excel (.xlsx, .xls), HTML, CSV, JSON, XML, images (with EXIF/OCR), audio (with transcription), ZIP archives, YouTube URLs, or EPubs to Markdown format for LLM processing or text analysis.

Allows to interact with web pages by performing actions such as clicking buttons, filling out forms, and navigating links. It works by remote controlling Google Chrome or Chromium browsers using the Chrome DevTools Protocol (CDP). When Claude needs to browse the web, it can use this skill to do so.

Use when a user asks Pi to build and deploy arbitrary web apps through JupyterHub named servers using direct Hub API calls (no nebari_app_* tools).

Use when Pi needs to troubleshoot logs/metrics/traces or verify LGTM (Grafana/Loki/Mimir/Tempo) access in local k3s, cloud Kubernetes, or any generic K8s setup.

House recipe for adding a new component to the nebari-design shadcn registry. Use when adding, creating, or scaffolding a registry component — e.g. "add a Button component to the registry", "create a new nebari component", "scaffold <X> in registry/nebari/ui", or "animate / add motion to a component". Covers the component file pattern (cva variants, data-slot/data-variant/data-size attributes, cn() merging, Base UI render-prop composition), the registry.json entry shape (dependencies vs registryDependencies), motion and animation (interaction states, overlay enter/exit, motion-safe gating, token usage), story and test templates, and the verification gate.

Add and use components from the Nebari design system (the @nebari shadcn registry) in this app. Use when asked to "add a nebari component", "use the nebari button/badge/alert/spinner", "install the nebari theme", "animate, add a transition, make it feel polished, or add an entrance animation with nebari", or "build <something> with nebari components". Covers registry setup (the @nebari namespace in components.json + the shadcn add command), the component catalog (variants, sizes, props), the Base UI render-prop composition convention, theming (the @nebari/theme tokens, CSS variables, and light/dark), and motion (duration/easing tokens, entrance animations, overlay transitions, accessibility guardrails).