How do I install the Build CI Local Script skill?

Run npx skillmds@latest add tomevault-io/build-ci-local-script 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 CI Local Script 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 CI Local Script?

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 CI Local Script free to use?

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

Who published Build CI Local Script?

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

Build CI Local Script by tomevault-io

Name: Build CI Local Script
Author: tomevault-io

File contents

build-ci-local.ps1 Workflow

When to use

Use this skill when working on:

scripts/build-ci-local.ps1
Build pipeline steps, flags, or output
How the script uses modules in scripts/modules/Build and scripts/modules/Core

How it’s structured (repo-specific)

Imports modules from scripts/modules:
- Core/Logging.psm1
- Core/Prerequisites.psm1
- Build/DotNetBuild.psm1
- Build/PluginBuild.psm1

Safe changes

Prefer adding reusable behavior in the appropriate module (Build/* or Core/*) and calling it from the script.
Keep flags backward compatible when possible.

Step-by-step procedure

Confirm which scenario is being modified (full CI, plugin-only, formatting, test docs).
Find the corresponding pipeline step in scripts/build-ci-local.ps1.
Prefer implementing reusable behavior in:

scripts/modules/Build/* for build operations
scripts/modules/Core/* for shared utilities/prereqs

Ensure the script continues to import modules from $ModulesDir (no hard-coded absolute paths).
Validate by running an appropriate command:

Quick sanity: pwsh -NoProfile -ExecutionPolicy Bypass -File scripts/build-ci-local.ps1 -SkipTests -SkipFormat
Full pipeline: pwsh -NoProfile -ExecutionPolicy Bypass -File scripts/build-ci-local.ps1

Examples (input → expected output)

Example: Add a new optional build step

Input: “Add a flag to run an extra verification step.”

Expected output:

A new param() switch with help text
Step wired into the pipeline with clear output
Reusable logic lives in a module if it’s non-trivial
Script still works with existing flags and defaults

How to run (examples)

Full build: pwsh -NoProfile -ExecutionPolicy Bypass -File scripts/build-ci-local.ps1
Quick: pwsh -NoProfile -ExecutionPolicy Bypass -File scripts/build-ci-local.ps1 -SkipTests -SkipFormat
Plugin-only: pwsh -NoProfile -ExecutionPolicy Bypass -File scripts/build-ci-local.ps1 -PluginOnly -DeployPlugin

References

Script docs: scripts/README.md
Module catalog: scripts/modules/README.md

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

---name: build-ci-local-scriptdescription: Run and modify scripts/build-ci-local.ps1 safely, keeping it aligned with scripts/modules and VS Code tasks. Use when this capability is needed.---# build-ci-local.ps1 Workflow## When to useUse this skill when working on:- `scripts/build-ci-local.ps1`- Build pipeline steps, flags, or output- How the script uses modules in `scripts/modules/Build` and `scripts/modules/Core`## How it’s structured (repo-specific)- Imports modules from `scripts/modules`: - `Core/Logging.psm1` - `Core/Prerequisites.psm1` - `Build/DotNetBuild.psm1` - `Build/PluginBuild.psm1`## Safe changes- Prefer adding reusable behavior in the appropriate module (`Build/*` or `Core/*`) and calling it from the script.- Keep flags backward compatible when possible.## Step-by-step procedure1. Confirm which scenario is being modified (full CI, plugin-only, formatting, test docs).2. Find the corresponding pipeline step in `scripts/build-ci-local.ps1`.3. Prefer implementing reusable behavior in:- `scripts/modules/Build/*` for build operations- `scripts/modules/Core/*` for shared utilities/prereqs4. Ensure the script continues to import modules from `$ModulesDir` (no hard-coded absolute paths).5. Validate by running an appropriate command:- Quick sanity: `pwsh -NoProfile -ExecutionPolicy Bypass -File scripts/build-ci-local.ps1 -SkipTests -SkipFormat`- Full pipeline: `pwsh -NoProfile -ExecutionPolicy Bypass -File scripts/build-ci-local.ps1`## Examples (input → expected output)### Example: Add a new optional build step**Input:** “Add a flag to run an extra verification step.”**Expected output:**- A new `param()` switch with help text- Step wired into the pipeline with clear output- Reusable logic lives in a module if it’s non-trivial- Script still works with existing flags and defaults## How to run (examples)- Full build: `pwsh -NoProfile -ExecutionPolicy Bypass -File scripts/build-ci-local.ps1`- Quick: `pwsh -NoProfile -ExecutionPolicy Bypass -File scripts/build-ci-local.ps1 -SkipTests -SkipFormat`- Plugin-only: `pwsh -NoProfile -ExecutionPolicy Bypass -File scripts/build-ci-local.ps1 -PluginOnly -DeployPlugin`## References- Script docs: [scripts/README.md](../../../scripts/README.md)- Module catalog: [scripts/modules/README.md](../../../scripts/modules/README.md)---> Converted and distributed by [TomeVault](https://tomevault.io/claim/danielshue) — claim your Tome and manage your conversions.

Frequently asked questions

Build CI Local Script