메뉴
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/Aditya232-rtx/Ouroboros --skill unreal-mcp명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Add security scanning to CI/CD with Fang — GitHub Actions, GitLab CI, or any pipeline — so every pull request gets a diff-scoped AI pentest that blocks vulnerable code before it merges, with results as PR comments and SARIF uploaded to code scanning. Covers both the self-hosted open-source CLI (runs in your runner) and the managed app.fang.ai platform (GitHub/GitLab app or API, no runner infra). Use when the user asks to add security scanning, SAST/DAST, pentesting, vulnerability checks, or automated security review to their CI pipeline, pre-merge gate, or PR workflow.
Fix security vulnerabilities found by a Fang pentest (open-source CLI or app.fang.ai cloud) — triage by severity, patch the root cause rather than the symptom, and re-run Fang to prove each fix actually closes the exploit. Handles injection, XSS, SSRF, broken access control, IDOR, and other validated findings. Use after a Fang scan reports findings, or when the user asks to remediate, patch, or fix security issues from a fang_runs report, vulnerabilities.json, findings.sarif, or a cloud scan.
Run a managed pentest of a web app or API through the app.fang.ai REST API — no local Docker, LLM key, or install needed. Create an API token, register domain/repository assets, launch and poll scans, triage vulnerabilities, export SARIF, download PDF/DOCX pentest reports for SOC 2 and other compliance evidence (Enterprise plan), start PR reviews, and set up schedules and webhooks. Use when the user wants continuous or scheduled pentesting-as-a-service, an auditor-ready pentest report, scans tracked in a team dashboard, or security testing from a sandboxed agent/CI environment with no infrastructure.
SKILL.md 표시 중
| name | unreal-mcp |
| description | Automate Unreal Engine editor scenes, actors, and renders. |
| version | 1.0.0 |
| requires | Unreal Editor 5.8+ with the Unreal MCP plugin enabled and its server running |
| author | Ouro |
| license | MIT |
| tags | ["unreal","unreal-engine","ue5","3d","mcp","scenes","cinematics","lighting","gamedev"] |
| platforms | ["linux","macos","windows"] |
| metadata | {"hermes":{"tags":["unreal","unreal-engine","ue5","3d","mcp","scenes","cinematics","lighting","gamedev"],"related_skills":[]}} |
Companion skill for the unreal-engine entry in the Ouro MCP catalog. The
MCP server (Epic's official, experimental "Unreal MCP" plugin, internal id
ModelContextProtocol) runs INSIDE the Unreal Editor process and exposes
editor functionality as typed tools. This skill teaches how to drive it well:
discovering the live tool surface, sequencing calls safely, translating
plain-English asks into scenes that actually look good, and verifying work
visually. The user should never need to touch the editor beyond launching it.
Use when the user wants anything done in Unreal Engine: build or dress a level, spawn/move/delete actors, set up lighting and atmosphere, create or tune material instances, frame a camera shot, capture screenshots or renders, import assets, inspect the scene or UI, run automation tests, or script the editor. Works for single actions ("make the sun golden hour") and for complete multi-step projects ("build me a moody forest clearing with a campfire and render a shot of it").
Don't use for: DCC-style mesh modeling/sculpting (model in Blender and import the result), or for editing Unreal C++ project source (that's normal code work — use the terminal; this skill is about the live editor).
Two halves, in this order: the editor side must be up before Ouro connects.
http://127.0.0.1:8000/mcp
(port/path configurable in the same panel; server name is unreal-mcp).
To start manually instead, run ModelContextProtocol.StartServer in the
editor console (backtick key).ouro mcp install unreal-engine
This writes the mcp_servers.unreal-engine HTTP entry pointing at
http://127.0.0.1:8000/mcp and probes the live server for its tools. Run it
while the editor + server are up so the probe sees the real surface. If the
user changed port/path in Editor Preferences, edit the in
under to match.
url~/.ouro/config.yamlmcp_servers.unreal-engineDo NOT use ModelContextProtocol.GenerateClientConfig for Ouro — that
writes .mcp.json-style files for Claude Code/Cursor/etc. Ouro connects
from config.yaml via the catalog entry.
ModelContextProtocol.StartServer manually).mcp_unreal_engine_*. If
they're missing: editor wasn't up first — start it, then open a new
Ouro session.mcp_unreal_engine_list_toolsets and confirm toolsets
come back.By default the plugin runs in tool-search mode: tools/list returns only
three meta-tools, and every real tool is reached through them. Through Ouro
they appear as:
| Ouro tool | Purpose |
|---|---|
mcp_unreal_engine_list_toolsets | Names + descriptions of every registered toolset |
mcp_unreal_engine_describe_toolset | Full JSON schemas for one named toolset's tools |
mcp_unreal_engine_call_tool | Invoke a named tool with arguments, get the result |
The discovery walk, always in this order:
list_toolsets → see what capability groups this project actually has
(the surface is project-dependent: enabled plugins, Game Feature Plugins,
and any custom toolsets all contribute). Names come back FULLY QUALIFIED
(editor_toolset.toolsets.scene.SceneTools,
EditorToolset.EditorAppToolset) — use them verbatim as toolset_name.describe_toolset on the group you need → read the real parameter
schemas. Never guess parameter names — schemas are the contract.call_tool with the qualified toolset name, the SHORT tool name
(find_actors, not the dotted form), and arguments matching the schema.Cache what you learn for the session; re-list only after the editor side
changes (new plugin enabled, toolset authored, RefreshTools run).
The alternative eager mode (Enable Tool Search off in Editor Preferences)
advertises every tool as its own mcp_unreal_engine_<tool> entry. Discovery
then happens at ouro mcp install/configure time instead. Tool-search
mode is the default and what this skill assumes; it also keeps schema tokens
out of every API call, so prefer it.
See references/tool-surface.md for the shipped toolset catalog, authoring
custom toolsets, and the full plugin configuration/console-command reference.
Every Unreal task follows the same loop:
call_tool → AgentSkillToolset.ListSkills): a matching project skill's
instructions override this skill's generic defaults.call_tool.
The server executes tools serially on the game thread — a big
monolithic operation freezes the editor UI until it finishes and risks
client timeouts. Exception: for loops over 5+ homogeneous operations,
ONE ProgrammaticToolset.execute_tool_script call batches them
server-side without breaking the serial rule
(references/advanced-workflows.md).mcp_unreal_engine_* calls in one turn — Ouro runs batched calls
concurrently, and parallel calls against the game thread deadlock or
fail. Strictly one call, await result, next call. This overrides the
general parallel-tool-calls guidance.references/tool-surface.md for
the capture options; vision_analyze the image — you are the art
director, judge it)./Game/...), file
locations of captures/renders.Rules of the world while you work:
references/scene-craft.md./Game/Folder/Asset.Asset for
project content, /Engine/BasicShapes/Cube.Cube for engine primitives.intensity: 10, and physical values blow
them out (references/scene-craft.md has the numbers,
references/pitfalls.md #12b has the calibration rule).The user gives intent, not specs. Translate before you build:
MEDIA: path), plus a short
summary of what exists in the level and where it was saved.references/recipes.md has complete worked builds (exterior daylight scene,
moody interior, golden-hour cinematic + render, asset import & placement)
with the exact call sequences and values.
Load on demand; keep SKILL.md-level rules in mind throughout.
| Reference | Contents |
|---|---|
references/tool-surface.md | Shipped toolsets catalog, discovery protocol detail, plugin console commands/CVars/flags, screenshot & capture paths, MCP Inspector debugging, extending with custom Python/C++ toolsets |
references/advanced-workflows.md | Sophisticated workflows, live-verified: ProgrammaticToolset batching, Blueprint DSL authoring loop (create→DSL→compile→spawn), PIE test sessions, Sequencer orientation (140 tools), LogsToolset self-debugging, automation testing, semantic asset search, config settings, per-situation decision table |
references/scene-craft.md | Numeric cheat sheet: physical light intensities, color temperatures, exposure/EV100, fog densities, mood recipes (noon/golden hour/overcast/night/interior), scale tables, content path conventions |
references/recipes.md | End-to-end worked builds with exact call sequences |
references/pitfalls.md | Setup, runtime, and workflow pitfalls with fixes — read before your first session and whenever something misbehaves |
mcp_unreal_engine_* tools = wrong order.mcp_servers.unreal-engine.timeout in ~/.ouro/config.yaml for
render/import-heavy sessions.ModelContextProtocol.RefreshTools in the editor console
and re-list_toolsets. New C++ UFUNCTIONs need a full editor restart —
Live Coding won't surface them.describe_toolset over memory, including this skill's
examples. When docs and the live schema disagree, the live schema wins.list_toolsets returns toolsets at session start (connection healthy)