inngest

Inngest expert for serverless-first background jobs, event-driven workflows, and durable execution without managing queues or workers. USE WHEN building background jobs, durable multi-step workflows, fan-out, or scheduled functions on Inngest instead of running your own queue/worker infra.

Zur Installation springen

Repository: Sheshiyer/skill-clusters
Letzte Quellaktivität: 5. Juni 2026 um 17:21
Erkannte Sprache von SKILL.md: Englisch
Sterne: 0
Forks: 1

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.

npx skills add https://github.com/Sheshiyer/skill-clusters --skill inngest

Der Befehl bleibt in einer Zeile. Scrollen Sie horizontal, um ihn vor dem Kopieren vollständig zu prüfen.

Sie bevorzugen eine lokale Kopie? Laden Sie die Dateien herunter, die SkillsMP derzeit vorliegen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

SKILL.md

Quellanweisungen · Schreibgeschützte Vorschau

Zurück zur Suche Zurück zur Installation

arcplume

Arcplume runs Grok through the Grok Build CLI's own OAuth-authenticated session (grok login) for image generation, with strict preflight validation, secret-safe handling, and headless CLI-driven execution -- no separate XAI_API_KEY billing. Video falls back to the billed xAI API. USE WHEN a user wants to generate an image via a locally logged-in Grok Build CLI session, e.g. 'generate an image with grok', 'use grok build', or 'use my logged-in grok session'.

2026-07-07

selemene-core

Shared reference for the Selemene cluster: the two report surfaces (deterministic Rust reports vs. narrative witness-pipeline readings), the @selemene/bridge CLI contract, the output manifest format, and non-prescriptive witnessing tone. USE WHEN deciding which Selemene surface to invoke or when routing between birth/compatibility/transit reports and solo/dyadic readings.

2026-07-07

selemene-orchestrator

Route Selemene Engine tasks to the right surface: deterministic reports (birth/compatibility/transit) via selemene-core and the @selemene/bridge CLI, or narrative witness readings via selemene-report. USE WHEN the user wants anything under the Selemene/Noesis umbrella but has not named the exact surface.

2026-07-07

Alle aus diesem Repository ansehen

// Step 2: Send welcome email
await step.run('send-email', async () => {
  await resend.emails.send({
    to: user.email,
    subject: 'Welcome!',
    template: 'welcome',
  });
});

// Step 3: Wait 24 hours, then send tips
await step.sleep('wait-for-tips', '24h');

await step.run('send-tips', async () => {
  await resend.emails.send({
    to: user.email,
    subject: 'Getting Started Tips',
    template: 'tips',
  });
});

// Parallel steps - both run simultaneously
const [inventory, payment] = await Promise.all([
  step.run('check-inventory', () => checkInventory(orderId)),
  step.run('validate-payment', () => validatePayment(orderId)),
]);

if (!inventory.available) {
  // Send event instead of direct call (fan-out pattern)
  await step.sendEvent('notify-backorder', {
    name: 'order/backordered',
    data: { orderId, items: inventory.missing },
  });
  return { status: 'backordered' };
}

// Process payment
const charge = await step.run('charge-payment', async () => {
  return await stripe.charges.create({
    amount: event.data.total,
    customer: payment.customerId,
  });
});

// Ship order
await step.run('ship-order', () => fulfillment.ship(orderId));

return { status: 'completed', chargeId: charge.id };

// Send to each user (creates child events)
await step.sendEvent(
  'send-digests',
  users.map(user => ({
    name: 'digest/send',
    data: { userId: user.id },
  }))
);

return { sent: users.length };

switch (type) {
  case 'checkout.session.completed':
    await step.run('fulfill-order', async () => {
      await fulfillOrder(data.session.id);
    });
    break;

  case 'customer.subscription.deleted':
    await step.run('cancel-subscription', async () => {
      await cancelSubscription(data.subscription.id);
    });
    break;
}

// Step 2: Chunk for embedding
const chunks = await step.run('chunk-text', async () => {
  return chunkText(text, { maxTokens: 500 });
});

// Step 3: Generate embeddings (API rate limited)
const embeddings = await step.run('generate-embeddings', async () => {
  return await openai.embeddings.create({
    model: 'text-embedding-3-small',
    input: chunks,
  });
});

// Step 4: Store in vector DB
await step.run('store-vectors', async () => {
  await vectorDb.upsert({
    vectors: embeddings.data.map((e, i) => ({
      id: `${event.data.documentId}-${i}`,
      values: e.embedding,
      metadata: { chunk: chunks[i] },
    })),
  });
});

return { chunks: chunks.length, status: 'indexed' };

1. Define Inngest functions (inngest)
2. Set up serve handler in Next.js (nextjs-app-router)
3. Configure function timeouts (vercel-deployment)
4. Deploy and test (vercel-deployment)

1. Design AI workflow steps (ai-agents-architect)
2. Implement with Inngest durability (inngest)
3. Store results in database (supabase-backend)
4. Handle retries for API failures (inngest)

1. Receive webhook (backend)
2. Send to Inngest with idempotency (inngest)
3. Process payment logic (stripe-integration)
4. Update application state (backend)

1. Trigger event from user action (inngest)
2. Schedule drip emails with step.sleep (inngest)
3. Send emails with retry (email-systems)
4. Track email status (supabase-backend)

1. Define cron triggers (inngest)
2. Implement processing logic (backend)
3. Aggregate and report data (analytics-architecture)
4. Handle failures with alerting (inngest)

name	inngest
description	Inngest expert for serverless-first background jobs, event-driven workflows, and durable execution without managing queues or workers. USE WHEN building background jobs, durable multi-step workflows, fan-out, or scheduled functions on Inngest instead of running your own queue/worker infra.
cluster	devops-infra
version	1.0.0
origin	antigravity-awesome-skills (MIT)
risk	none
source	vibeship-spawner-skills (Apache 2.0)
date_added	"2026-02-27T00:00:00.000Z"

name	inngest
description	Inngest expert for serverless-first background jobs, event-driven workflows, and durable execution without managing queues or workers. USE WHEN building background jobs, durable multi-step workflows, fan-out, or scheduled functions on Inngest instead of running your own queue/worker infra.
cluster	devops-infra
version	1.0.0
origin	antigravity-awesome-skills (MIT)
risk	none
source	vibeship-spawner-skills (Apache 2.0)
date_added	"2026-02-27T00:00:00.000Z"

inngest

Installationsoptionen

Quelldateien prüfen

Inngest Integration

Inngest Integration

Principles

Capabilities

Scope

Tooling

Core

Frameworks

Deployment

Patterns

Patterns

Basic Function Setup

Multi-Step Workflow

Scheduled/Cron Functions

Webhook Handler with Idempotency

AI Pipeline with Long Processing

Validation Checks

Inngest serve handler present

Functions registered with serve

Step.run has descriptive name

waitForEvent has timeout

Function has concurrency limit

Event types defined

Function has unique ID

Sleep uses duration string

Retry policy configured

Idempotency key for payment functions

Collaboration

Delegation Triggers

Vercel Background Jobs

AI Pipeline

Webhook Processing

Email Automation

Scheduled Tasks

Related Skills

When to Use

Limitations

inngest

Quellinformationen

Installationsoptionen

Quelldateien prüfen

Mehr aus diesem Repository

Mehr aus diesem Repository

Inngest Integration

Inngest Integration

Principles

Capabilities

Scope

Tooling

Core

Frameworks

Deployment

Patterns

Patterns

Basic Function Setup

Multi-Step Workflow

Scheduled/Cron Functions

Webhook Handler with Idempotency

AI Pipeline with Long Processing

Validation Checks

Inngest serve handler present

Functions registered with serve

Step.run has descriptive name

waitForEvent has timeout

Function has concurrency limit

Event types defined

Function has unique ID

Sleep uses duration string

Retry policy configured

Idempotency key for payment functions

Collaboration

Delegation Triggers

Vercel Background Jobs

AI Pipeline

Webhook Processing

Email Automation

Scheduled Tasks

Related Skills

When to Use

Limitations