CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

surrealdb-js

Using SurrealDB from JavaScript and TypeScript with the official surrealdb SDK, covering connecting (WebSocket/HTTP and embedded engines), authentication, CRUD, parameterized queries, and live queries. Use when connecting to SurrealDB from Node, Deno, Bun, or the browser, using the surrealdb npm package, or performing CRUD and real-time operations from JS/TS code. Triggers: surrealdb JS, surrealdb.js, new Surreal(), db.query, db.create, db.live, TypeScript SDK, npm i surrealdb.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

87%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Excellent token efficiency and actionability with exemplary progressive disclosure — real, well-organized one-level-deep reference files. The one substantive weakness is workflow clarity around destructive/batch operations: a whole-table `db.delete("person")` and bulk `db.insert` are demonstrated without any caution, error-handling, or verification checkpoint, which the rubric caps at 3 for database skills.

Suggestions

Add an explicit warning next to `db.delete("person")` that it deletes every record in the table, and show how to scope deletes to a specific RecordId or a WHERE clause as a safety checkpoint.

Include a brief verification pattern after bulk operations (e.g., `const count = await db.query<[number]>("SELECT count() FROM person GROUP ALL")`) so batch inserts/updates can be confirmed.

Show basic error handling around the connect/signin sequence (try/catch or a check that signin succeeded before running queries) to add a validation checkpoint to the main workflow.

DimensionReasoningScore

Conciseness

The body is lean and code-first: it never explains what SurrealDB is or how libraries work, and every line is either executable guidance ("Always pass user input via bound parameters, never string interpolation") or a tight code example. Every token earns its place.

5 / 5

Actionability

All snippets are copy-paste-ready TypeScript covering the common cases: full connect/use/signin/close flow, all CRUD variants with RecordId, parameterized db.query, and a live-query subscription with kill. This matches the 'fully executable, covers common cases' top anchor.

5 / 5

Workflow Clarity

The connect sequence is explicit and the injection-safety rule is stated, but destructive and batch database operations are shown with no validation, warning, or verification: `await db.delete("person")` deletes an entire table and `db.insert` bulk-inserts with no checkpoint. The rubric explicitly caps workflow clarity at 3 for database operations missing validation/verification steps.

3 / 5

Progressive Disclosure

The SKILL.md is a clear overview with well-signaled, one-level-deep references: in-body pointers ("See [references/embedded.md]", "See [references/live-queries.md]") plus an annotated References section; all three bundle files exist, are substantive, and contain no nested references.

5 / 5

Total

18

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person, concrete, and comprehensive, with an explicit 'Use when...' clause and an unusually rich trigger list covering package name, runtimes, and API calls. No vague or padded language is present.

DimensionReasoningScore

Specificity

The description lists multiple concrete capability areas — "connecting (WebSocket/HTTP and embedded engines), authentication, CRUD, parameterized queries, and live queries" — giving comprehensive coverage of the SDK's surface with no significant gaps, matching the top anchor rather than the 'minor gaps' level 4 anchor.

5 / 5

Completeness

It explicitly answers both what ("Using SurrealDB from JavaScript and TypeScript with the official surrealdb SDK, covering connecting... authentication, CRUD, parameterized queries, and live queries") and when ("Use when connecting to SurrealDB from Node, Deno, Bun, or the browser..."), followed by concrete trigger phrases — the level 5 example pattern.

5 / 5

Trigger Term Quality

Trigger terms are comprehensive and natural: "surrealdb JS, surrealdb.js, new Surreal(), db.query, db.create, db.live, TypeScript SDK, npm i surrealdb", plus runtime names ("Node, Deno, Bun, or the browser") and the npm package name — covering synonyms, API calls users would paste, and install commands.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — SurrealDB from JS/TS via the official SDK — with distinct triggers like "new Surreal()" and "db.live" that would not fire for any other skill, so conflict risk is minimal.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

boranfurkan/discordlancer

Path

.claude/skills/surrealdb-js/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.