CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pocketbase

Models PocketBase backends: collections, relations, auth, API rules, migrations, and architecture. Use when designing schema, security rules, data modeling, choosing between hooks vs client access, or explaining PocketBase platform concepts — not for npm JS SDK code or pb_hooks.

Quality

82%

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

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

A well-structured, mostly lean platform overview with genuinely useful PocketBase-specific guidance (rule semantics, access-pattern decisions, sibling-skill routing). Its main defects are a broken internal reference to a missing file and the absence of a concrete worked example for the core design tasks.

Suggestions

Fix the broken reference: the body links to [pockethost-hosting.md](pockethost-hosting.md) but no such file exists in the bundle — either add the hosting reference file or remove/correct the link.

Strengthen actionability with one worked example, e.g. a complete collection definition (fields plus create/update/delete rules) or a short JS migration snippet showing the common design flow end-to-end.

Trim generic lines that restate what Claude already knows ('Indexes improve filter/sort performance', 'JWT tokens identify authenticated requests') and either deepen the thin Realtime/Files sections or remove them.

DimensionReasoningScore

Conciseness

Mostly lean, table-driven content, but a few lines restate generic knowledge Claude already has ('Indexes improve filter/sort performance on large collections', 'JWT tokens identify authenticated requests') and the version-gated '(PB ≥0.37)' reference will age.

4 / 5

Actionability

Provides concrete executable guidance — a real rule expression ('@request.auth.id != "" && @request.auth.id = user.id'), exact semantics for null/empty-string rules, and specific directives ('use $app APIs directly') — but lacks a worked example such as a complete collection definition with create/update rules or a migration snippet.

4 / 5

Workflow Clarity

Decision paths are clearly structured (client access vs hooks vs server-side SDK) with a numbered sequence for privileged operations and an explicit checkpoint ('Superusers bypass rules, so test as real users'), though the schema-design and migration flows are not sequenced end-to-end.

4 / 5

Progressive Disclosure

Sections are well-organized with clear headers and a routing table, but the only internal reference ('see [pockethost-hosting.md](pockethost-hosting.md)') points to a file that does not exist anywhere in the bundle, leaving the one clearly-signaled deep link broken.

3 / 5

Total

15

/

20

Passed

Description

87%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 that explicitly states what it models and when to use it, reinforced by a negative boundary against sibling skills. Trigger coverage is good though not exhaustive, and capabilities are enumerated as domain objects under one verb rather than as distinct actions.

DimensionReasoningScore

Specificity

Names the domain and enumerates specific capability areas ('collections, relations, auth, API rules, migrations, and architecture'), but capabilities are presented as objects under a single verb ('Models') rather than multiple distinct concrete actions, so it falls just short of comprehensive.

4 / 5

Completeness

Clearly and explicitly answers both what ('Models PocketBase backends: collections, relations, auth, API rules, migrations, and architecture') and when ('Use when designing schema, security rules, data modeling, choosing between hooks vs client access, or explaining PocketBase platform concepts') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good coverage of natural terms ('PocketBase', 'designing schema', 'security rules', 'data modeling', 'choosing between hooks vs client access'), but a few natural variations users might say — 'filters', 'database design', 'record relations' — are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche with an explicit exclusion clause ('not for npm JS SDK code or pb_hooks') that distinguishes it from closely related sibling skills; minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

pockethost/pockethost

Path

.cursor/skills/pocketbase/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.