How do I install the Aspire SQL Projects skill?

Run npx get-skill add tomevault-io/aspire-sql-projects in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Aspire SQL Projects skill do?

Use SQL Database Projects (.sqlproj) with .NET Aspire for declarative schema deployment via dacpac. Use when this capability is needed. It is listed under Data & Analytics on SkillMD.

Is Aspire SQL Projects safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Aspire SQL Projects?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Aspire SQL Projects free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Aspire SQL Projects?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Aspire SQL Projects by tomevault-io

Name: Aspire SQL Projects
Author: tomevault-io

File contents

Aspire SQL Projects

Use when

Replacing ad-hoc SQL scripts with declarative schema management.
Needing repeatable schema deployment in Aspire startup.

Workflow

Add an SDK-style .sqlproj using Microsoft.Build.Sql for new work.
Build with dotnet build; the output artifact is a .dacpac.
Publish the .dacpac with SqlPackage /Action:Publish or an equivalent deployment task.
Model publish as an Aspire run-to-completion executable/container resource.
Ensure DAB and tools WaitForCompletion on the schema deployment resource.

Guardrails

Use WaitForCompletion for run-to-completion schema tasks.
Do not assert a first-party Aspire.Hosting.MSBuild SQL-project flow unless verified in current docs.
Keep SQL projects declarative: one source file per object; publish computes the target diff.
Treat publish as a deployment step, not just a project reference.
Keep DDL declarative and idempotency-aware where applicable.

Related skills

aspire-data-api-builder
data-api-builder-config

Microsoft Learn

Source: JerryNixon/data-api-builder-vscode-ext — distributed by TomeVault.

Frequently asked questions