BF surrealdb
Expert SurrealDB 3 architect and developer skill (tracks v3.1.4+). SurrealQL mastery, multi-model data modeling (document, graph, vector, time-series, geospatial), schema design, security, deployment, performance tuning, SDK integration (JS, Python, Go, Rust, Java, .NET, C, PHP, Swift, Kotlin, Ruby), Surrealism WASM extensions, SurrealML scope coverage (preview), built-in MCP (v3.1+) and standalone SurrealMCP, LangChain Python integration, editor tooling (LSP v0.1.6, tree-sitter, CodeMirror v1.0.6, VS Code/JetBrains/Neovim/Zed), and ecosystem integrations (Surrealist v3.9, Surreal-Sync, SurrealFS, SurrealKit v0.7, n8n, Agent Skills, setup-surreal). Universal skill for 30+ AI agents.
As a process F 56/100 · Will not run — References files that are not bundled: {baseDir}/AGENTS.md
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.
The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 6
✓ No critical or high findings
Medium and low: 6
-
medium Secrets in code
secret-private-keyrules/security.md:642Private key material (key header without key body; quoted — discussed, not commanded)WITH ISSUER KEY '-----BEGIN PRIVATE KEY----- …
header onlyquoted -
medium Secrets in code
secret-private-keyrules/security.md:890Private key material (key header without key body; quoted — discussed, not commanded)WITH ISSUER KEY '-----BEGIN PRIVATE KEY----- …
header onlyquoted -
low Dangerous commands
cmd-pipe-to-shellCHANGELOG.md:3086Downloads and executes remote code from an unrecognised host (pipe to shell) (negated — the text forbids it)- **No regression to declared security posture.** All v1.4.0 changes are documentation-only -- no new scripts, no new binaries vendored, no new third-party network endpoints called by the skill itself
negated -
low Dangerous commands
cmd-pipe-to-shellrules/gotchas.md:115Downloads and executes remote code from an unrecognised host (pipe to shell) (documentation table row; documentation of a security skill)| `curl \| sh` installers | Supply-chain risk in audited environments | Prefer brew, apt, Docker, or `surreal upgrade` |
tablesecurity skill -
low Secrets in code
secret-private-keyrules/surrealql.md:554Private key material (placeholder value)WITH ISSUER KEY '-----BEGIN PRIVATE KEY----- …
placeholder
A further 1 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 38. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: {baseDir}/AGENTS.md - note
frontmatter-keyunknown frontmatter key "requires" - note
frontmatter-keyunknown frontmatter key "security"
Process rating: all ten parameters 56/100
- 0Tools and files. 1 referenced file(s) missing: {baseDir}/AGENTS.md
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 18 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4304 tokens
- 100Steps. 16 steps
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- -2localhost URLs: will not work for another user
- -31 of 5 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 691: enough signal without eating the budget
- +4Structure: 32 headings
- +3Step-by-step instructions: 16 items
- +3Output format is stated explicitly
- +4Has examples (9 code blocks)
- +4Reference files are cited in the instructions (19 of 21)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.