deepnote
Use when a task mentions Deepnote, the connected Deepnote app, Deepnote OAuth connection, Deepnote docs, projects, workspaces, notebooks, blocks, integrations, or notebook runs.
- License 许可
- MIT
- 最近更新
- 2026-07-19
- Stars
- ★ 1
- Forks
- 1
01 前言 Front Matter
- name
- deepnote
- description
- Use when a task mentions Deepnote, the connected Deepnote app, Deepnote OAuth connection, Deepnote docs, projects, workspaces, notebooks, blocks, integrations, or notebook runs.
02 资源文件 1
- 参考文档references/workspace-summary.md5.9 KB
03 SKILL.md 正文
Deepnote Router
Use the connected Deepnote app tools as the source of truth for hosted Deepnote state. Prefer them over browser automation, screenshots, ad hoc HTTP calls, or local filesystem guesses for Deepnote projects, notebooks, blocks, integrations, docs, or runs.
If the Deepnote app tools are unavailable, say so and ask the user to connect the Deepnote app with OAuth. Do not pretend to have inspected Deepnote state.
When the user asks what Deepnote can do, start with:
Deepnote can identify the current workspace, search resources, list projects and integrations, inspect notebooks, create and edit notebook structure, map integration usage and cached table structure, read Deepnote docs, run notebooks, and fetch run status and history.
Capability Map
Use the current tool surface only; if a required tool is absent, say which capability is missing.
- Identity and discovery:
get_me,search,list_projects. - Notebook inspection:
get_notebook. - Notebook editing:
create_project,create_notebook,create_block,update_block,reorder_notebook_blocks. - Integrations:
list_integrations,get_integration,list_integration_project_usages,list_integration_notebook_usages,list_integration_block_usages. - Execution:
create_run,list_notebook_runs,get_run. - Docs:
list_docs,get_doc.
Route By Intent
| User asks for | Use |
|---|---|
| Workspace overview, heartbeat, active/scheduled notebooks, broad inventory | get_me, list_projects, list_integrations, and references/workspace-summary.md |
| Notebook contents, inputs, SQL, blocks, outputs, review, or explanation | deepnote-notebooks |
| Project/notebook creation, adding cells, updating cells, moving/reordering cells, scaffolded notebook content | deepnote-notebook-editing |
| Notebook execution, run status, recent/failed runs, run history, snapshots, integration usage, cached tables/columns | deepnote-data-execution |
| Project, notebook, workspace, or share links | deepnote-links |
| Product docs or how-to questions | list_docs, then get_doc |
Routing Defaults
- Resolve ambiguous names and IDs with
search,list_projects, orlist_integrations. - Use
get_mewhen workspace identity, connected user, caller role, or OAuth context matters. - Read with
get_notebookbefore reasoning about notebook blocks, inputs, latest run metadata, or before editing notebook structure. - Use
get_integrationfor cached table, schema, column, or table-existence questions about an integration. - Use
list_notebook_runsfor run history or failed-run searches; useget_runfor one selected run's status, errors, or snapshot. - Use specialist skills for any workflow with detailed rules. Keep this skill as the router.
Global Guardrails
- Never expose tokens, secret values, raw credentials, or sensitive integration metadata. Refer to secret names only.
- Treat project creation, notebook creation, block creation, block updates, block reordering, and notebook runs as persistent or stateful actions. Resolve targets carefully and report affected IDs.
- Do not run a notebook unless the user asks for execution, clearly needs fresh results, or confirms a creation workflow's final run prompt. Creation workflows may ask whether to run the newly created notebook, but must not run it preemptively. Run input overrides apply only to that run.
- Do not expose
snapshotDownloadUrlvalues unless the user asks for a download/file handoff; use inline snapshots only when output or error details are needed. - Use cached integration structure when available, but do not claim a fresh live database scan, row preview, single-block execution, environment mutation, permission change, publishing change, or scheduling change unless a current app tool exposes it.
- Keep responses brief and grounded in Deepnote object names, IDs, statuses, and links when available.
04 同仓库更多 Skills
Zotero
Use Zotero Desktop from Codex to enable/probe the local API, search a local Zotero library, list items/collections/tags, export BibTeX, insert citation keys into LaTeX or Markdown drafts, read indexed full text when requested, and import BibTeX/RIS records into Zotero through the connector server. Use when the user mentions Zotero, citations, references.bib, BibTeX export, local Zotero API, localhost:23119, or adding citations from a Zotero library.
zoom-apps-sdk
Use when using Apps SDK.
youtube
Obtain accurate, timestamped YouTube video transcripts (preferring manual captions over auto-generated) as the primary deliverable, then derive summaries, key claims, or notes from that transcript. Use when the user provides a YouTube URL (or video ID) and wants the transcript, a faithful summary, key claims with attribution, timestamped notes, or "what does this video actually say". The skill is transcript-first: never substitute metadata, title, description, or search snippets for the spoken content. Triggers: "youtube transcript", "get the transcript of this video", "summarize this youtube video", "what did they say in https://youtube.com/...", "key claims from this talk".
yeet
Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.
x-post-creator
Create X-ready post threads and co-located story packages from the active conversation or referenced project material. Use when the user says turn this into an X-post, /x-post, make this into an X thread, or wants plain-language social posts with supporting images saved to docs/x-posts/[story-name]/.
x-api
Search, read, and write X posts through the local X API MCP server (the same backend used by the Codex x-api skill). Use for searching X/x.com, reading threads and replies, creating lists, staging/publishing posts for @alltheputs, finding high-visibility reply targets for research outreach, ingesting public context, or any request that mentions /x-api or "search X".