CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

surreal-data

Discordlancer's SurrealDB conventions - the schema, the append-only history tables, record IDs, money, transactions, connecting and testing. Use whenever work touches src/db/, schema.surql, queries, tables, fields, indexes, events, stages stored in the database, or database tests, even if the user only says "save this", "record it", "add a field" or "the database".

Quality

92%

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

86%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.

The body is a dense, high-signal conventions document: nearly every line records a hard-won, project-specific fact with exact identifiers, SurrealQL syntax, and commands, and it covers destructive-operation safety (append-only guards, parameter binding, cancelable cloud tests) well. The only deductions are time-sensitive version/date details outside a deprecated section and an implicit rather than explicit test-verification checkpoint in the schema-change workflow.

DimensionReasoningScore

Conciseness

The body is lean and almost every line is a non-obvious, project-specific fact (the db.close() hang, FLEXIBLE-after-TYPE parse order, no-op updates not firing events) that earns its place. However, time-sensitive details — "The SDK must be 2.2.1 or later", "@surrealdb/node 3.2.0 or later", "This was proven on 9 Nov" — sit outside any deprecated/old-patterns section, which the rubric penalizes, keeping it below anchor 5.

4 / 5

Actionability

Guidance is fully concrete and executable: a copy-paste-ready SurrealQL guard ("DEFINE EVENT OVERWRITE append_only ON <table> WHEN $event IN [\"UPDATE\", \"DELETE\"] THEN { THROW \"...\" }"), exact JS ("new RecordId('project', name)"), named helpers (closeDatabase, recordEvent, safeRecord, memoryDb), exact transaction syntax, and commands like "npm run db:migrate". Specific examples cover the common cases, matching anchor 5.

5 / 5

Workflow Clarity

"Adding a table or field: 1. Change schema.surql. 2. Add a test in test/db/schema.test.ts. 3. Update the data model in PLAN.md" is a clear sequence with validation embedded (a required test step, "A test checks this" for stage parity, idempotent OVERWRITE schema, CANCEL TRANSACTION for cloud tests). It falls short of anchor 5 only because the run-tests-and-verify loop for schema changes is implicit rather than an explicit checkpoint with error recovery.

4 / 5

Progressive Disclosure

This is a lean single-file skill (no bundle files exist) with well-organized sections — Connecting, Schema, Append-only history, Records and values, Queries, Tests — and no inlined bulk content. External pointers ("Read the vendor skills surrealdb-js and surrealql", "described in PLAN.md") are one level deep and clearly signaled, fitting the simple-skill exception for anchor 5.

5 / 5

Total

18

/

20

Passed

Description

95%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.

The description is exemplary: it states a concrete, project-specific scope, and its 'Use whenever' clause is unusually thorough, covering file paths, schema artifacts, and the indirect phrases a user might use instead of naming the database. Its only weakness is that the 'what' is expressed as coverage topics rather than actions, which slightly limits specificity.

DimensionReasoningScore

Specificity

"the schema, the append-only history tables, record IDs, money, transactions, connecting and testing" enumerates seven concrete coverage areas with no vague filler. It falls short of anchor 5 because these are topic nouns rather than concrete actions (no verbs like 'extract' or 'define'), and above anchor 3 because coverage clearly exceeds 1-2 items.

4 / 5

Completeness

A clear 'what' ("SurrealDB conventions - the schema, the append-only history tables, record IDs, money, transactions, connecting and testing") is paired with an explicit "Use whenever work touches..." clause listing concrete trigger phrases, including indirect user speech like "save this". This explicitly answers both what and when, matching anchor 5.

5 / 5

Trigger Term Quality

"src/db/, schema.surql, queries, tables, fields, indexes, events, stages stored in the database, or database tests, even if the user only says 'save this', 'record it', 'add a field' or 'the database'" covers file paths, technical terms, and the natural colloquial phrases a user would actually say. This matches anchor 5's comprehensive coverage including synonyms and file extensions.

5 / 5

Distinctiveness Conflict Risk

"Discordlancer's SurrealDB conventions" anchored to project-specific triggers (src/db/, schema.surql, the history tables) carves out a clear niche with minimal conflict risk against generic database skills. Matches anchor 5's 'clear niche with distinct triggers'.

5 / 5

Total

19

/

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/surreal-data/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.