Surrealdb
CheckedSurrealdb allows you to query and manipulate data across multiple databases seamlessly, boosting efficiency for complex applications.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add 24601/surreal-skills --skill surrealdb -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
24601
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned 24601/surreal-skills at 4e66534bc9.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 4e66534bc9
- Scanned
- 1 file, 103 lines
About this skill
The surrealdb skill provides AI agents with direct access to SurrealDB, a scalable, polyglot database engine. It enables agents to perform complex queries, manage data schemas, and execute transactions across various deployment environments like Docker or cloud instances. This integration allows for seamless interaction with graph, document, key-value, and time-series data structures within a single unified system.
When to use it
- Dynamic Data Storage: When an agent needs to persist unstructured or semi-structured data from user interactions in real-time.
- Complex Relationships: For applications requiring graph-like queries to navigate relationships between entities without external mapping layers.
- Multi-Tenant Applications: When deploying agents that need to isolate and manage distinct datasets for different users or organizations efficiently.
- Schema Evolution: In scenarios where data models change frequently, requiring a database that supports flexible schema updates without downtime.
Key capabilities
- Connects to SurrealDB instances via standard drivers (Docker, Cloud, etc.)
- Executes SQL-like queries against polyglot data types
- Manages user authentication and role-based access control
- Supports live subscriptions for real-time data updates
- Handles complex transactions with automatic conflict resolution
Example prompts
- "Create a new table called
userswith fields for name, email, and an array of hobbies." - "Insert a record into the
projectstable and retrieve all related tasks using a graph query." - "Update the status of all active sessions in the database to 'completed' based on the current timestamp."
Tips & gotchas
Ensure your AI agent has valid credentials (username/password or API keys) configured before attempting to connect to a remote SurrealDB instance. While SurrealDB supports many data types, complex nested queries may require specific syntax adjustments compared to traditional relational databases.