Log file path is available immediately after build

Run UnrealCV closed-loop test workflow (build + launch + test).

You say
Buy it · $69 Read it before you buy $69 Written by unrealcv · unverified publisher
Context cost
1.9k tokensestimated from the bundle, loaded when it triggers
Bundle
1 file · 7.8 kBtext throughout, nothing executable
Licence
MITpaid listing
Last change
no release on file
Servers it uses
Noneruns standalone

What it does

Run UnrealCV closed-loop test workflow (build + launch + test)

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Workflow

Runs a procedure end to end.

gamedev

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md7.8 kB · 286 lines
--- name: test-workflow description: Run UnrealCV closed-loop test workflow (build + launch + test) model: sonnet ---
7You are the UnrealCV Test Workflow Runner. Execute the complete build-test-debug pipeline using the workflow harness.
8
9## Task
10
11Run the UnrealCV debug harness to verify code changes work correctly:
121. **Build** - Compile UE project with UnrealCV plugin
132. **Launch** - Start game and wait for UnrealCV server
143. **Test** - Run connectivity and API tests
154. **Report** - Show results and any errors
16
17## Execution Modes
18
19### Default: Full Workflow
20Run complete pipeline (build + launch + test):
21```bash
22cd workflow && python harness.py full
23```
24
25### Build Only
26Just compile without testing:
27```bash
28cd workflow && python harness.py build
29```
30
31## Configuration
32
33The harness uses default settings from config.py. If you need custom paths, create workflow/config.json:
34
35```json
36{
37 "ue_path": "H:/UE_5.6/Engine",
38 "project_path": "G:/HUAWEI_Project_UE56/HUAWEI_Project.uproject",
39 "plugin_root": "G:/HUAWEI_Project_UE56/Plugins/unrealcv",
40 "port": 9000,
41 "log_filter_keywords": ["UnrealCV", "Error", "Warning", "Camera", "Sensor"],
42 "post_launch_delay": 5.0 // Seconds to wait after server ready before tests
43}
44```
45
46**Important configs:**
47- post_launch_delay: Time to wait after server ready before running tests (default: 3.0s). Increase this if shaders need time to compile.
48- server_ready_timeout: Max time to wait for server to start (default: 60s)
49
50## Windows Paths Caution
51Use / rather than \\, \ for paths, e.g. G:/HUAWEI_Project_UE56 rather than G:\\HUAWEI_Project_UE56, G:\HUAWEI_Project_UE56.
52
53### Bad Use Cases
54 Bash(cd G:\HUAWEI_Project_UE56\Plugins\unrealcv\workflow && python harness.py full)
55 ⎿  Error: Exit code 1
56 /usr/bin/bash: line 1: cd: G:HUAWEI_Project_UE56Pluginsunrealcvworkflow: No such file or directory
57### Good Use Cases
58● Bash(python workflow/harness.py full)
59
60## Execution Steps
61
62### Step 1: Verify Environment
63
641. Check workflow directory exists: workflow/
652. Verify default paths in config.py match your environment (or create config.json to override)
663. Verify UE path and project path are valid
67
68### Step 2: Run Build
69
70Execute build phase:
71```bash
72cd workflow && python harness.py build
73```
74
75Monitor for:
76- Compilation errors in UnrealCV plugin files
77- Link errors
78- Warnings that might indicate issues
79
80**If build fails**:
81- Check for syntax errors in modified files
82- Verify all includes are correct
83- Check for missing dependencies
84
85## Build Logs
86
87Build logs are automatically saved to workflow/debug_logs/ directory:
88
89```
90workflow/debug_logs/build_<TargetName>_<YYYYMMDD_HHMMSS>.log
91```
92
93**Accessing build logs from the skill:**
94
95After running build, the log file path is stored in BuildResult.log_path:
96
97```python
98from workflow.builder import UEBuilder
99
100builder = UEBuilder()
101result = builder.build()
102
103# Log file path is available immediately after build
104if result.log_path:
105 print(f"Build log saved to: {result.log_path}")
106 # Read the full build log
107 with open(result.log_path, 'r') as f:
108 build_log_content = f.read()
109```
110
111**Finding the latest build log:**
112
113```python
114from pathlib import Path
115import glob
116
117log_dir = Path("workflow/debug_logs")
118if log_dir.exists():
119 log_files = list(log_dir.glob("build_*.log"))
120 if log_files:
121 latest_log = max(log_files, key=lambda p: p.stat().st_mtime)
122 print(f"Latest build log: {latest_log}")
123```
124
125**In the harness output:**
126The build phase displays the log path:
127```
128[Build] Log file: workflow/debug_logs/build_HUAWEI_Project_20250311_143052.log
129[OK] Build completed in 45.2s
130Build log: workflow/debug_logs/build_HUAWEI_Project_20250311_143052.log
131```
132
133### Step 3: Run Tests
134
135Execute full test suite:
136```bash
137cd workflow && python harness.py full
138```
139
140Or with headless mode (no window):
141```bash
142cd workflow && python harness.py full --headless
143```
144
145### Step 4: Analyze Results
146
147**Success indicators**:
148```
149[OK] Build completed in XXXs
150[OK] Server ready
151[OK] All basic tests passed
152Test Results:
153 [PASS] Connection (0.01s)
154 [PASS] Version (0.02s)
155 [PASS] Status (0.01s)
156 [PASS] Cameras (0.01s)
157 [PASS] Camera 0 Location (0.01s)
158 [PASS] Camera 0 Rotation (0.01s)
159 [PASS] Camera 0 FOV (0.01s)
160 [PASS] Objects (0.02s)
161 [PASS] Capture Lit (0.15s) # Image capture tests
162 [PASS] Capture Depth (0.12s)
163 [PASS] Capture Normal (0.14s)
164 [PASS] Capture ObjectMask (0.13s)
165
166Summary: 12/12 passed
167```
168
169**Failure indicators**:
170- Build errors (compilation/linking)
171- Server timeout (game didn't start)
172- Test failures (API not working)
173
174## Test Coverage
175
176The workflow runs these tests:
177
178### Basic Connectivity Tests
1791. **Connection** - TCP connection to UnrealCV server
1802. **Version** - Get plugin version
1813. **Status** - Get server status
1824. **Cameras** - List available cameras
1835. **Camera 0 Location** - Get camera position
1846. **Camera 0 Rotation** - Get camera rotation
1857. **Camera 0 FOV** - Get camera field of view
1868. **Objects** - List scene objects
187
188### Image Capture Tests (with post_launch_delay wait)
1899. **Capture Lit** - vget /camera/0/lit - RGB image capture
19010. **Capture Depth** - vget /camera/0/depth - Depth map capture
19111. **Capture Normal** - vget /camera/0/normal - Normal map capture
19212. **Capture ObjectMask** - vget /camera/0/object_mask - Segmentation mask
19313. **Capture OpticalFlow** - vget /camera/0/optical_flow - Optical flow (if available)
194
195## Common Issues & Solutions
196
197### Build Issues
198| Error | Solution |
199|-------|----------|
200| Build tool not found | Check ue_path in config.json |
201| Compilation error | Fix syntax in modified .cpp/.h files |
202| Link error | Check all function declarations have definitions |
203
204### Launch Issues
205| Error | Solution |
206|-------|----------|
207| Server timeout | Increase server_ready_timeout in config |
208| Port in use | Kill existing process or change port |
209| Game crashes | Check UE logs for assertion failures |
210
211### Test Issues
212| Error | Solution |
213|-------|----------|
214| Connection refused | Server not started, check launch phase |
215| Command timeout | Command handler not registered or crashed |
216| Wrong response | Command implementation bug |
217
218## Log Monitoring
219
220After tests pass, monitor logs for warnings:
221```bash
222cd workflow && python harness.py logs --filter "UnrealCV,Error,Warning"
223```
224
225## Report Format
226
227After execution, provide summary:
228
229```
230UnrealCV Test Workflow Report
231==============================
232
233Build Phase:
234 Status: ✓ SUCCESS / ✗ FAILED
235 Duration: XXXs
236 Warnings: N (if any)
237 Log File: workflow/debug_logs/build_xxx.log
238
239Launch Phase:
240 Status: ✓ SUCCESS / ✗ FAILED
241 Server startup: XXs
242 Post-launch delay: X.Xs (for shader compilation)
243
244Test Phase:
245 Status: ✓ PASSED / ✗ FAILED
246 Passed: N/12 (basic + capture tests)
247 Failed tests: (list if any)
248 Capture tests: ✓ Lit, Depth, Normal, ObjectMask (OpticalFlow if available)
249
250Overall: ✓ ALL TESTS PASSED / ✗ WORKFLOW FAILED
251
252Recommendations:
253- If build failed: Fix compilation errors, check build log
254- If tests failed: Check command implementations, verify image capture sensors
255- If capture tests failed: May need longer post_launch_delay for shader compilation
256- If all passed: Code is ready for commit
257```
258
259## Usage Examples
260
261**After making code changes**:
262```
263User: /test-workflow
264```
265**Build only**:
266```
267User: /test-workflow --build-only
268```
269
270**With headless mode**:
271```
272User: /test-workflow --headless
273```
274
275## Exit Codes
276
277- 0: All tests passed
278- 1: Build or test failed
279
280## Notes
281
282- First build may take 3-5 minutes
283- Subsequent builds are faster (incremental)
284- Headless mode is useful for CI/CD
285- Game window may steal focus during launch
286
In the file
SKILL.md1,074 words
Files1
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈30
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
1,920
on trigger
The instruction body, read only when the skill fires.
0.97%
of a 200k window
Ten skills this size would take about 10% of the window before you open a file.
050k100k150k200k context window

1.9k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Middling. Fine to keep on in a project where you use it weekly, worth unloading in one where you never do.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

1 file, 7.8 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md7.8 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 1 file you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

$69 once
Log file path is available immediately after build · MIT · unrealcv
one-time
Price$69 once
LicenceMIT — the author’s, unchanged by this purchase
Paid throughStripe, once, on the card you add at the checkout
Keeps workingfor good — the files are yours once they are on disk
Updatesevery update its author ships, delivered through this account

You can read the whole bundle before paying — the SKILL.md above is the product, not a preview of it. What the money buys is the delivery: the folder packaged and handed to your machine by key, every update its author ships, and our support if it does not do what this listing says. The terms of use are MIT, set by the author and unchanged by buying it here.

Payment runs through Stripe, on a page like this one rather than a redirect. Once there is an account it joins the same mcprush invoice as everything else you run, so there is never a second card to enter.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Versionnot versioned
Publishedno release date on file
Price$69
Referenceunrealcv/log-file-path-is-available-immediately-after-buil

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v
  • No earlier releases have been published to the marketplace.
Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Who wrote it

UN
unrealcv

Publishes on mcprush.

0 servers listed1 skill listednot claimed
Profile
Publisher
Servers0