vast-data/data-engine-skills

2Stars on the repository
8Mods indexed here, across every type
4mo agoLast push, which is what freshness is scored on
noneNo LICENSE: all rights reserved, so bodies are not copied

create-function

01

vast-data/data-engine-skills

Skill Claude CodeCodex

Create a new VAST DataEngine serverless function with proper project structure, handler pattern, and dependencies. Use when scaffolding a new function from scratch or converting existing code into a DataEngine function.

2 4mo ago A 43 tokens

function-manifest

02

vast-data/data-engine-skills

Skill Claude CodeCodex

Create and manage VAST DataEngine function manifests for registering, updating, and deploying function images using the vastde CLI. Use when you need to register a built function image with DataEngine or update an existing function.

2 4mo ago A 47 tokens

vast-data/data-engine-skills

Skill Claude CodeCodex

Build, run, and test VAST DataEngine functions locally using vastde CLI. Use when you need to build a function image, run it as a local container, or send test CloudEvents for development and debugging.

2 4mo ago A 50 tokens

vast-data/data-engine-skills

Skill Claude CodeCodex

Deploy a VAST DataEngine pipeline, check its status, view logs, traces, and metrics. Use when deploying a pipeline to Kubernetes, monitoring execution, or debugging function failures.

2 4mo ago A 43 tokens

pipeline-manifest

05

vast-data/data-engine-skills

Skill Claude CodeCodex

Create VAST DataEngine pipeline manifests that wire triggers, functions, and secrets into deployable data processing workflows. Use when building or modifying a pipeline configuration YAML file.

2 4mo ago A 37 tokens

trigger-manifest

06

vast-data/data-engine-skills

Skill Claude CodeCodex

Create VAST DataEngine trigger manifests for S3 element triggers and schedule (cron) triggers using the vastde CLI. Use when setting up event sources that invoke DataEngine functions.

2 4mo ago A 40 tokens

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: