Agent skill

Serviceradar Build Test

by carverauto in carverauto/serviceradar

Use before building, testing, linting, formatting, producing images, or validating ServiceRadar changes locally or before a PR/release.

Apache-2.0Auto-check passedTesting & QA

Install Serviceradar Build Test

skills CLI
$ npx skills add carverauto/serviceradar --skill serviceradar-build-test -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install carverauto/serviceradar serviceradar-build-test --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/carverauto/serviceradar.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/serviceradar-build-test .claude/skills/serviceradar-build-test && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
serviceradar-build-test
GitHub stars
921
Token cost
~532 tokens
SKILL.md length
247 words
Files
1
Skills in repo
18
Repo updated
First seen
Licence
Apache-2.0

At a glance

Use before building, testing, linting, formatting, producing images, or validating ServiceRadar changes locally or before a PR/release.

  • Tasks that involve Linting and formatting
  • Calls make, cargo and bazel

What it does

Serviceradar Build Test is an agent skill from carverauto/serviceradar. Use before building, testing, linting, formatting, producing images, or validating ServiceRadar changes locally or before a PR/release.

Its SKILL.md is about 530 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Linting and formatting. It works with WebAssembly, Elixir and Rust. The repository describes itself as: Open-Source Network Management, Monitoring, ITOM, and Security Analytics. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Linting and formatting

Example prompts

  • “/serviceradar-build-test”

Requirements

  • Docker

What it can do on your machine

Read from SKILL.md and the folder at commit 2563b3f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • make
    • cargo
    • bazel
    • go

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Serviceradar Build Test loads about 532 tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 247 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~40
When it runs · the whole SKILL.md, loaded when a task matches
~532

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from carverauto/serviceradar at commit 2563b3f, republished under its Apache-2.0 licence (© carverauto). 247 words, ~532 tokens.

Download SKILL.mdSave it as .claude/skills/serviceradar-build-test/SKILL.md (or your agent's skills folder).
name
serviceradar-build-test
description
Use before building, testing, linting, formatting, producing images, or validating ServiceRadar changes locally or before a PR/release.
user-invocable
false
metadata.internal
true

ServiceRadar Build and Test Commands

Build & Test Commands

  • Every unit test, the way CI runs them: make test — an alias for bazel test -c opt --config=remote //... --test_tag_filters=-integration_test,-acceptance_test. --config=remote, not --config=ci: the CI profile points its caches at /bazel-cache, the node volume only the BuildBuddy executors mount, so it cannot run on a workstation. Run this before opening a PR and before cutting any release. It is the only command that covers the whole repo, because the Elixir unit shards exist ONLY as bazel targets (//elixir/serviceradar_core:unit_tests_*, //elixir/web-ng:unit_tests_*) and are invisible to go test, cargo test and mix test. Two broken Elixir suites reached a release tag that way.
  • Per-language tests + Go coverage profiles: make test-toolchains (go test / cargo test / vitest / mix precommit). Useful for a fast local loop; not a substitute for make test, and make check-coverage depends on it for the cover.*.profile files.
  • Lint: make lint.
  • Focused Go packages: go test ./go/pkg/....
  • SRQL (Rust) integration tests: cd rust/srql && cargo test.
  • Bazel images: bazel run //docker/images:<target>_push. A worktree without .bazelrc.remote is not on RBE — copy the gitignored rc files first (Hard Rules).
  • First-party Wasm plugins: make build_wasm_plugins, make push_wasm_plugins, make verify_wasm_plugins. Bazel fetches the pinned TinyGo toolchain automatically; local oras is still required for publish/inspect workflows. make push_all is the container-image path; make push_all_release adds the Wasm publish/sign/verify path for release-style runs.

Prefer Bazel targets when modifying code that already has BUILD files. Always run gofmt/cargo fmt where applicable (Go formatting handled by gofmt, Rust by cargo fmt).

© carverauto, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/serviceradar-build-test of carverauto/serviceradar.

Open the folder on GitHubat commit 2563b3f

Compare with similar skills

Serviceradar Build Test next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Serviceradar Build Test compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Serviceradar Build Test this skillcarverauto/serviceradar921—~532Automated safety check: PassApache-2.0
Maintainopenwpm/OpenWPM1.4k—~1.5kAutomated safety check: PassCustom licence
Review Pre Commitopenwpm/OpenWPM1.4k—~788Automated safety check: PassCustom licence
Fix Errorswarpdotdev/common-skills610—~1.4kAutomated safety check: PassMIT
Go Local Healthinstructa/agent-skills139—~732Automated safety check: PassNone
Working With Nixxmtp/libxmtp121—~1.4kAutomated safety check: PassMIT

Similar skills

  • Maintain

    openwpm/OpenWPM

    A skill your agent uses to run a periodic codebase-health pass — dependency audit, lint, test suite, dead code / TODO scan, doc freshness, crosslink issue hygiene, and build artifacts.

    1.4k GitHub stars~1.5k tokensUpdated 6 days ago
    Testing & QAAuto-check passed
  • Review Pre Commit

    openwpm/OpenWPM

    Use as a pre-commit quality gate — review the working diff for stub patterns (TODO/FIXME/unimplemented!()/todo!()), debug leftovers (dbg!, stray console.log/println!, commented-out code), then run…

    1.4k GitHub stars~788 tokensUpdated 6 days ago
    Testing & QAAuto-check passed
  • Fix Errors

    warpdotdev/common-skills

    Fix compilation errors, linting issues, and test failures in the warp Rust codebase.

    610 GitHub stars~1.4k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Go Local Health

    instructa/agent-skills

    Run local Go health checks (tests, coverage, lint) in Go repositories that contain go.mod/go.sum.

    139 GitHub stars~732 tokensUpdated 12 days ago
    Testing & QAAuto-check passed
  • Working With Nix

    xmtp/libxmtp

    A skill your agent uses when working with Nix flakes, selecting devShells, debugging environment issues, or understanding Nix infrastructure - covers shell selection, environment detection, common…

    121 GitHub stars~1.4k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Alef

    xberg-io/alef

    Use Alef correctly for Rust-to-polyglot binding generation. An agent skill from xberg-io/alef.

    100 GitHub stars~1.7k tokensUpdated today
    DevelopmentAuto-check passed

More from carverauto/serviceradar

All 18 skills in this repo
  • Demo Cnpg Local Web Ng

    carverauto/serviceradar

    Run ServiceRadar web-ng locally against the live Kubernetes demo CNPG database for dashboard, SRQL, services, and UI testing.

    921 GitHub stars~672 tokensUpdated yesterday
    Auto-check passed
  • Web Ng Docker Loop

    carverauto/serviceradar

    Run ServiceRadar elixir/web-ng locally against the Docker Compose CNPG database with copied mTLS certs and Docker secrets, then verify dashboard UI changes with Playwright.

    921 GitHub stars~737 tokensUpdated yesterday
    Auto-check passed
  • Demo Local Rollout

    carverauto/serviceradar

    Build unpublished sha-... An agent skill from carverauto/serviceradar.

    921 GitHub stars~4.2k tokensUpdated yesterday
    Auto-check passed
  • Demo Web Ng Fastpath

    carverauto/serviceradar

    Refresh the Kubernetes demo namespace with a web-ng-only change using the ServiceRadar fast path.

    921 GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Fieldsurvey Local Web Ng

    carverauto/serviceradar

    Run ServiceRadar web-ng locally against the Kubernetes demo namespace FieldSurvey data, including CNPG NodePort access, NATS Object Store artifact access, authenticated browser checks, and…

    921 GitHub stars~785 tokensUpdated yesterday
    Auto-check passed
  • Release Cut And Demo Roll

    carverauto/serviceradar

    Cut a ServiceRadar release and roll the Kubernetes demo namespace to the resulting published semver image tag through the guarded ArgoCD release branch.

    921 GitHub stars~3.9k tokensUpdated yesterday
    Auto-check passed

Questions about Serviceradar Build Test

What does Serviceradar Build Test do?

Use before building, testing, linting, formatting, producing images, or validating ServiceRadar changes locally or before a PR/release. Serviceradar Build Test is an agent skill from carverauto/serviceradar. Use before building, testing, linting, formatting, producing images, or validating ServiceRadar changes locally or before a PR/release.

When should I use Serviceradar Build Test?

Serviceradar Build Test fits situations like: tasks that involve Linting and formatting.

How do I install Serviceradar Build Test in Claude Code?

Run `npx skills add carverauto/serviceradar --skill serviceradar-build-test -a claude-code`. Or copy the skill folder (.agents/skills/serviceradar-build-test in carverauto/serviceradar) into .claude/skills/serviceradar-build-test in your project. Claude Code loads it when a task matches its description.

How do I install Serviceradar Build Test in Codex?

Run `npx skills add carverauto/serviceradar --skill serviceradar-build-test -a codex`. Or copy the skill folder (.agents/skills/serviceradar-build-test in carverauto/serviceradar) into .agents/skills/serviceradar-build-test in your project. Codex loads it when a task matches its description.

Can I use Serviceradar Build Test in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add carverauto/serviceradar --skill serviceradar-build-test -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/serviceradar-build-test, .gemini/skills/serviceradar-build-test, .github/skills/serviceradar-build-test and .opencode/skills/serviceradar-build-test in your project.

What does Serviceradar Build Test need to run?

Going by SKILL.md and its folder, Serviceradar Build Test needs the command-line tools its instructions call (make, cargo, bazel and go). Our summary lists: Docker.

Does Serviceradar Build Test access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Serviceradar Build Test safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Serviceradar Build Test use?

Serviceradar Build Test is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Serviceradar Build Test use?

About 532 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Serviceradar Build Test?

Skills that share tags, products or a category with Serviceradar Build Test: Maintain (openwpm/OpenWPM, 1.4k stars), Review Pre Commit (openwpm/OpenWPM, 1.4k stars), Fix Errors (warpdotdev/common-skills, 610 stars) and Go Local Health (instructa/agent-skills, 139 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Serviceradar Build Test?

carverauto (a GitHub organization) maintains it in carverauto/serviceradar, which has 921 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 10, 2026.

Source: carverauto/serviceradar on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.