storing-data

How to store application data in agent-native apps. All data lives in SQL. Use when adding data models, deciding where to store data, or reading/writing application data.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/storing-data/SKILL.md

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A thorough, highly actionable reference with executable commands and a useful decision table. It is held back by verbosity in places, the absence of an explicit validation feedback loop for batch/destructive ops, and a monolithic single-file structure.

Suggestions

Tighten the migration-naming 'Why' anecdote to a few sentences and trim Do/Don't entries that restate the Rule section.

Add an explicit validate-fix-retry checkpoint for destructive/batch DB operations (e.g. db-exec --statements rollback guidance).

Offload the per-template table and the migration-naming deep-dive into reference files linked one level deep from SKILL.md.

Dimension	Reasoning	Score
Conciseness	Dense and high-signal with no padding about basics Claude knows, but the migration-naming anecdote and some Do/Don't restatements run long and could be tightened.	2 / 3
Actionability	Provides executable code, exact `pnpm action ...` commands, a decision table for `db-exec` vs `db-patch`, and a portable schema DSL example that is copy-paste ready.	3 / 3
Workflow Clarity	Workflow is largely reference material; destructive/batch operations have gating guidance (fail closed, dev-only caps) but lack an explicit validate-fix-retry feedback loop, capping this at 2.	2 / 3
Progressive Disclosure	A single well-organized SKILL.md with clear sections and no bundle files, but it is a long dense document whose per-template tables and migration deep-dive could be split into one-level-deep references.	2 / 3
	Total	9 / 12 Passed

Description

75%

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 clear, well-scoped description that answers both what and when with an explicit trigger clause. It is slightly generic on natural trigger terms and lists situations rather than concrete actions.

Suggestions

Add a couple of concrete action verbs (e.g. "model, migrate, query") to lift specificity from domain-and-situations to multiple specific actions.

Broaden trigger terms with natural user phrasings (e.g. "database", "schema", "where to put data") alongside the technical "SQL" / "data models" wording.

Dimension	Reasoning	Score
Specificity	Names the domain and a few concrete situations ("adding data models", "deciding where to store data", "reading/writing application data") but does not enumerate multiple specific actions like the score-3 anchor.	2 / 3
Completeness	Explicitly states what it does ("store application data", "All data lives in SQL") and gives an explicit "Use when..." trigger clause, answering both what and when.	3 / 3
Trigger Term Quality	Relevant terms (SQL, data models, store data) are present but skew technical/generic and miss common natural phrasings a user would actually say, so not full coverage.	2 / 3
Distinctiveness Conflict Risk	The "agent-native apps" framing plus SQL-as-source-of-truth niche is distinct and unlikely to trigger for unrelated skills, despite the broad phrase "store data".	3 / 3
	Total	10 / 12 Passed

Validation

81%

Warnings & errors only

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

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: BuilderIO/agent-native
Path: .agents/skills/storing-data/SKILL.md
Commit: e9a2f0e

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.