deepnote-data-execution Skill
Use when running Deepnote notebooks, inspecting notebook inputs, reviewing integration references and cached table structure, listing run history, or interpreting run status and snapshot outputs through the Deepnote app tools. Published by openai in plugins.
Decision snapshot
Is this a fit?
Data analysis, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
18 days ago
No specific cautions were detected. Review the source and requested permissions before installing.
What is deepnote-data-execution Skill?
Use when running Deepnote notebooks, inspecting notebook inputs, reviewing integration references and cached table structure, listing run history, or interpreting run status and snapshot outputs through the Deepnote app tools. Published by openai in plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Data analysis
- Data analysis use cases
Declared skill metadata
- Source file: plugins/deepnote/skills/deepnote-data-execution/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use deepnote-data-execution Skill
- Use it for data analysis.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/plugins
- Skill file: plugins/deepnote/skills/deepnote-data-execution/SKILL.md
What it does
Use when running Deepnote notebooks, inspecting notebook inputs, reviewing integration references and cached table structure, listing run history, or interpreting run status and snapshot outputs through the Deepnote app tools.
Skill instructions
Deepnote Data And Execution Available Context Use the connected Deepnote app tools for the execution and context they currently expose: - getnotebook for notebook blocks, input variables, last-run metadata, and integration references visible in blocks. - listintegrations for workspace integration names and types. - getintegration for integration details and cached table structure, optionally filtered by databaseName, schemaName, or exact tableName. - listintegrationprojectusages, listintegrationnotebookusages, and listintegrationblockusages for direct integration usage mapping. - createrun to start full-notebook execution, optionally with input values. - listnotebookruns for historical notebook runs, newest first, with pageSize and pageToken pagination. - getrun for run status, errors, completion time, and run snapshots. When snapshotDelivery is omitted, it returns a short-lived snapshotDownloadUrl when a snapshot is available; this is equivalent to snapshotDelivery: "downloadUrl". Req
Verified compatibility and discovery
Frequently asked questions
What is deepnote-data-execution?
deepnote-data-execution is a open-source AI agent skill with Copy skill directory. Use when running Deepnote notebooks, inspecting notebook inputs, reviewing integration references and cached table structure, listing run history, or interpreting run status and snapshot outputs.
Who is deepnote-data-execution best for?
deepnote-data-execution is best for reusing agent instructions, scripts, and references, data analysis workflows.
How do I install deepnote-data-execution?
Install or run deepnote-data-execution using Copy skill directory. Check deepnote-data-execution for the latest setup command.
Is deepnote-data-execution actively maintained?
deepnote-data-execution may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
