blaxel-ai/build-dev
.agents/skills/build-dev/SKILL.md
Build the CLI in development mode. Use when the user says "build", "build dev", "compile", "rebuild", or when you need to test local changes to the CLI binary. Also use this after writing code changes to verify they compile correctly, or when the user wants to try out their changes locally.
$ install --global
skillsauthnpx skillsauth add blaxel-ai/toolkit build-devInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 8:37 PM40.9s1 file scanned
SKILL.md
- name:
- build-dev
- description:
- Build the CLI in development mode. Use when the user says "build", "build dev", "compile", "rebuild", or when you need to test local changes to the CLI binary. Also use this after writing code changes to verify they compile correctly, or when the user wants to try out their changes locally.
Run make build-dev from the repository root.
make build-dev
This compiles the blaxel binary with go build, injecting version=dev and the current git commit via -ldflags, then copies it to ~/.local/bin/blaxel and ~/.local/bin/bl so the user can immediately test with bl or blaxel.
If the build fails, read the error output carefully, fix the issue in the source code, and re-run until it succeeds.
Related Skills
blaxel-ai/lint
development
VerifiedTrustedCommunity
Lint all changed Go files, fix every error, and confirm the build passes. Use when the user says "fix lint", "run lint", "lint", or when pre-commit hooks fail. Also use this proactively before committing code or when you notice linter warnings in build output.
9SKILL.mdUpdated Apr 16, 2026
openclaw/taskflow
tools
VerifiedTrustedCommunity
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
357,764SKILL.mdUpdated Apr 10, 2026
openclaw/extensions/lobster
tools
VerifiedTrustedCommunity
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
357,764SKILL.mdUpdated Apr 10, 2026
steipete/extensions/lobster
tools
VerifiedTrustedCommunity
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
357,588SKILL.mdUpdated Apr 13, 2026