How do I install the Build Backend skill?

Run npx skillmds@latest add tomevault-io/build-backend 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.

Is Build Backend safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Build Backend?

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 Build Backend free to use?

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

Who published Build Backend?

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

Build Backend by tomevault-io — Agent Skill

Name: Build Backend
Author: tomevault-io

Build Backend

Builds the Fake Survey Generator backend .NET projects. Use this skill when backend code changes need to be compiled and validated for syntax errors. This skill orchestrates the dotnet build command and reports compilation errors.

tomevault-io c9a170a 2 files · 3.2 KB Updated Sep 17, 2026

File contents

Build Backend Skill

Use this skill to validate that all backend C# projects compile successfully without errors.

What This Skill Does

Runs dotnet build to compile all .NET projects in the solution
Captures and parses compilation errors
Reports errors with file and line number references
Exits with failure status if any compilation errors are found

When to Use

After implementing backend features in the Api project, Application project, or Worker project
To validate that dependencies and package versions are correct
Before running tests or other downstream validation steps
To catch syntax errors or type mismatches early

How the Agent Should Use This Skill

Prepare: Ensure you are in the repository root directory
Invoke: Run the backend build helper script from the repository root:
```
dotnet .github/skills/build-backend/build-backend.cs
```
Parse Output: Monitor stdout for success message and stderr for errors
Handle Errors: If exit code is non-zero, the build failed. Review the error messages to identify:
- File paths and line numbers from error output
- Type errors, syntax errors, or missing references
- Package version conflicts
Report: If any errors occur, halt further validation and report the compilation error details to the user

Success Criteria

Exit code: 0
Stdout contains: [BUILD] Backend build completed successfully

Failure Indicators

Exit code: 1
Stderr contains compilation errors (e.g., error CS0103: The name 'xyz' does not exist)
Stdout/stderr may contain file paths and line numbers of errors

Notes

The build script automatically finds the repository root by searching for FakeSurveyGenerator.slnx or FakeSurveyGenerator.sln
Full build output is captured; review stderr for detailed error messages
Backend projects are: Api, Application, Application.Tests, Api.Tests.Integration, Worker, ServiceDefaults, Proxy

Next Steps After Success

Once backend build succeeds, typically invoke:

Frontend Build Skill - to compile TypeScript
Test Backend Units Skill - to run unit and integration tests

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: build-backenddescription: Builds the Fake Survey Generator backend .NET projects. Use this skill when backend code changes need to be compiled and validated for syntax errors. This skill orchestrates the dotnet build command and reports compilation errors.---# Build Backend SkillUse this skill to validate that all backend C# projects compile successfully without errors.## What This Skill Does1. Runs `dotnet build` to compile all .NET projects in the solution2. Captures and parses compilation errors3. Reports errors with file and line number references4. Exits with failure status if any compilation errors are found## When to Use- After implementing backend features in the Api project, Application project, or Worker project- To validate that dependencies and package versions are correct- Before running tests or other downstream validation steps- To catch syntax errors or type mismatches early## How the Agent Should Use This Skill1. **Prepare**: Ensure you are in the repository root directory2. **Invoke**: Run the backend build helper script from the repository root: ``` dotnet .github/skills/build-backend/build-backend.cs ```3. **Parse Output**: Monitor stdout for success message and stderr for errors4. **Handle Errors**: If exit code is non-zero, the build failed. Review the error messages to identify: - File paths and line numbers from error output - Type errors, syntax errors, or missing references - Package version conflicts5. **Report**: If any errors occur, halt further validation and report the compilation error details to the user## Success Criteria- Exit code: 0- Stdout contains: `[BUILD] Backend build completed successfully`## Failure Indicators- Exit code: 1- Stderr contains compilation errors (e.g., `error CS0103: The name 'xyz' does not exist`)- Stdout/stderr may contain file paths and line numbers of errors## Notes- The build script automatically finds the repository root by searching for `FakeSurveyGenerator.slnx` or `FakeSurveyGenerator.sln`- Full build output is captured; review stderr for detailed error messages- Backend projects are: Api, Application, Application.Tests, Api.Tests.Integration, Worker, ServiceDefaults, Proxy## Next Steps After SuccessOnce backend build succeeds, typically invoke:- **Frontend Build Skill** - to compile TypeScript- **Test Backend Units Skill** - to run unit and integration tests---> Converted and distributed by [TomeVault](https://tomevault.io/claim/marcelmichau) — claim your Tome and manage your conversions.

Frequently asked questions