Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Venus Build Run

ASecurity

Build Venus targets (CMake/MSVC build-msvc dir) and run demos correctly, target names, config flags, CWD/asset-path gotchas, env vars, and how to capture + inspect a demo frame. Use when asked to build, run, or screenshot any Venus executable, or when a demo "renders nothing"/"can't find assets".

9 stars
0 votes
0 copies
0 views
Added 9/27/2026
ai-agentsgoshellbash

Security Analysis

A100/100

Scanned 9/27/2026

$npx -y skills add Ugbot/ai-grind --skill venus-build-run --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Venus Build Run?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Venus Build Run
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ugbot-venus-build-run/badge)](https://www.skillsdirectory.com/skills/ugbot-venus-build-run)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: venus-build-run
description: Build Venus targets (CMake/MSVC build-msvc dir) and run demos correctly, target names, config flags, CWD/asset-path gotchas, env vars, and how to capture + inspect a demo frame. Use when asked to build, run, or screenshot any Venus executable, or when a demo "renders nothing"/"can't find assets".
---

# Build

One build tree: `build-msvc/` (MSVC multi-config; Release is the default working config, Debug enables VK validation layers).

```bash
cd C:/code/Venus
cmake --build build-msvc --target <target> --config Release
```

- Filter output: `2>&1 | grep -E "error|\.exe$"`, full MSVC output floods the context.
- Reconfigure only when CMakeLists changed: `cmake -S . -B build-msvc`. **`option()` defaults do NOT override an existing cache**, flipping a default in CMakeLists needs `-DTHE_OPTION=ON` once to update the cache.
- Zero-warnings law: pre-existing offenders are jobs.c/camera_rts.c C4133 + voxel macro redefs + libuv (don't add new ones; don't "fix" those in passing without a task).
- zig build exists (`build.zig`) but MSVC is the daily driver; smoke zig before claiming cross-build parity.

Key targets: `flagship_demo` (GL), `flagship_demo_vk` (VK flagship, THE visual bench), `vk_pbr_test` (VK PBR harness + presets), `Venus`, `space_game`, `space_rts`, `venus_editor`, `venus_playground`, `venus_cook` (asset cooker), `flagship_smoke_test`, and unit tests (`vasset_unit_test`, `ghi_format_unit_test`, `rg_v2_smoke`).

# Run demos

- **GL demos load shaders/assets CWD-relative → run from the repo root** (`cd C:/code/Venus && ./build-msvc/Release/flagship_demo.exe`). Running from the exe dir = "Failed to load shader file" errors.
- **VK demos** copy their `.spv` (and the HUD font) next to the binary post-build; they run from anywhere, but repo root is still safest.
- Asset pack: `VENUS_HELLO_ASSETS` (default probe: `C:/code/mars/external/HelloVulkan/Assets`) enables Sponza + skinned models + pack HDRIs. The pack's 4K HDRs make the CPU IBL bake take minutes, prefer the in-repo 1K `assets/textures/hdr/kloppenheim_07_puresky_1k.hdr`.
- Useful env: `VENUS_LOG_LEVEL=INFO` (Release defaults WARN), `VENUS_USE_GRAPH_V2=0|1` (two-way graph bisection), `VENUS_SCENE_PRESET=<name>` (vk_pbr_test), `VENUS_HELLO_IBL_HDR=<path>` (explicit HDR override).
- Backgrounding from bash: `(./demo.exe > log 2>&1 & echo $! > pid) && sleep 20 && kill $(cat pid)`. Direct-run logs are sometimes empty (pipe-vs-console quirk), the smoke harness's `--dump-stdout` is the reliable capture (see venus-smoke-golden).

# Capture + inspect a frame

```bash
powershell -ExecutionPolicy Bypass -File C:/code/Venus/cap_window.ps1 -Match "<window title substr>" -Out C:/code/Venus/build-msvc/cap.png
```
Then **Read the PNG with the Read tool**, you can see the frame and diagnose visually (black = unlit/zeroed UBO; giant flat triangles = garbage/uninitialized buffers; stripes = emit truncation). Smoke screenshots land at `build-msvc/smoke_view_vk13_<n>.png`.

Kill stray demos before rebuilding (exe lock ⇒ LNK1104):
`powershell -Command "Get-Process flagship_demo_vk,flagship_smoke_test -ErrorAction SilentlyContinue | Stop-Process -Force"`

Attribution

UgbotUgbot
View sourceSee grades on GitHubMore from Ugbot →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →