CtrlK
BlogDocsLog inGet started
Tessl Logo

magicbase

Use when an HTML micro-app needs MagicBase persistence, window.Magic.db row operations, current-user context through window.Magic.getContext, creators, owners, assignees, permissions, CRUD, forms, surveys, todos, dashboards, filters, statistics, exports, or any saved user data.

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

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.

Highly actionable with executable examples and validation-gated workflows for destructive and batch operations. The main weaknesses are repeated safety guidance across sections and a monolithic single-file structure that inlines reference material no bundle files split out.

Suggestions

Consolidate the repeated system-field/created_by write-prohibition into one canonical statement and reference it from the per-API sections to cut token cost.

Move the runtime API reference (getTables/getTable/createRow/queryRows/etc. signatures) into a references/RUNTIME_API.md and keep SKILL.md as an overview pointing to it, enabling one-level-deep progressive disclosure.

Consider extracting the permission-intent matrix and scope-selection guidance into references/PERMISSIONS.md, leaving the core decision questions inline.

DimensionReasoningScore

Conciseness

The body is dense with operational specifics and avoids explaining basic concepts, but the system-field/created_by warnings ("Do not write system fields such as created_by…", "data must contain only dynamic column keys") recur 4–5 times across sections and could be consolidated.

3 / 5

Actionability

Provides copy-paste-ready, executable code for every runtime API (createRow, queryRows, updateRow, deleteRow, getContext), the admin guard, and a full create_magicbase_table JSON payload covering common cases.

5 / 5

Workflow Clarity

The schema-prep sequence (query tables → create table/columns → generate HTML) is numbered, and destructive/batch ops carry explicit validation (query before delete to show scope, confirm_delete=true, Pending-migration repair), with only minor checkpoint gaps.

4 / 5

Progressive Disclosure

Section headers are well organized, but no bundle files exist and the full API reference plus permission-intent matrix are inlined into one ~450-line file rather than split into one-level-deep reference files.

3 / 5

Total

15

/

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, concrete description that names specific capabilities and surfaces natural trigger terms with an explicit "Use when" clause. It clearly distinguishes the skill's niche with minimal conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — "MagicBase persistence, window.Magic.db row operations, current-user context through window.Magic.getContext, creators, owners, assignees, permissions, CRUD" — giving comprehensive coverage rather than vague abstraction.

5 / 5

Completeness

Explicitly states both what the skill handles (MagicBase persistence, row ops, current-user context, permissions, CRUD) and when to use it via the "Use when an HTML micro-app needs…" clause with concrete triggers.

5 / 5

Trigger Term Quality

Covers natural terms a user would say ("forms, surveys, todos, dashboards, filters, statistics, exports, or any saved user data") plus technical synonyms, matching the comprehensive keyword anchor.

5 / 5

Distinctiveness Conflict Risk

The named platform ("MagicBase") and "HTML micro-app" framing carve a clear niche with distinct triggers and minimal overlap with other skills.

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
dtyq/magic
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.