AO Desktop App Launcher
OrchestratorInc/agent-orchestrator
Launches, restarts and troubleshoots the real AO Electron desktop app from a checkout, with isolated or real local data and checks for stale processes.
Builds and runs a Go project locally to reproduce compile or runtime problems safely, using test environment variables and mocks instead of production credentials.
Install Local Build and Run
$ npx skills add pilinux/gorest --skill build-run -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pilinux/gorest build-run --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/pilinux/gorest.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/build-run .claude/skills/build-run && rm -rf skills-srcUse ~/.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/
Install the "build-run" agent skill from https://github.com/pilinux/gorest/tree/main/.agents/skills/build-run into .claude/skills/build-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-run", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/pilinux/gorest/tree/main/.agents/skills/build-runType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add pilinux/gorest --skill build-run -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pilinux/gorest build-run --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pilinux/gorest.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/build-run .agents/skills/build-run && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "build-run" agent skill from https://github.com/pilinux/gorest/tree/main/.agents/skills/build-run into .agents/skills/build-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-run", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pilinux/gorest --skill build-run -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pilinux/gorest build-run --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pilinux/gorest.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/build-run .cursor/skills/build-run && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "build-run" agent skill from https://github.com/pilinux/gorest/tree/main/.agents/skills/build-run into .cursor/skills/build-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-run", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/pilinux/gorest.git --path .agents/skills/build-run--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add pilinux/gorest --skill build-run -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pilinux/gorest build-run --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pilinux/gorest.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/build-run .gemini/skills/build-run && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "build-run" agent skill from https://github.com/pilinux/gorest/tree/main/.agents/skills/build-run into .gemini/skills/build-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-run", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install pilinux/gorest build-runInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add pilinux/gorest --skill build-run -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pilinux/gorest.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/build-run .github/skills/build-run && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "build-run" agent skill from https://github.com/pilinux/gorest/tree/main/.agents/skills/build-run into .github/skills/build-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-run", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pilinux/gorest --skill build-run -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pilinux/gorest build-run --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pilinux/gorest.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/build-run .opencode/skills/build-run && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "build-run" agent skill from https://github.com/pilinux/gorest/tree/main/.agents/skills/build-run into .opencode/skills/build-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-run", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
build-run- GitHub stars
- 506
- Token cost
- ~362 tokens
- SKILL.md length
- 160 words
- Files
- 1
- Skills in repo
- 20
- Repo updated
- First seen
- Licence
- MIT
At a glance
Builds and runs a Go project locally to reproduce compile or runtime problems safely, using test environment variables and mocks instead of production credentials.
- Checking that a Go project still compiles
- SKILL.md covers When to Use, Rules, Commands and Output, plus 3 more sections
- Calls go
- Reproducing a failing integration test locally
What it does
The skill is a short procedure for confirming that a Go project compiles, reproducing a runtime issue or validating environment-dependent changes without touching production. It forbids production credentials and external services unless you supply safe mocks or stubs, and it loads local settings with source setTestEnv.sh. The listed commands are go build, go fmt, go vet, go mod tidy, a single go test run for a named test, and starting the example app with go run.
The agent reports a result of success or failure, the first relevant error or stack lines, a minimal reproduction of one to three commands and suggested next steps, such as which logs to check or which mocks to add. It points to AGENTS.md and setTestEnv.sh for details and names the related skills test-runner, ci-orchestrator and fix-suggester.
When your agent uses it
- Checking that a Go project still compiles
- Reproducing a failing integration test locally
- Validating a change that depends on environment settings
Example prompts
- “Does the project compile? Run the build and report the first error.”
- “Reproduce the failing integration test TestLogin and show me the first failing lines.”
- “Start the example app with the test environment and tell me if it boots.”
Requirements
- The Go toolchain
- The project's setTestEnv.sh script for local test settings
What it can do on your machine
Read from SKILL.md and the folder at commit 38aab64. 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:
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
Local Build and Run loads about 362 tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 160 words of instructions outside code blocks.
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 pilinux/gorest at commit 38aab64, republished under its MIT licence (© pilinux). 160 words, ~362 tokens.
Download SKILL.mdSave it as
.claude/skills/build-run/SKILL.md (or your agent's skills folder).- name
- build-run
- description
- Build and run the project locally to reproduce compile/runtime issues in a safe, non-production way.
- license
- MIT
- metadata.mode
- verify
- metadata.purpose
- build-run
Build and Run
When to Use
- Confirm the codebase compiles, reproduce a runtime issue locally, or validate environment-dependent changes.
Rules
- Do not use production credentials or external services unless the user provides safe mocks/stubs.
- Use
source setTestEnv.shfor local env needed by tests or the app. - Prefer reproducible, minimal commands and capture key output lines.
Commands
- Compile:
go build -v ./... - Format:
go fmt ./... - Vet:
go vet -v ./... - Tidy deps:
go mod tidy - Run tests that reproduce an issue:
source setTestEnv.sh && go test -run <TestName> ./pkg/path - Start example app:
cd example2/cmd/app && go run main.go(use with test env)
Output
- Result: success or failure.
- Key logs: first relevant error or stack lines.
- Minimal repro: 1-3 commands.
- Next steps: which logs/files to inspect or which mocks to add.
Examples
- "Does the project compile?" - run
go build -v ./...and report. - "Reproduce failing integration test X" - provide commands and first failing lines.
Related Skills
test-runner,ci-orchestrator,fix-suggester
References
AGENTS.md(build and run commands),setTestEnv.sh,llms.txt
© pilinux, MIT. 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/build-run of pilinux/gorest.
Open the folder on GitHubat commit 38aab64
Compare with similar skills
Local Build and Run 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Local Build and Run this skillpilinux/gorest | 506 | — | ~362 | Automated safety check: Pass | MIT | |
| AO Desktop App LauncherOrchestratorInc/agent-orchestrator | 13k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Golang Troubleshootingsamber/cc-skills-golang | 3.4k | — | ~3.3k | Automated safety check: Pass | MIT | |
| Golang Samber Oopscontext-labs/whip | 1.1k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Golang Troubleshootingcontext-labs/whip | 1.1k | — | ~3.2k | Automated safety check: Pass | MIT | |
| Golang PerformanceMadAppGang/claude-code | 285 | — | ~5k | Automated safety check: Pass | MIT |
Similar skills
Golang Troubleshooting
samber/cc-skills-golang
Troubleshoot Golang programs systematically - find and fix the root cause.
Golang Samber Oops
context-labs/whip
Structured error handling in Golang with samber/oops — error builders, stack traces, codes, context, wrapping, attributes, user-facing vs developer messages, panic recovery, logger integration.
Golang Troubleshooting
context-labs/whip
Troubleshoot Golang programs — find and fix the root cause. An agent skill from context-labs/whip.
Golang Performance
MadAppGang/claude-code
A skill your agent uses when profiling Go applications (pprof), running benchmarks, optimizing memory/CPU usage, or debugging performance bottlenecks in production Go code.
Local Dev
SmilyOrg/photofield
Run, test, and debug the photofield server locally. An agent skill from SmilyOrg/photofield.
More from pilinux/gorest
All 20 skills in this repoConfig Loader Helper
pilinux/gorest
Diagnoses configuration failures in the gorest project by listing the required environment variables grouped by feature and giving minimal commands for a safe local test setup.
Go AST Code Introspection
pilinux/gorest
Enumerates Go declarations and signatures from the syntax tree, then proposes small, mechanically safe refactors with file and line citations.
Code Navigation
pilinux/gorest
Rapid, focused navigation to locate definitions/usages and map the impact of proposed changes.
Cited Code Explainer
pilinux/gorest
Explains how a module behaves in a few short, read-only sections, with a path-and-line citation behind every non-trivial claim.
Cited File Reader
pilinux/gorest
Reads only the lines needed from a source file and answers with a short summary and path:line citations, without changing anything.
Fix Suggester
pilinux/gorest
Diagnose failures and propose minimal, test-backed fixes with verification and rollback instructions.
Related
Works with
Categories
Questions about Local Build and Run
What does Local Build and Run do?
Builds and runs a Go project locally to reproduce compile or runtime problems safely, using test environment variables and mocks instead of production credentials. The skill is a short procedure for confirming that a Go project compiles, reproducing a runtime issue or validating environment-dependent changes without touching production.sh.
When should I use Local Build and Run?
Local Build and Run fits situations like: checking that a Go project still compiles; reproducing a failing integration test locally; validating a change that depends on environment settings.
How do I install Local Build and Run in Claude Code?
Run `npx skills add pilinux/gorest --skill build-run -a claude-code`. Or copy the skill folder (.agents/skills/build-run in pilinux/gorest) into .claude/skills/build-run in your project. Claude Code loads it when a task matches its description.
How do I install Local Build and Run in Codex?
Run `npx skills add pilinux/gorest --skill build-run -a codex`. Or copy the skill folder (.agents/skills/build-run in pilinux/gorest) into .agents/skills/build-run in your project. Codex loads it when a task matches its description.
Can I use Local Build and Run 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 pilinux/gorest --skill build-run -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/build-run, .gemini/skills/build-run, .github/skills/build-run and .opencode/skills/build-run in your project.
What does Local Build and Run need to run?
Going by SKILL.md and its folder, Local Build and Run needs the command-line tools its instructions call (go). Our summary lists: The Go toolchain; The project's setTestEnv.sh script for local test settings.
Does Local Build and Run 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 Local Build and Run 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 Local Build and Run use?
Local Build and Run is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Local Build and Run use?
About 362 tokens (SKILL.md is roughly 1.4k 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 Local Build and Run?
Skills that share tags, products or a category with Local Build and Run: AO Desktop App Launcher (OrchestratorInc/agent-orchestrator, 13k stars), Golang Troubleshooting (samber/cc-skills-golang, 3.4k stars), Golang Samber Oops (context-labs/whip, 1.1k stars) and Golang Troubleshooting (context-labs/whip, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Local Build and Run?
pilinux (a GitHub user) maintains it in pilinux/gorest, which has 506 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on September 25, 2026.
Source: pilinux/gorest on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.