CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

data-programs

Save a run-code fetch/join/aggregate script as a stored, refreshable data source any app's own charts/tables can render, instead of a hardcoded provider action or a per-view re-fetch. Use when an ad-hoc run-code or provider-api-request analysis should become a live, cached data source other users or panels can reuse.

Quality

85%

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

81%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 well-structured, operational reference: concrete action signatures, explicit limits, a thorough caching/refresh model, and an authoring workflow with genuine validation checkpoints (dry-run-before-save, structured errors, lastGoodRun fallback). The main gaps are the absence of a worked example program and a couple of sections (rationale, cache edge-case rows) that could be tightened or moved to a reference file.

DimensionReasoningScore

Conciseness

The body is dense and operational — action signatures, a limits table, a caching behavior table — with no explanation of concepts Claude already knows. Minor trims are possible (the two-paragraph "Why this exists" rationale and a few long table cells), matching anchor 4 rather than the fully lean anchor 5.

4 / 5

Actionability

Concrete, copy-paste-ready action signatures are given for all six operations (e.g., `save-data-program({ name, title, description, code, defaultParams?, refreshMode?, refreshTtlMs?, background? })`) plus the `emit(rows, schema?)` contract and sandbox globals. A complete worked example of an actual program script (sample code calling emit with rows) is absent, which keeps it below anchor 5.

4 / 5

Workflow Clarity

The 6-step "Authoring workflow" is clearly sequenced with explicit validation checkpoints: step 1 says to confirm the prototype returns expected rows, and step 3 documents that save dry-runs the code and rejects failures with structured errors, returning `rowCount`/`columns`/`sampleRows` as proof. Failure modes and recovery (`lastGoodRun`, stale-serve, `background_pending`) are enumerated, matching anchor 5; anchor 4 would lack these explicit checkpoints.

5 / 5

Progressive Disclosure

Well-organized sections with clear headers, tables for caps and cache behavior, and clearly signaled one-level cross-references (analytics template's `data-programs` skill, and the `actions`/`sharing`/`security` related skills). No bundle files exist, and the ~120-line body is self-contained; a reference file could absorb some of the detailed cache-semantics table, so anchor 4 rather than 5.

4 / 5

Total

17

/

20

Passed

Description

83%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 strong: it states a concrete, distinctive capability and pairs it with an explicit 'Use when...' trigger clause containing natural platform vocabulary. Trigger coverage has minor gaps (a few synonyms like "query" or "dashboard" are absent), but conflict risk and completeness are well handled.

DimensionReasoningScore

Specificity

Concrete actions are named — "Save a run-code fetch/join/aggregate script as a stored, refreshable data source any app's own charts/tables can render" — with specific mechanisms (cached, refreshable, per-view re-fetch avoided), but it is one composite action rather than a comprehensive list of several discrete operations, matching anchor 4 rather than 5.

4 / 5

Completeness

Explicitly answers both: what ("Save a run-code fetch/join/aggregate script as a stored, refreshable data source...") and when ("Use when an ad-hoc run-code or provider-api-request analysis should become a live, cached data source other users or panels can reuse") with concrete trigger phrasing. Not below anchor 4 because the 'when' clause is fully explicit rather than merely present.

5 / 5

Trigger Term Quality

Good natural-term coverage for this platform's users: "run-code", "provider-api-request", "ad-hoc analysis", "live, cached data source", "reuse" — phrases users would plausibly say when wanting to persist an analysis. A few common variations (e.g., "query", "chart", "dashboard", "refresh") are missing, keeping it below anchor 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche — persisting run-code analyses as stored refreshable data sources — with distinct triggers unlikely to fire for unrelated skills. Minor overlap risk with generic run-code/analysis skills, so anchor 4 rather than 5.

4 / 5

Total

17

/

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

BuilderIO/agent-native

Path

.agents/skills/data-programs/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.