Token导航 LogoToken导航

Agent Skill · 前端设计

ue-async-threading(ue 异步线程)

ue-async-threading 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

ue-async-threading 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为接触敏感数据;许可证信息还不明确,第三方扫描已通过,按安装量在前端设计类的 10,216 个 Skill 里排第 2,872。

总安装 1,811周安装 77GitHub Stars 125下载 634核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:ue-async-threading(ue 异步线程)
来源仓库:https://github.com/quodsoler/unreal-engine-skills
仓库路径:skills/ue-async-threading
安装命令:
npx skills add https://github.com/quodsoler/unreal-engine-skills --skill ue-async-threading
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/quodsoler/unreal-engine-skills --skill ue-async-threading

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

ue-async-threading 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。适合围绕仓库状态、代码变更或协作事项进行整理和分析。可结合来源仓库和原始 README 核验具体用法,提升协作效率。

安装命令:npx skills add https://github.com/quodsoler/unreal-engine-skills --skill ue-async-threading。建议确认权限范围和维护状态,避免触发联网、命令执行或文件读写。

来源仓库内路径:skills/ue-async-threading

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/quodsoler/unreal-engine-skills --skill ue-asyn…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

ue-async-threading 怎么安装?

在终端执行 npx skills add https://github.com/quodsoler/unreal-engine-skills --skill ue-async-threadin…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

ue-async-threading 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

ue-async-threading 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

ue-async-threading 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

ue-async-threading 用的人多吗?

公开数据是累计安装 1,811 次,近一周安装 77 次,下载 634 次,GitHub 125 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

ue-async-threading 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

前端设计类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
frontend-design

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
ue-async-threading

ue 异步线程 · 本页

1,811125接触敏感数据未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

UE Async and Threading

You are an expert in Unreal Engine's threading model, async task systems, and concurrent programming patterns.

Context Check

Read .agents/ue-project-context.md before proceeding. Engine version matters: UE::Tasks::Launch is the modern preferred API (UE 5.0+), while FAsyncTask and TaskGraph remain fully supported. Determine: What work needs to be offloaded? Is UObject access required? What latency/throughput tradeoff is acceptable?

Information Gathering

Ask the user if unclear:

  • Offload type — CPU-bound computation, I/O wait, or periodic background work?
  • UObject interaction — Does the background work need to read/write UObject state?
  • Lifetime — One-shot task, recurring work, or long-lived thread?
  • Result delivery — Fire-and-forget, or does the game thread need results back?

UE Threading Model

UE runs several named threads plus a scalable worker pool. Understanding which thread owns what prevents the most common threading bugs.

Named threads:

  • Game Thread — All UObject access, Blueprint execution, gameplay logic. Check with IsInGameThread().
  • Render Thread — Render commands, scene proxy updates. IsInRenderingThread().
  • RHI Thread — GPU command submission (platform-dependent).
  • Worker Threads — Unnamed pool threads for task dispatch. Count scales with CPU cores.

The golden rule: UObjects are game-thread-only. No UPROPERTY reads, no UFUNCTION calls, no GetWorld(), no spawning from background threads. Violating this causes intermittent crashes that depend on GC timing and are extremely difficult to diagnose.


Pattern Selection Guide

Choose the simplest API that fits your needs.

PatternBest ForLifetimeResult?
AsyncTask(GameThread, Lambda)Dispatch to game thread from backgroundOne-shotNo
UE::Tasks::LaunchGeneral async work (preferred, UE5+)One-shotTTask<T>
Async(EAsyncExecution, Lambda)Flexible dispatch with TFutureOne-shotTFuture<T>
FAsyncTask<T>Reusable pooled work unitsReusableVia GetTask()
FAutoDeleteAsyncTask<T>Fire-and-forget pooled workOne-shotNo
TGraphTask<T>Complex dependency graphsOne-shotFGraphEvent
ParallelForData-parallel loopsBlockingNo
FRunnable + FRunnableThreadLong-lived dedicated threadsPersistentManual

FRunnable and FRunnableThread

Use FRunnable only when you need a dedicated, long-lived thread -- a socket listener, a file watcher, or a continuous processing loop. For one-shot work, prefer UE::Tasks::Launch or FAsyncTask.

Lifecycle: Init() (new thread) -> Run() (new thread) -> Exit() (new thread, after Run returns). Stop() is called externally to request shutdown.

FRunnableThread::Create signature: static FRunnableThread* Create(FRunnable*, const TCHAR* ThreadName, uint32 StackSize = 0, EThreadPriority = TPri_Normal, uint64 AffinityMask, EThreadCreateFlags).

Key points: Stop() signals the thread -- it does not block. Kill(true) calls Stop() then waits for completion. Always delete the FRunnableThread* after Kill. Use std::atomic<bool> bShouldStop in Run() loop, set it in Stop().

See references/threading-patterns.md for a complete FRunnable subclass template with proper shutdown.


FAsyncTask and FAutoDeleteAsyncTask

For reusable work units on the engine thread pool (GThreadPool). Subclass FNonAbandonableTask and implement DoWork() + GetStatId().

class FMyComputeTask : public FNonAbandonableTask
{
    friend class FAsyncTask<FMyComputeTask>;
    int32 Result = 0;
    TArray<int32> InputData;

    FMyComputeTask(TArray<int32> InData) : InputData(MoveTemp(InData)) {}

    void DoWork()
    {
        for (int32 Val : InputData) { Result += Val; }
    }

    FORCEINLINE TStatId GetStatId() const
    {
        RETURN_QUICK_DECLARE_CYCLE_STAT(FMyComputeTask, STATGROUP_ThreadPoolAsyncTasks);
    }
};

Usage:

// Reusable — you manage lifetime
auto* Task = new FAsyncTask<FMyComputeTask>(MoveTemp(Data));
Task->StartBackgroundTask();          // dispatches to GThreadPool
Task->EnsureCompletion();             // blocks or runs inline if not started
int32 R = Task->GetTask().Result;
delete Task;

// Fire-and-forget — auto-deletes on completion
(new FAutoDeleteAsyncTask<FMyComputeTask>(MoveTemp(Data)))->StartBackgroundTask();

IsWorkDone() is the non-blocking completion check. Cancel() prevents execution if not yet started. StartSynchronousTask() runs inline on the calling thread.


TaskGraph

For work with complex dependency chains. Each task declares prerequisites; the scheduler handles ordering.

class FMyGraphTask
{
public:
    FMyGraphTask(int32 InValue) : Value(InValue) {}

    static ESubsequentsMode::Type GetSubsequentsMode()
    { return ESubsequentsMode::TrackSubsequents; }

    ENamedThreads::Type GetDesiredThread()
    { return ENamedThreads::AnyThread; }

    TStatId GetStatId() const
    { RETURN_QUICK_DECLARE_CYCLE_STAT(FMyGraphTask, STATGROUP_TaskGraphTasks); }

    void DoTask(ENamedThreads::Type CurrentThread, const FGraphEventRef& MyCompletionGraphEvent)
    { /* work here */ }

private:
    int32 Value;
};

Dispatching with prerequisites:

FGraphEventArray Prerequisites;  // TArray<FGraphEventRef, TInlineAllocator<4>>
Prerequisites.Add(SomePriorEvent);

FGraphEventRef TaskEvent = TGraphTask<FMyGraphTask>::CreateTask(&Prerequisites)
    .ConstructAndDispatchWhenReady(42);  // args forwarded to constructor

FTaskGraphInterface::Get().WaitUntilTaskCompletes(TaskEvent, ENamedThreads::GameThread);

Quick dispatch (no custom class needed):

AsyncTask(ENamedThreads::GameThread, [this]()
{
    MyActor->UpdateHealth(NewValue); // safe — runs on game thread
});

UE::Tasks::Launch (Modern Preferred API)

Recommended for new code (UE 5.0+). Simpler syntax than TaskGraph, automatic thread pool dispatch, built-in chaining.

#include "Tasks/Task.h"

UE::Tasks::TTask<int32> Task = UE::Tasks::Launch(
    UE_SOURCE_LOCATION,
    []() { return ExpensiveComputation(); }
);
int32 Result = Task.GetResult(); // blocks until complete

// With prerequisites
UE::Tasks::TTask<FVector> TaskA = UE::Tasks::Launch(UE_SOURCE_LOCATION,
    []() { return ComputePosition(); });

UE::Tasks::TTask<void> TaskB = UE::Tasks::Launch(UE_SOURCE_LOCATION,
    [&TaskA]() { ProcessPosition(TaskA.GetResult()); },
    UE::Tasks::Prerequisites(TaskA)
);

TTask API: GetResult() blocks and returns result. IsCompleted() non-blocking. Wait() / Wait(FTimespan) for timed blocking. TryRetractAndExecute() runs inline if not yet started (work stealing).

FTaskEvent for manual synchronization -- call Trigger() to unblock dependent tasks.


Async, TFuture, and TPromise

Async() is the most flexible one-shot dispatch. Returns TFuture<T> with execution context control.

TFuture<FMyResult> Future = Async(EAsyncExecution::ThreadPool,
    []() -> FMyResult { return ComputeResult(); },
    []() { /* completion callback — runs on unspecified thread */ }
);
FMyResult R = Future.Get(); // blocks, does NOT invalidate (unlike std::future)

EAsyncExecution modes:

ModeThread
TaskGraphWorker via TaskGraph
TaskGraphMainThreadGame thread via TaskGraph
ThreadNew dedicated thread
ThreadPoolGThreadPool worker
LargeThreadPoolGLargeThreadPool (WITH_EDITOR only)

Convenience: AsyncPool(GThreadPool, Lambda), AsyncThread(Lambda, StackSize, Priority).

TFuture API

Key difference from std::future: Get() does not invalidate. Call it multiple times safely. Consume() invalidates like std::future::get().

  • IsReady() -- non-blocking check
  • Wait() / WaitFor(FTimespan) -- block without consuming
  • Then(Continuation) / Next(Continuation) -- chaining, continuation runs on any thread
  • Share() -- convert to shared future

TPromise

For producer-consumer patterns where producing and consuming sides are decoupled.

TPromise<FMyData> Promise;
TFuture<FMyData> Future = Promise.GetFuture(); // call once

Async(EAsyncExecution::ThreadPool, [P = MoveTemp(Promise)]() mutable
{
    P.SetValue(GenerateData()); // or EmplaceValue()
});

FMyData Result = Future.Get(); // blocks on game thread

ParallelFor

For data-parallel loops where each iteration is independent. The calling thread participates -- ParallelFor blocks until all iterations complete.

ParallelFor(Meshes.Num(), [&Meshes](int32 Index)
{
    ProcessMesh(Meshes[Index]);
});

// With MinBatchSize — prevents overhead for small workloads
ParallelFor(TEXT("ProcessMeshes"), Meshes.Num(), 64,
    [&Meshes](int32 Index) { ProcessMesh(Meshes[Index]); }
);

EParallelForFlags:

FlagValueEffect
None0Default behavior
ForceSingleThread1Debug: run sequentially
Unbalanced2Iterations have variable cost
PumpRenderingThread4Pump render commands while waiting
BackgroundPriority8Lower priority for workers

ParallelForWithTaskContext provides a per-worker context object -- use when workers need scratch memory to avoid per-iteration allocation.


Game Thread Safety

Threading bugs in UE are silent -- they corrupt state, cause GC races, and produce bugs that only reproduce under load. See references/thread-safety-guide.md for complete patterns.

UObject Access Rules

  1. All UObject access must happen on the game thread. No reads, writes, or function calls from background threads.
  2. GC can destroy UObjects between ticks. A raw UObject* captured in a lambda may be dangling by execution time.
  3. Spawning, destroying, modifying components -- game thread only.

Safe Dispatch Pattern

AsyncTask(ENamedThreads::GameThread, [WeakActor = TWeakObjectPtr<AActor>(MyActor)]()
{
    if (AActor* Actor = WeakActor.Get()) // nullptr if GC'd
    {
        Actor->UpdateFromBackgroundWork(NewData);
    }
});

Always capture TWeakObjectPtr, never raw UObject*. For non-UObject shared data, use TSharedPtr<T, ESPMode::ThreadSafe> -- the default ESPMode::NotThreadSafe has non-atomic refcounting.


Synchronization Primitives

FCriticalSection (Recursive Mutex)

FCriticalSection is UE::FPlatformRecursiveMutex. Same thread can lock multiple times without deadlocking.

FCriticalSection DataLock;
void AddPosition(const FVector& Pos)
{
    FScopeLock Lock(&DataLock);  // RAII — unlocks on scope exit
    SharedPositions.Add(Pos);
}

FRWLock (Read-Write Lock)

Multiple readers OR one exclusive writer. FRWLock is not recursive -- do not nest.

FRWLock CacheLock;
FVector Read(FName Key)  { FReadScopeLock  RL(CacheLock); return Cache.FindRef(Key); }
void Write(FName K, FVector V) { FWriteScopeLock WL(CacheLock); Cache.Add(K, V); }

FEventRef and Atomics

FEventRef is the RAII wrapper for thread signaling. Prefer over raw FEvent*.

FEventRef WorkReady(EEventMode::AutoReset);
WorkReady->Trigger(); // producer signals
WorkReady->Wait();    // consumer blocks

FThreadSafeCounter and FThreadSafeBool are deprecated -- use std::atomic<int32> and std::atomic<bool> directly.


TQueue (Lock-Free Queue)

Thread-safe queue for producer-consumer without locks.

TQueue<FMyMessage, EQueueMode::Mpsc> MessageQueue;

// Producer (any thread)
MessageQueue.Enqueue(FMyMessage{...});

// Consumer (game thread tick)
FMyMessage Msg;
while (MessageQueue.Dequeue(Msg)) { ProcessMessage(Msg); }

Spsc -- single-producer, single-consumer (slightly faster). Mpsc -- multiple-producer, single-consumer (most common). Peek() reads without dequeuing.


Common Mistakes

Accessing UObject from background thread -- dispatch results back:

// WRONG — UObject access off game thread
Async(EAsyncExecution::ThreadPool, [this]()
{ MyActor->Health = ComputeNewHealth(); });

// RIGHT — compute off-thread, apply on game thread via weak pointer
Async(EAsyncExecution::ThreadPool, [WeakActor = TWeakObjectPtr<AActor>(MyActor)]()
{
    float NewHealth = ComputeNewHealth();
    AsyncTask(ENamedThreads::GameThread, [WeakActor, NewHealth]()
    { if (AActor* A = WeakActor.Get()) { A->SetHealth(NewHealth); } });
});

TSharedPtr with default ESPMode across threads:

// WRONG — non-atomic refcount
auto Data = MakeShared<FMyData>();
// RIGHT
auto Data = MakeShared<FMyData, ESPMode::ThreadSafe>();

FRWLock nested acquisition -- deadlock:

// WRONG — FRWLock is NOT recursive
FReadScopeLock Outer(Lock);
FReadScopeLock Inner(Lock);  // DEADLOCK on some platforms
// RIGHT — acquire once, do all reads, release

ParallelFor with shared mutable state:

// WRONG — concurrent writes
int32 Total = 0;
ParallelFor(Data.Num(), [&](int32 i) { Total += Data[i]; });
// RIGHT — atomic accumulation
std::atomic<int32> Total{0};
ParallelFor(Data.Num(), [&](int32 i)
{ Total.fetch_add(Data[i], std::memory_order_relaxed); });

Related Skills

  • ue-cpp-foundations -- TSharedPtr, TWeakObjectPtr, GC lifetime, smart pointer rules
  • ue-gameplay-framework -- game thread tick flow, actor lifecycle ordering
  • ue-networking-replication -- RPC dispatch threads, replication callbacks
  • ue-data-assets-tables -- FStreamableManager async loading, soft references

平台分布

Codex

38.45%
按下载量换算244

Claude

28.03%
按下载量换算178

Cursor

18.51%
按下载量换算117

Gemini CLI

10.63%
按下载量换算67

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills