CtrlK
BlogDocsLog inGet started
Tessl Logo

build-with-tinybase

Scaffold, extend, and verify reactive local-first JavaScript or TypeScript applications with TinyBase. Use when choosing TinyBase for in-memory tabular or key-value state, generating an app with create-tinybase, adding schemas or UI bindings, resolving TinyBase import paths, configuring browser or database persistence, configuring MergeableStore synchronization over WebSockets or Cloudflare Durable Objects, or diagnosing an existing TinyBase application.

77

Quality

96%

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

The canonical home for this skill is build-with-tinybase in tinyplex/tinybase

SKILL.md
Quality
Evals
Security

Quality

Content

92%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-constructed instructional skill body: executable generator commands, clearly sequenced scaffold/extend/verify workflows with behavioral validation checkpoints, and clean one-level-deep progressive disclosure over four real reference files. The only flaw is minor duplication of the architecture.md read-condition and the memory-recall instruction, which costs a small amount of token efficiency.

Suggestions

Remove the duplicate architecture.md guidance: the 'Select The Architecture' section repeats the read-when condition already given in the reference table — fold its scope-fit checklist into that section and drop the repeated pointer.

State the anti-memory-recall instruction once (either the preamble or 'Read The References') instead of twice ('Prefer a current generated application over reconstructing TinyBase setup from memory' and 'Do not recall TinyBase API details from memory').

DimensionReasoningScore

Conciseness

The body is lean and imperative with no explanations of concepts Claude already knows (no "what is TinyBase" padding, no version-dated instructions), so it is well above the score-3 anchor. However, the architecture.md read-condition is stated twice — once in the reference table ("Choosing between Store and MergeableStore, a persistence backend...") and again nearly verbatim in "Select The Architecture" — and the anti-memory-recall instruction is also repeated in the preamble and "Read The References"; these minor duplicated tokens keep it just short of the score-5 "every token earns its place" anchor.

4 / 5

Actionability

Guidance is fully executable: a copy-paste-ready generator contract command ("npm create tinybase@latest -- --list-options"), a complete unattended generation command with every flag spelled out, concrete post-generation steps, a current documentation entry point (https://tinybase.org/llms.txt), and specific API names in the error list ("createMergeableStore()", "startAutoPersisting()", "await synchronizer.startSync()", "WsServerDurableObject"). This matches the score-5 anchor: specific commands and examples cover the common cases with no key details missing.

5 / 5

Workflow Clarity

Multi-step processes are clearly sequenced with explicit validation checkpoints: scaffold (list options → translate requirements → generate → numbered post-generation steps including "Run the generated client build"), extend ("Inspect package.json, TinyBase imports, Store creation... before editing"), and a dedicated "Verify The Outcome" section with behavior-matched checks (real reload for persistence, two clients propagating in both directions for sync, reconnection testing, schema-rejection confirmation, "Report any verification that could not be performed"). This matches the score-5 anchor's explicit validation steps and checklists; it is above score 4 because validation is not merely present but matched to each risky behavior.

5 / 5

Progressive Disclosure

The body is a concise overview routing to four real, verified bundle files (references/architecture.md, import-paths.md, lifecycle.md, durable-objects.md) via a well-signaled read-when table, and all references are one level deep (they cross-link only to sibling references, never further). Content is appropriately split — detail lives in the references while the SKILL.md carries decisions, workflow, and a distilled error list — matching the score-5 anchor exactly.

5 / 5

Total

19

/

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.

An exemplary description: third-person, concrete action verbs, an explicit and detailed "Use when..." trigger clause, and unambiguous niche boundaries around TinyBase. Every judging guideline (no fluff, no over-claims, no verbosity) is satisfied.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Scaffold, extend, and verify reactive local-first JavaScript or TypeScript applications" — and enumerates specific tasks in the when-clause ("generating an app with create-tinybase, adding schemas or UI bindings, resolving TinyBase import paths, configuring browser or database persistence, configuring MergeableStore synchronization over WebSockets or Cloudflare Durable Objects"). Coverage is comprehensive with no generic filler, matching the score-5 anchor; it exceeds the score-4 anchor because there are no minor gaps in the action inventory.

5 / 5

Completeness

Both questions are answered explicitly: what ("Scaffold, extend, and verify reactive local-first JavaScript or TypeScript applications with TinyBase") and when ("Use when choosing TinyBase... generating an app with create-tinybase... or diagnosing an existing TinyBase application") with concrete trigger phrases. This is a direct match to the score-5 anchor example structure, not merely the score-4 pattern where the when-clause could be more specific.

5 / 5

Trigger Term Quality

Natural terms a user would actually say are comprehensively covered: "TinyBase", "create-tinybase", "schemas", "UI bindings", "import paths", "persistence", "MergeableStore", "WebSockets", "Cloudflare Durable Objects", "local-first", plus synonyms like "in-memory tabular or key-value state". This matches the score-5 anchor (comprehensive coverage including synonyms); it is above score 4 because no common phrasing for this niche is missing.

5 / 5

Distinctiveness Conflict Risk

The description is anchored to a clear niche (TinyBase) with distinct, library-specific triggers (MergeableStore, create-tinybase, Durable Objects), so conflict with adjacent JS-state or database skills is minimal. It matches the score-5 anchor; score 4 would require some noted overlap risk with closely related skills, which is not present.

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
tinyplex/tinybase
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.