Agent UI
aiskillstore/marketplace
Batteries-included agent component for React/Next.js from ui.inference.sh.
A skill your agent uses when streaming durable workflow updates to a UI in real time — live order status pages that animate as steps complete, AI agent token streaming from a function to the…
$ npx skills add Asymmetric-al/core --skill inngest-realtime -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Asymmetric-al/core inngest-realtime --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Asymmetric-al/core.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/inngest-realtime .claude/skills/inngest-realtime && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "inngest-realtime" agent skill from https://github.com/Asymmetric-al/core/tree/develop/.agents/skills/inngest-realtime into .claude/skills/inngest-realtime/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inngest-realtime", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Asymmetric-al/core/tree/develop/.agents/skills/inngest-realtimeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Asymmetric-al/core --skill inngest-realtime -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Asymmetric-al/core inngest-realtime --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Asymmetric-al/core.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/inngest-realtime .agents/skills/inngest-realtime && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "inngest-realtime" agent skill from https://github.com/Asymmetric-al/core/tree/develop/.agents/skills/inngest-realtime into .agents/skills/inngest-realtime/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inngest-realtime", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Asymmetric-al/core --skill inngest-realtime -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Asymmetric-al/core inngest-realtime --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Asymmetric-al/core.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/inngest-realtime .cursor/skills/inngest-realtime && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "inngest-realtime" agent skill from https://github.com/Asymmetric-al/core/tree/develop/.agents/skills/inngest-realtime into .cursor/skills/inngest-realtime/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inngest-realtime", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Asymmetric-al/core.git --path .agents/skills/inngest-realtime--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Asymmetric-al/core --skill inngest-realtime -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Asymmetric-al/core inngest-realtime --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Asymmetric-al/core.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/inngest-realtime .gemini/skills/inngest-realtime && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "inngest-realtime" agent skill from https://github.com/Asymmetric-al/core/tree/develop/.agents/skills/inngest-realtime into .gemini/skills/inngest-realtime/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inngest-realtime", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Asymmetric-al/core inngest-realtimeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Asymmetric-al/core --skill inngest-realtime -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Asymmetric-al/core.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/inngest-realtime .github/skills/inngest-realtime && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "inngest-realtime" agent skill from https://github.com/Asymmetric-al/core/tree/develop/.agents/skills/inngest-realtime into .github/skills/inngest-realtime/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inngest-realtime", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Asymmetric-al/core --skill inngest-realtime -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Asymmetric-al/core inngest-realtime --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Asymmetric-al/core.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/inngest-realtime .opencode/skills/inngest-realtime && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "inngest-realtime" agent skill from https://github.com/Asymmetric-al/core/tree/develop/.agents/skills/inngest-realtime into .opencode/skills/inngest-realtime/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inngest-realtime", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
inngest-realtimeA skill your agent uses when streaming durable workflow updates to a UI in real time — live order status pages that animate as steps complete, AI agent token streaming from a function to the…
Inngest Realtime is an agent skill from Asymmetric-al/core. Use when streaming durable workflow updates to a UI in real time — live order status pages that animate as steps complete, AI agent token streaming from a function to the browser, log tailing for long-running jobs, or human-in-the-loop approval flows that publish a prompt and wait for a user reply. Covers Inngest v4 native realtime: defining typed channels, publishing from inside step.run, minting subscription tokens via server actions, and consuming the stream from React/Next.js client components.
Its SKILL.md is about 5.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Human-in-the-loop approvals. It works with Next.js, React and npm. The repository describes itself as: A high-performance, enterprise-grade Next.js 16 application for mission-focused non-profit organizations. Built for high impact teams. The licence is AGPL-3.0.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit c30c8ff. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
npmnpxFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
inngest.comFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
INNGEST_SIGNING_KEYINNGEST_EVENT_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Inngest Realtime loads about 5.3k tokens when it runs. Until then it costs about 130 tokens; SKILL.md has 1,366 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- `INNGEST_DEV=1` set in `.env.local` for local development (without it, the SDK demands cloud signing keys and 401s onl realtime operations 401 / 500. Add to `.env.local`. Hard restart the dev server (Next.js does not hot-reload `.env.locAutomated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from Asymmetric-al/core at commit c30c8ff, republished under its AGPL-3.0 licence (© Asymmetric-al). 1,366 words, ~5,263 tokens.
.claude/skills/inngest-realtime/SKILL.md (or your agent's skills folder).Stream updates from durable Inngest functions to live UIs. Use channels and topics to broadcast progress, render workflow execution as it happens, or build bi-directional human-in-the-loop flows.
These skills are focused on TypeScript. For Python or Go, refer to the Inngest documentation for language-specific guidance. Core concepts apply across all languages.
⚠ CRITICAL: v3 vs v4 package selection
Realtime in Inngest v4 lives at the SDK subpath
inngest/realtime. The standalone@inngest/realtimenpm package is a v3-era package and is NOT compatible withinngest@4.x. If your project is on v4 (the npm default), do not install@inngest/realtime. Use the imports below.Symptoms of using the wrong package on v4:
TypeError: Cls is not a constructoron everyPUT /api/inngest, 401 on subscription tokens, type incompatibility onnew Inngest({ middleware: [...] }). Verify yourpackage.jsonshows"inngest": "^4.x"before reading further.
npm install inngest) — see the inngest-setup skillINNGEST_DEV=1 set in .env.local for local development (without it, the SDK demands cloud signing keys and 401s on token requests)npx inngest-cli@latest dev)zod for schema validation on topics| Problem shape | Pattern |
|---|---|
| Order status page animates as durable workflow steps complete | Per-run channel, publish per step, client subscribes |
| AI agent streams tokens to a chat UI | Per-conversation channel, publish chunks, stream to browser |
| Log tail for a long-running job | Single channel, log topic, append to UI |
| Human-in-the-loop approval | Channel + waitForEvent, publish prompt, wait for response |
| Admin dashboard with live order list | Global admin channel, fan-out from each function |
Three pieces:
step.realtime.publish between steps to wrap a durable publish, or inngest.realtime.publish inside step.run because you're already inside a memoized step. See "Which publish method to use" below.useRealtime hook (or the lower-level subscribe() API for non-React consumers).Channels are pure data — no class hierarchy, no zod runtime required (but recommended for type safety). Define them once and import where needed.
// src/inngest/channels.ts
import { channel } from "inngest/realtime";
import { z } from "zod";
// Per-run channel: each fulfill-order run publishes step updates to its own channel.
export const orderChannel = channel({
name: (orderId: string) => `order:${orderId}`,
topics: {
step: {
schema: z.object({
name: z.string(),
status: z.enum(["running", "complete", "failed"]),
output: z.record(z.string(), z.unknown()).optional(),
ts: z.number(),
}),
},
},
});
// Global admin channel: fan-out for cross-cutting visibility.
export const adminChannel = channel({
name: "admin",
topics: {
order: {
schema: z.object({
orderId: z.string(),
step: z.string(),
status: z.enum(["running", "complete", "failed"]),
ts: z.number(),
}),
},
},
});Two channel name shapes:
name: 'admin' — static channel, accessed as adminChannel.order (topic ref)name: (id) => 'channel:${id}' — parametric, accessed as orderChannel(id).step (call the channel def with the id, then access topic)Inngest v4 ships realtime support natively — no middleware required. But where you call publish matters: it determines whether the publish is durable, and it's the most common place to get realtime wrong.
| Where you are | Use this | Why |
|---|---|---|
Outside a step (top-level handler code, between step.run calls) | step.realtime.publish(id, topicRef, data) | Wraps the publish in its own step so it's durable, deduplicated by id, and retry-safe. |
Inside a step (inside the callback passed to step.run) | inngest.realtime.publish(topicRef, data) | You're already inside a memoized step. step.realtime.publish would create a step inside a step. The bare client publish is the right call here. |
| Outside a function (one-off route, script, etc.) | inngest.realtime.publish(topicRef, data) | Allowed, but not retry-safe — your client receiver must handle duplicates. |
The 90% rule: if you're writing handler code and you reach for publish, use step.realtime.publish. If you're writing code inside a step.run block and you reach for publish, use inngest.realtime.publish.
// src/inngest/functions/fulfill-order.ts
import { inngest } from "../client";
import { orderChannel, adminChannel } from "../channels";
export const fulfillOrder = inngest.createFunction(
{
id: "fulfill-order",
retries: 3,
triggers: [{ event: "store/order.placed" }],
},
async ({ event, step }) => {
const { orderId, customerEmail, lineItems } = event.data;
// Outside any step.run — use step.realtime.publish for a durable wrapper.
const emit = async (
name: string,
status: "running" | "complete" | "failed",
output?: Record<string, unknown>,
) => {
const ts = Date.now();
await step.realtime.publish(
`emit-order-${name}-${status}`,
orderChannel(orderId).step,
{ name, status, output, ts },
);
await step.realtime.publish(
`emit-admin-${name}-${status}`,
adminChannel.order,
{ orderId, step: name, status, ts },
);
};
await emit("capture-payment", "running");
// Inside step.run — use inngest.realtime.publish (already in a memoized step).
const payment = await step.run("capture-payment", async () => {
const intent = await stripe.paymentIntents.create({
/* ... */
});
// Stream a partial update mid-step. No step-in-step wrapping needed.
await inngest.realtime.publish(orderChannel(orderId).step, {
name: "capture-payment",
status: "running",
output: { stage: "intent-created", intentId: intent.id },
ts: Date.now(),
});
return await stripe.paymentIntents.confirm(intent.id);
});
await emit("capture-payment", "complete", payment);
await emit("reserve-inventory", "running");
const inventory = await step.run("reserve-inventory", async () => {
// ...
});
await emit("reserve-inventory", "complete", inventory);
// ...
},
);Why no middleware: Earlier versions used @inngest/realtime's realtimeMiddleware() to inject a publish arg into the handler. v4 puts it on step.realtime and inngest.realtime directly.
In Next.js App Router, use a Server Action to securely mint a short-lived token for the React hook in Step 4. Without a token, clients can't subscribe.
// src/app/orders/[orderId]/actions.ts
"use server";
import { getClientSubscriptionToken } from "inngest/react";
import { inngest } from "@/inngest/client";
import { orderChannel } from "@/inngest/channels";
export async function fetchOrderSubscriptionToken(orderId: string) {
// ⚠ AUTHORIZATION GATE: verify the current user owns this orderId
// before minting a token. Channels are addressable by ID, so without
// an ownership check, anyone can subscribe to any order's stream by
// guessing IDs.
//
// const session = await getServerSession();
// if (!session) throw new Error('Unauthenticated');
// const order = await db.order.findUnique({ where: { id: orderId } });
// if (order?.userId !== session.userId) throw new Error('Forbidden');
return getClientSubscriptionToken(inngest, {
channel: orderChannel(orderId),
topics: ["step"],
});
}getClientSubscriptionToken from inngest/react returns a token shape that the useRealtime hook in Step 4 consumes directly. No ChannelInstance stripping needed — that gotcha only applies to the lower-level getSubscriptionToken + manual subscribe() path (see "Pattern: Manual subscribe" below).
useRealtime hookThe recommended consumer for React/Next.js is the useRealtime hook from inngest/react. It handles the subscription lifecycle, reconnect, type narrowing per topic, and cleanup.
// src/components/OrderStatusClient.tsx
'use client';
import { useRealtime } from 'inngest/react';
import { orderChannel } from '@/inngest/channels';
import { fetchOrderSubscriptionToken } from '@/app/orders/[orderId]/actions';
export function OrderStatusClient({ orderId }: { orderId: string }) {
const { messages, connectionStatus, error } = useRealtime({
channel: orderChannel(orderId),
topics: ['step'] as const,
token: () => fetchOrderSubscriptionToken(orderId),
});
if (error) return <div>Error: {error.message}</div>;
return (
<div>
<div>Status: {connectionStatus}</div>
<ul>
{messages.all.map((m, i) => (
<li key={i}>
{(m.data as { name: string }).name}: {(m.data as { status: string }).status}
</li>
))}
</ul>
</div>
);
}Useful options on the hook:
| Option | Default | Use it when |
|---|---|---|
enabled | true | Delay the subscription until you have an ID (e.g., enabled: !!runId). |
bufferInterval | 0 | Batch updates from a fast stream so React doesn't re-render per message. |
pauseOnHidden | false | Pause the stream when the tab isn't visible (saves bandwidth). |
autoCloseOnTerminal | true | Disconnect when the run completes — turn off to keep the stream open for fan-out channels. |
historyLimit | unbounded | Cap how many messages are retained in messages.all. |
The hook returns messages.byTopic (latest per topic), messages.all (full history), messages.last (most recent), and messages.delta (new since last render).
The useRealtime hook covers the React case. If you're not using React, or you need a custom subscription lifecycle (server-side streaming, background workers, custom protocols), use the lower-level subscribe() API directly.
// src/app/orders/[orderId]/actions.ts
"use server";
import { getSubscriptionToken } from "inngest/realtime";
import { inngest } from "@/inngest/client";
import { orderChannel } from "@/inngest/channels";
export async function fetchOrderSubscriptionTokenLowLevel(orderId: string) {
// ⚠ AUTHORIZATION GATE: same as Step 3 — verify ownership before minting.
const token = await getSubscriptionToken(inngest, {
channel: orderChannel(orderId),
topics: ["step"],
});
// ⚠ CRITICAL: strip the ChannelInstance from the response.
// getSubscriptionToken returns { channel: ChannelInstance, ... } where
// ChannelInstance contains zod schema methods (a class with prototypes).
// Next.js refuses to serialize classes across the server-action → client-component
// boundary, so return ONLY primitives.
return {
channel: orderChannel(orderId).name as string,
topics: ["step"] as const,
key: token.key,
apiBaseUrl: token.apiBaseUrl,
};
}// src/components/OrderStatusManual.tsx
"use client";
import * as React from "react";
import { subscribe } from "inngest/realtime";
import { fetchOrderSubscriptionTokenLowLevel } from "@/app/orders/[orderId]/actions";
export function OrderStatusManual({ orderId }: { orderId: string }) {
const [messages, setMessages] = React.useState<unknown[]>([]);
React.useEffect(() => {
let cancelled = false;
let sub: { close?: (reason?: string) => void } | undefined;
(async () => {
const token = await fetchOrderSubscriptionTokenLowLevel(orderId);
if (cancelled) return;
sub = await subscribe(
{
channel: token.channel,
topics: [...token.topics],
key: token.key,
apiBaseUrl: token.apiBaseUrl,
},
(message) => {
if (cancelled) return;
setMessages((prev) => [...prev, message.data]);
},
);
})();
return () => {
cancelled = true;
sub?.close?.("unmount");
};
}, [orderId]);
// ... render ...
}Subscribe inside a Next.js API route and pipe the stream to the client via SSE:
// src/app/api/orders/[orderId]/stream/route.ts
import { inngest } from "@/inngest/client";
import { subscribe } from "inngest/realtime";
import { orderChannel } from "@/inngest/channels";
export async function GET(
req: Request,
{ params }: { params: { orderId: string } },
) {
// ⚠ AUTHORIZATION GATE: same rule as the server-action token mint above.
// Authenticate the request and confirm the caller owns params.orderId
// before opening the SSE stream. Skipping this leaks every order's
// step events to anyone with a URL.
const stream = await subscribe({
app: inngest,
channel: orderChannel(params.orderId),
topics: ["step"],
});
return new Response(stream.getEncodedStream(), {
headers: {
"Content-Type": "text/event-stream",
"Cache-Control": "no-cache",
Connection: "keep-alive",
},
});
}Client consumes via fetch().getReader() rather than the subscribe() callback. Use this when you want the SSE behavior or when the client-side subscribe() API doesn't fit your component lifecycle.
Combine step.realtime.publish with step.waitForEvent:
import crypto from "crypto";
export const reviewWorkflow = inngest.createFunction(
{ id: "review-workflow", triggers: [{ event: "review/start" }] },
async ({ event, step }) => {
const confirmationId = await step.run("gen-id", () => crypto.randomUUID());
// Publish a prompt — the client subscribes and renders an approval UI
await step.realtime.publish("publish-prompt", reviewChannel.message, {
message: "Confirm to proceed?",
confirmationId,
});
// Wait up to 15 minutes for the user to send the matching event back
const confirmation = await step.waitForEvent("await-confirmation", {
event: "review/confirmation",
timeout: "15m",
if: `async.data.confirmationId == "${confirmationId}"`,
});
if (!confirmation) {
// user didn't respond — abort or escalate
return { decision: "timed_out" };
}
// continue workflow...
},
);The confirmationId links the published prompt to the matching reply, so the workflow knows which response to act on.
@inngest/realtime on v4The standalone @inngest/realtime package is for Inngest v3 only. On v4, all realtime APIs are in the SDK subpath inngest/realtime. Mixing them produces:
TypeError: Cls is not a constructor on PUT /api/inngest (v3 middleware class signature mismatch)Verify with: grep '"inngest"' package.json — if it's ^4.x, use inngest/realtime. Period.
getSubscriptionToken returns { channel: ChannelInstance, ... } where ChannelInstance has zod schema methods (a class). Next.js refuses to serialize classes across the server-action → client-component boundary. Strip to primitives before returning. See "Pattern: Manual subscribe" above.
This gotcha does not apply when you use getClientSubscriptionToken from inngest/react (Step 3 — the recommended path). That helper returns a serialization-safe shape directly.
INNGEST_DEV=1 is required for local devWithout it, the SDK assumes cloud mode and demands INNGEST_SIGNING_KEY + INNGEST_EVENT_KEY. All realtime operations 401 / 500. Add to .env.local. Hard restart the dev server (Next.js does not hot-reload .env.local changes).
If your published payload doesn't match the zod schema, the publish fails server-side. Subscriber receives nothing. Catch publish errors during step execution, or run with validate: false in subscribe() if you have a reason to skip schema validation client-side.
import { channel } from 'inngest/realtime' — channel definitionsimport { useRealtime, getClientSubscriptionToken } from 'inngest/react' — React hook + matching token helper (Step 3 + Step 4)import { getSubscriptionToken, subscribe } from 'inngest/realtime' — lower-level helpers for non-React or custom transportstep.realtime.publish(id, topicRef, data) — wraps in a durable stepstep.run: inngest.realtime.publish(topicRef, data) — already inside a memoized step, no wrapping neededinngest.realtime.publish(topicRef, data) — allowed but not retry-safesubscribe(token) returns a stream; subscribe(token, callback) invokes callback per messageChannelInstance → return { channel: string, topics, key, apiBaseUrl }. Not needed with getClientSubscriptionToken.These upstream Inngest instructions are vendored for agent tooling and integration work in this monorepo.
Use this skill when inngest-realtime matches the current Inngest task. If the
right skill is unclear, start with docs/ai/skills/inngest/SKILL.md.
inngest-brownfield-audit before changing existing app workflows or
fragile background work.AGENTS.md, repo
rulebooks, framework docs, and runtime evidence.INNGEST_* env
requirements out of agent-tooling-only changes.docs/ai/skills/inngest/references/upstream.md.© Asymmetric-al, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .agents/skills/inngest-realtime of Asymmetric-al/core.
Open the folder on GitHubat commit c30c8ff
Inngest Realtime next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Inngest Realtime this skillAsymmetric-al/core | 381 | — | ~5.3k | Automated safety check: Notes | AGPL-3.0 | |
| Agent UIaiskillstore/marketplace | 433 | 1 repos | ~883 | Automated safety check: Notes | None | |
| Convex Self Hostingwaynesutton/markdown-site | 627 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Build With SimplepdfSimplePDF/simplepdf-embed | 407 | — | ~7k | Automated safety check: Pass | MIT | |
| Tools UIaiskillstore/marketplace | 433 | 1 repos | ~990 | Automated safety check: Pass | None | |
| Javascript SDKaiskillstore/marketplace | 433 | 1 repos | ~3.3k | Automated safety check: Pass | None |
aiskillstore/marketplace
Batteries-included agent component for React/Next.js from ui.inference.sh.
waynesutton/markdown-site
Integrate Convex static self hosting into existing apps using the latest upstream instructions from get-convex/self-hosting every time.
SimplePDF/simplepdf-embed
Integrate SimplePDF into a web application for PDF viewing, editing, filling, signing, programmatic control, AI-agent interaction, human-in-the-loop form prefilling, submissions, webhooks, or…
aiskillstore/marketplace
Tool lifecycle UI components for React/Next.js from ui.inference.sh.
aiskillstore/marketplace
JavaScript/TypeScript SDK for inference.sh - run AI apps, build agents, integrate with all models.
greensock/gsap-skills
Shows how to run GSAP animations in React and Next.js with the useGSAP hook, refs, scoped selectors and automatic cleanup on unmount.
Asymmetric-al/core
Implement idempotency keys and handling to ensure operations can be safely retried without duplicate effects.
Asymmetric-al/core
Audit and fix accessibility in Core UI. An agent skill from Asymmetric-al/core.
Asymmetric-al/core
A skill your agent uses when building any system where email content triggers actions — AI agent inboxes, automated support handlers, email-to-task pipelines, or any workflow processing untrusted…
Asymmetric-al/core
Build modern, composable, and accessible React UI components following the components.build specification.
Asymmetric-al/core
Guides a one-question-at-a-time design interview, captures alignment in agent/EVE-BRIEF.md, then scaffolds and implements a runnable eve agent with verbose teaching comments.
Asymmetric-al/core
Design engineering principles and patterns for building polished, accessible web interfaces.
Categories
A skill your agent uses when streaming durable workflow updates to a UI in real time — live order status pages that animate as steps complete, AI agent token streaming from a function to the…. Inngest Realtime is an agent skill from Asymmetric-al/core. Use when streaming durable workflow updates to a UI in real time — live order status pages that animate as steps complete, AI agent token streaming from a function to the browser, log tailing for long-running jobs, or human-in-the-loop approval flows that publish a prompt and wait for a user reply.
Inngest Realtime fits situations like: streaming durable workflow updates to a UI in real time — live order status pages that animate as steps complete; AI agent token streaming from a function to the browser; log tailing for long-running jobs; human-in-the-loop approval flows that publish a prompt and wait for a user reply.
Run `npx skills add Asymmetric-al/core --skill inngest-realtime -a claude-code`. Or copy the skill folder (.agents/skills/inngest-realtime in Asymmetric-al/core) into .claude/skills/inngest-realtime in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Asymmetric-al/core --skill inngest-realtime -a codex`. Or copy the skill folder (.agents/skills/inngest-realtime in Asymmetric-al/core) into .agents/skills/inngest-realtime in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Asymmetric-al/core --skill inngest-realtime -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/inngest-realtime, .gemini/skills/inngest-realtime, .github/skills/inngest-realtime and .opencode/skills/inngest-realtime in your project.
Going by SKILL.md and its folder, Inngest Realtime needs the command-line tools its instructions call (npm and npx) and credentials named INNGEST_SIGNING_KEY and INNGEST_EVENT_KEY. Our summary lists: Python 3; Node.js.
SKILL.md names 1 domain. As links in the text: inngest.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Inngest Realtime is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 5.3k tokens (SKILL.md is roughly 21k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Inngest Realtime: Agent UI (aiskillstore/marketplace, 433 stars), Convex Self Hosting (waynesutton/markdown-site, 627 stars), Build With Simplepdf (SimplePDF/simplepdf-embed, 407 stars) and Tools UI (aiskillstore/marketplace, 433 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Asymmetric-al (a GitHub organization) maintains it in Asymmetric-al/core, which has 381 GitHub stars. The repository holds 43 skills in this directory. The repository was last updated on October 9, 2026.
Source: Asymmetric-al/core on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.