datadata-api
Query Datadata Sources
Teams need a safer way to inspect Datadata sources without building custom API calls. This skill provides guided CLI workflows for metadata, SQL execution, exports, and data-space table management.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "datadata-api" from https://skillstore.io/skills/datadata-team-datadata-api.md and its manifest at https://skillstore.io/api/skills/datadata-team-datadata-api/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "datadata-api". Search Datadata for customer datasources.
Expected outcome:
A numbered list of matching sources with names, owners, visibility, and source type for user confirmation.
Using "datadata-api". Run a sales summary query and fetch the result.
Expected outcome:
The execution ID, saved file path, format, byte count, row count, and suggested preview command.
Using "datadata-api". Create a products table in my ducklake data space.
Expected outcome:
A concise confirmation that the table was created, followed by the next safe insert or describe action.
Security Audit
High RiskThe skill is Datadata-focused and I found no prompt injection or hidden payloads. Most static alerts are false positives from markdown backticks, Chinese documentation, placeholders, and Datadata resource IDs. Confirmed issues involve authenticated network use, local credential storage, API key exposure in device-flow output, broad default permissions, and local result-file writes.
Confirmed security concerns (3)
Capability review items (46)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (36)
🌐 Network access (39)
📁 Filesystem access (19)
🔑 Env variables (130)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/datadata-team-datadata-api/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/datadata-team-datadata-api?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/datadata-team-datadata-api?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/datadata-team-datadata-api/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/datadata-team-datadata-api.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
datadata-team. (2026). datadata-api security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/datadata-team-datadata-api/audits/4BibTeX citation
@techreport{datadata-team-datadata-team-datadata-api-2026,
author = {datadata-team},
title = {datadata-api security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/datadata-team-datadata-api/audits/4},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "datadata-api security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "datadata-team"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/datadata-team-datadata-api/audits/4"
identifiers:
- type: other
value: "skillstore:datadata-team-datadata-api:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Explore a New Dataset
Inspect datasource metadata, list tables, and describe selected schemas before writing SQL.
Build an API Workflow
Generate a Datadata REST or CLI flow for queries, exports, and error handling.
Load Data Into a Space
Create ducklake tables, insert prepared rows, and verify the stored table schema.
Try These Prompts
Use Datadata to list tables for datasource <id>. Show table names, schemas, and the next safe step.
Describe table <table> in datasource <id> and explain the columns that matter for a simple query.
Run a read-only Datadata SQL query for <question>. Confirm datasource bindings and return the execution ID.
Create a ducklake data-space table for <dataset>, insert these rows, then describe the table after insertion.
Best Practices
- Confirm the selected datasource before running queries or write commands.
- Inspect datasource type, tables, and columns before writing SQL.
- Keep API keys in environment variables or local config, never in prompts.
Avoid
- Do not run drop or insert commands without explicit user approval.
- Do not load full NDJSON or CSV exports into model context.
- Do not send API keys to an unverified base URL or shared command log.