Zero TiDB(Deprecated)

Create ephemeral TiDB Cloud Zero databases for agent workflows in Technical Preview.

What to check before installing: - Provenance: The skill's source/homepage is unknown and the skill name includes "(Deprecated)" — verify who published it and whether this is an official TiDB/PingCAP offering before trusting it. - Runtime dependencies: SKILL.md examples use curl, jq, the mysql CLI and Node's mysql2, but the skill metadata lists no required binaries. Ensure those tools are available in the agent environment or the instructions will fail. Consider asking the publisher to list explicit runtime dependencies. - API safety: The guide implies provisioning via POST to https://zero.tidbapi.com without any auth. Confirm the API's access controls and rate limits with the provider — unauthenticated provisioning can be abused and may expose you to unexpected costs or resource creation. - Secrets handling: The API returns DB credentials; the skill explicitly tells the agent to write them to a local file. Ensure the agent environment is sandboxed, that files are stored securely, and that the agent is not allowed to exfiltrate files to untrusted endpoints. - Test manually first: Run the documented curl commands yourself from a controlled environment to confirm behavior and inspect the response shape and expiration policy. If you cannot verify the publisher or the API behavior, or you do not want the agent to make external network calls, do not install or do not grant network access/autonomous invocation. If you proceed, ask the skill author to correct metadata (declare required binaries) and provide an official documentation link or contact.

Type: OpenClaw Skill Name: zero Version: 1.0.1 The skill's primary purpose is to provision TiDB Cloud Zero databases, which involves making API calls and providing connection details. However, the `SKILL.md` file contains instructions for the agent to execute `mysql` commands where the connection string, obtained directly from an external API response (`zero.tidbapi.com`), is interpolated into a shell command. This pattern (`mysql "<connectionString>"`) presents a shell injection vulnerability (RCE risk) if the `connectionString` returned by the API were maliciously crafted, even though the skill author's intent is to connect to their own provisioned database. This risky capability, despite lacking clear malicious intent from the skill author, warrants a 'suspicious' classification due to the potential for remote code execution via a compromised API endpoint.