portability

How to keep template code PostgreSQL-specific and hosting-agnostic. Use when defining schemas, writing raw SQL, or creating server routes.

Quality

73%

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/portability/SKILL.md

Quality

Content

68%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 tight, actionable reference with executable Drizzle/H3 code and concrete avoid-lists. Weakest on workflow clarity because it is a pattern catalog rather than a sequenced process with validation checkpoints.

Suggestions

Add a short worked example of a complete H3 route handler (defineEventHandler + readBody + Drizzle query) so the API list becomes a copy-paste-ready pattern.

Collapse the duplicated raw-SQL guidance into one place to remove the minor redundancy between the 'Never' prose and the 'Raw SQL helpers' subsection.

If any multi-step process is intended (e.g., adding a migration then updating the schema), sequence it with an explicit validate/run checkpoint to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence: a compact Drizzle schema, a query example, a tight export table, and rules stated once. A few minor redundancies (raw-SQL guidance restated across the 'Never' and 'Raw SQL helpers' subsections) keep it just below the 'every token earns its place' anchor of 5.	4 / 5
Actionability	Provides copy-paste-ready Drizzle schema and query-builder code plus specific named APIs ('defineEventHandler', 'readBody', 'getMethod', 'setResponseHeader') and concrete filenames to avoid ('netlify.toml', 'wrangler.toml', 'vercel.json'). Minor gaps (no example H3 handler body, no migration snippet) hold it at 4 rather than 5.	4 / 5
Workflow Clarity	This is a rules-and-patterns reference, not a sequenced workflow; sections (Rule, Database, Hosting Agnostic) imply an ordering but there are no explicit checkpoints or validation steps, so it sits at the midpoint anchor rather than above.	3 / 5
Progressive Disclosure	Well-organized into clear sections with a 'Related Skills' list that links one level deep to sibling skills and no nested references; no bundle files exist, and the ~100-line body is appropriately self-contained, fitting the 'good structure; minor organization gaps' anchor.	4 / 5
	Total	15 / 20 Passed

Description

78%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 focused, well-scoped description that pairs a clear niche with an explicit 'Use when' trigger clause. The main gap is that the 'what' is framed as a goal rather than enumerated capabilities, and trigger synonyms are thin.

Suggestions

Reframe the 'what' as concrete capabilities (e.g., 'Define PostgreSQL schemas, write Drizzle queries, and build H3/Nitro routes that stay hosting-agnostic') so the action list is explicit.

Add natural synonyms and tokens users actually say, such as 'Drizzle', 'migrations', 'deploy targets', or '.sql files', to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('PostgreSQL-specific and hosting-agnostic') and lists three concrete trigger contexts ('defining schemas, writing raw SQL, or creating server routes'), fitting the 'several specific actions; minor gaps' anchor rather than the 1-2 action anchor below.	4 / 5
Completeness	Explicitly gives both a 'what' ('keep template code PostgreSQL-specific and hosting-agnostic') and a 'when' ('Use when defining schemas, writing raw SQL, or creating server routes'); the 'what' is a goal statement rather than a crisp capability list, keeping it just below the 5 anchor.	4 / 5
Trigger Term Quality	Natural developer phrases ('defining schemas', 'writing raw SQL', 'server routes', 'PostgreSQL') are present, but it misses common synonyms and file/extension terms, so it does not reach the comprehensive coverage anchor of 5.	4 / 5
Distinctiveness Conflict Risk	The PostgreSQL-specific + hosting-agnostic niche with concrete triggers is clearly distinct from generic SQL or web skills and carries minimal overlap risk, matching the 'clear niche with distinct triggers' anchor.	5 / 5
	Total	17 / 20 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/portability/SKILL.md
Commit: cc2a915

Reviewed: 6 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.