Chroma Vector Database
Orchestra-Research/AI-Research-SKILLs
Shows how to store documents and embeddings in Chroma, query them by similarity with metadata filters, and persist them to disk for RAG and semantic search projects.
Search a video library with natural language via the VSS Pipeline Manager - upload a video (POST /videos), generate its embeddings (POST /videos/search-embeddings/{id}), then run a query (POST…
$ npx skills add open-edge-platform/edge-ai-libraries --skill vss-search-index -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install open-edge-platform/edge-ai-libraries vss-search-index --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/open-edge-platform/edge-ai-libraries.git skills-src && mkdir -p .claude/skills && cp -r skills-src/sample-applications/video-search-and-summarization/.github/skills/vss-search-index .claude/skills/vss-search-index && 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 "vss-search-index" agent skill from https://github.com/open-edge-platform/edge-ai-libraries/tree/main/sample-applications/video-search-and-summarization/.github/skills/vss-search-index into .claude/skills/vss-search-index/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vss-search-index", 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/open-edge-platform/edge-ai-libraries/tree/main/sample-applications/video-search-and-summarization/.github/skills/vss-search-indexType 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 open-edge-platform/edge-ai-libraries --skill vss-search-index -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install open-edge-platform/edge-ai-libraries vss-search-index --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/open-edge-platform/edge-ai-libraries.git skills-src && mkdir -p .agents/skills && cp -r skills-src/sample-applications/video-search-and-summarization/.github/skills/vss-search-index .agents/skills/vss-search-index && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vss-search-index" agent skill from https://github.com/open-edge-platform/edge-ai-libraries/tree/main/sample-applications/video-search-and-summarization/.github/skills/vss-search-index into .agents/skills/vss-search-index/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vss-search-index", 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 open-edge-platform/edge-ai-libraries --skill vss-search-index -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install open-edge-platform/edge-ai-libraries vss-search-index --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/open-edge-platform/edge-ai-libraries.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/sample-applications/video-search-and-summarization/.github/skills/vss-search-index .cursor/skills/vss-search-index && 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 "vss-search-index" agent skill from https://github.com/open-edge-platform/edge-ai-libraries/tree/main/sample-applications/video-search-and-summarization/.github/skills/vss-search-index into .cursor/skills/vss-search-index/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vss-search-index", 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/open-edge-platform/edge-ai-libraries.git --path sample-applications/video-search-and-summarization/.github/skills/vss-search-index--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 open-edge-platform/edge-ai-libraries --skill vss-search-index -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install open-edge-platform/edge-ai-libraries vss-search-index --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/open-edge-platform/edge-ai-libraries.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/sample-applications/video-search-and-summarization/.github/skills/vss-search-index .gemini/skills/vss-search-index && 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 "vss-search-index" agent skill from https://github.com/open-edge-platform/edge-ai-libraries/tree/main/sample-applications/video-search-and-summarization/.github/skills/vss-search-index into .gemini/skills/vss-search-index/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vss-search-index", 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 open-edge-platform/edge-ai-libraries vss-search-indexInstalls 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 open-edge-platform/edge-ai-libraries --skill vss-search-index -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/open-edge-platform/edge-ai-libraries.git skills-src && mkdir -p .github/skills && cp -r skills-src/sample-applications/video-search-and-summarization/.github/skills/vss-search-index .github/skills/vss-search-index && 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 "vss-search-index" agent skill from https://github.com/open-edge-platform/edge-ai-libraries/tree/main/sample-applications/video-search-and-summarization/.github/skills/vss-search-index into .github/skills/vss-search-index/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vss-search-index", 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 open-edge-platform/edge-ai-libraries --skill vss-search-index -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install open-edge-platform/edge-ai-libraries vss-search-index --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/open-edge-platform/edge-ai-libraries.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/sample-applications/video-search-and-summarization/.github/skills/vss-search-index .opencode/skills/vss-search-index && 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 "vss-search-index" agent skill from https://github.com/open-edge-platform/edge-ai-libraries/tree/main/sample-applications/video-search-and-summarization/.github/skills/vss-search-index into .opencode/skills/vss-search-index/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vss-search-index", 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.
vss-search-indexSearch a video library with natural language via the VSS Pipeline Manager - upload a video (POST /videos), generate its embeddings (POST /videos/search-embeddings/{id}), then run a query (POST…
Vss Search Index is an agent skill from open-edge-platform/edge-ai-libraries. Search a video library with natural language via the VSS Pipeline Manager - upload a video (POST /videos), generate its embeddings (POST /videos/search-embeddings/{id}), then run a query (POST /search/query) with optional tag and time filters and read the ranked clip results. Use when the user says "search my videos", "find something in the videos", "when did X happen", or wants to ingest/index a video for search. Requires a search-capable deployment (--search, --dual, or --unified).
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 18 other files, including scripts and reference files (for example `benchmark/benchmark.json`, `benchmark/benchmark.md` and `evals/evals.json`).
It sits in AI & LLM Engineering, covering Embeddings. The repository describes itself as: Libraries, microservices, tools, and other reference software, supporting development of performance-optimized Edge AI applications. The licence is Apache-2.0.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 0ed0479. 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.
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
curljqbashgitFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use curl and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Vss Search Index loads about 2.2k tokens when it runs, and up to ~3.1k if it reads all its reference files. Until then it costs about 126 tokens; SKILL.md has 800 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 found no risky patterns in SKILL.md.
Automated 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); the scripts in this folder are not scanned.
The full file from open-edge-platform/edge-ai-libraries at commit 0ed0479, republished under its Apache-2.0 licence (© open-edge-platform). 800 words, ~2,209 tokens.
.claude/skills/vss-search-index/SKILL.md (or your agent's skills folder). This skill also uses 13 other files; get the full folder from GitHub.<!--
SPDX-FileCopyrightText: (C) 2026 Intel Corporation
SPDX-License-Identifier: Apache-2.0
-->
Natural-language search over the indexed video library. Call the documented API
yourself and report only observed responses. Endpoints use the nginx /manager
prefix.
Set HOST=http://${HOST_IP:-localhost}:${APP_HOST_PORT:-12345}.
The user may be away from the deployment, or $HOST may refuse connections. In
that case do not stall and do not invent responses. Answer with the exact
call sequence instead: full endpoint paths, request bodies / form fields, the
field each step carries over from the previous response, and the condition that
says a step is finished. State plainly that the commands were not executed.
Never end the answer by asking whether to run them.
This skill drives the Video Search & Summarization app through its real source files, so the VSS application must be present and you must run commands from its app root. Do this before anything else, and it works whether or not the VSS source is already in your workspace.
Run the bundled bootstrap. It resolves the app root in this order and prints it as the only line on stdout:
setup.sh, docker/, and
pipeline-manager/.git rev-parse --show-toplevel) and
check whether it holds sample-applications/video-search-and-summarization,
or is itself a VSS app root. This is what makes your own clone - or a fork -
work unchanged.${XDG_CACHE_HOME:-$HOME/.cache}/vss-src/edge-ai-libraries.If any of those hit, that checkout is reused and NO clone is performed. Only
when all three miss does it clone - and then only a shallow (--depth 1),
single-branch, sparse checkout of just
sample-applications/video-search-and-summarization from main:
# SKILL_DIR is THIS skill's own directory (shown to you when the skill loads);
# in-repo it is .github/skills/vss-search-index. Works the same if the skill is installed standalone.
SKILL_DIR=".github/skills/vss-search-index"
APP_ROOT="$(bash "$SKILL_DIR/scripts/vss-bootstrap.sh")"
cd "$APP_ROOT"Every command below assumes the working directory is this APP_ROOT. To pull
from a fork/branch or reuse a specific checkout dir, override VSS_REPO_URL,
VSS_REPO_BRANCH, or VSS_CLONE_DIR before running it. The bootstrap refuses
to overwrite an existing non-VSS clone destination.
Backend healthy and search enabled - probe first; if not, use the installed
vss-troubleshoot or vss-deploy skill by name:
curl -sf "$HOST/manager/health" >/dev/null && \
curl -s "$HOST/manager/app/features" | jq -e '(.search // .) == "FEATURE_ON"'POST /manager/videos - multipart/form-data, field name video, optional
comma-separated tags. File must be a streamable MP4 (server rejects otherwise).
curl -s -X POST "$HOST/manager/videos" \
-F "video=@/path/to/clip.mp4" \
-F "tags=outdoor,daytime" | jq .
# → { "videoId": "<VIDEO_ID>" }When the user says a video is already uploaded or just uploaded, list
videos first and match the exact real filename. Reuse that record's videoId;
do not search the local filesystem and upload another copy. Upload only when no
exact filename match exists and the user actually supplied a local file to
ingest.
The list response is an object
{ "videos": [...] }, not a bare array; name is a generated hash, so use
url / dataStore.fileName for the real filename:
curl -s "$HOST/manager/videos" | jq '.videos[] | {videoId, file: .dataStore.fileName}'
curl -s "$HOST/manager/videos/<VIDEO_ID>" | jq '.video' # single record is wrapped under .videoA video is not searchable until embeddings exist. Trigger them after upload (or to retry a failed run):
curl -s -X POST "$HOST/manager/videos/search-embeddings/<VIDEO_ID>" | jq .Wait for completion (re-check the video record) before querying.
One-off query - POST /manager/search/query. The response is an object
{ "results": [ { "query_id", "results": [ … ] } ] } - wrapped, NOT a bare
array - so the ranked clips are at .results[].results[]:
curl -s -X POST "$HOST/manager/search/query" \
-H 'Content-Type: application/json' \
-d '{
"query": "person wearing a hat",
"tags": "indoor",
"timeFilter": { "value": 7, "unit": "days" }
}' | jq -r '.results[].results[]
| "score=\(.metadata.relevance_score) clip=\(.metadata.segment_start)-\(.metadata.segment_end)s seek=\(.metadata.seek_timestamp)s video_id=\(.metadata.video_id)"'query (required): natural language.tags (optional): comma-separated, intersected with the query.timeFilter (optional): either relative (value + unit =
minutes|hours|days|weeks) or absolute (start/end ISO-8601). See
references/search-request.md.Each clip's metadata carries relevance_score (0..1; top hit can be exactly
1), video_id, video_url, segment_start/segment_end, seek_timestamp,
tags, and video_metadata (duration/fps). In search mode page_content is a
segment locator ("Video segment from Ns to Ms…"), not a caption.
Filename is NOT in the result - metadata has video_id but no video /
file_name. To show the clip's filename, join video_id against the video list
(.videos[].dataStore.fileName):
curl -s "$HOST/manager/videos" \
| jq '[.videos[] | {key:.videoId, value:.dataStore.fileName}] | from_entries' > /tmp/idmap.json
curl -s -X POST "$HOST/manager/search/query" -H 'Content-Type: application/json' \
-d '{ "query": "person wearing a hat" }' \
| jq --slurpfile m /tmp/idmap.json -r '.results[].results[]
| "score=\(.metadata.relevance_score) file=\($m[0][.metadata.video_id] // "?") clip=\(.metadata.segment_start)-\(.metadata.segment_end)s"'Present top hits with their filename + clip window + seek time.
If a filtered query returns no results, report the empty result as valid. Then
inspect the Manager video list for the requested tags and indexing readiness,
explain only what the observed state supports, and give a Manager-based next
step that preserves the same filters. To merge missing tags into an existing
record, use the documented embedding operation with a body such as
POST /manager/videos/search-embeddings/<VIDEO_ID> plus
{"tags":"indoor"}, then rerun the same filtered query.
Never present an unfiltered hit as though it satisfied the requested filter.
Tool arguments may not be visible to the user or evaluator. The final answer
must therefore name the public Pipeline Manager operations used (method and
/manager/... path), the important request fields, the observed status or
response, and any carried identifier such as videoId. Include the bootstrap
outcome (resolved app root and whether an existing checkout was reused) plus the
observed health and feature-preflight result. For searches, identify
the exact query/filter payload and say that ranked hits came from
POST /manager/search/query; for filename joins, say that the mapping came from
GET /manager/videos. If an id cannot be resolved, label it unresolved rather
than inventing a filename.
curl -s -X POST "$HOST/manager/search" -H 'Content-Type: application/json' \
-d '{"query":"forklift"}' | jq . # create a persistent query → queryId
curl -s "$HOST/manager/search/<QUERY_ID>" | jq . # fetch results
curl -s -X POST "$HOST/manager/search/<QUERY_ID>/refetch" | jq . # re-run
curl -s --request PATCH --json '{"watch":true}' \
"$HOST/manager/search/<QUERY_ID>/watch" | jq . # auto-refresh
curl -s "$HOST/manager/search/watched" | jq .
curl -s -X DELETE "$HOST/manager/search/<QUERY_ID>"© open-edge-platform, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 13 other files (scripts, references) in sample-applications/video-search-and-summarization/.github/skills/vss-search-index of open-edge-platform/edge-ai-libraries.
Open the folder on GitHubat commit 0ed0479
Vss Search Index 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 |
|---|---|---|---|---|---|---|
| Vss Search Index this skillopen-edge-platform/edge-ai-libraries | 171 | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Chroma Vector DatabaseOrchestra-Research/AI-Research-SKILLs | 13k | 7 repos | ~2.3k | Automated safety check: Pass | MIT | |
| SageMaker Serving Image Selectionhuggingface/skills | 11k | 1 repos | ~4.6k | Automated safety check: Pass | Apache-2.0 | |
| Codebase Managementgiancarloerra/SocratiCode | 3.3k | 1 repos | ~1.8k | Automated safety check: Pass | AGPL-3.0 | |
| CLIP Image-Text MatchingOrchestra-Research/AI-Research-SKILLs | 13k | 7 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Sentence-Transformers Training Routerhuggingface/skills | 11k | 1 repos | ~2.6k | Automated safety check: Pass | Apache-2.0 |
Orchestra-Research/AI-Research-SKILLs
Shows how to store documents and embeddings in Chroma, query them by similarity with metadata filters, and persist them to disk for RAG and semantic search projects.
huggingface/skills
Chooses the right serving container and current image URI for deploying a Hugging Face model to a SageMaker endpoint, preferring Hugging Face images over generic ones.
giancarloerra/SocratiCode
Set up, index, and manage SocratiCode codebase indexing. An agent skill from giancarloerra/SocratiCode.
Orchestra-Research/AI-Research-SKILLs
Explains OpenAI's CLIP model for zero-shot image classification, image-text similarity, semantic image search and content moderation, with install steps and code patterns.
huggingface/skills
Routes a sentence-transformers training task to the right model type and required reference docs and example scripts, covering bi-encoders, rerankers, sparse and multi-vector models.
rehan-remade/universal-modder
Build cross-game mashups and total conversions, the "Minecraft inside Elden Ring" or "skateboarding in MW2" kind.
open-edge-platform/edge-ai-libraries
Build a new time-series analytics use case on top of the deployed Time Series Analytics microservice — bring it up with Docker Compose (from a repo clone, or by fetching the compose files from…
open-edge-platform/edge-ai-libraries
Scaffolds and wires a new NestJS service/module for the Video Search & Summarization sample app's pipeline-manager using the repo's real conventions.
open-edge-platform/edge-ai-libraries
Deploy Chat Question-and-Answer Core to Kubernetes using Helm (OpenVINO CPU, OpenVINO GPU, or Ollama), including values.yaml configuration, helm install/upgrade, deployment verification, uninstall…
open-edge-platform/edge-ai-libraries
Generates or updates CHANGELOG.md by analyzing git commit history between two branches, tags, or revisions in ANY git repository or folder.
open-edge-platform/edge-ai-libraries
Deploys and manages VSS through setup.sh and its Docker Compose overlays.
open-edge-platform/edge-ai-libraries
A skill your agent uses whenever a developer needs to deploy VSS to Kubernetes, helm install VSS, configure values.yaml for VSS, or run VSS on k8s with GPU/vLLM for the…
Categories
Search a video library with natural language via the VSS Pipeline Manager - upload a video (POST /videos), generate its embeddings (POST /videos/search-embeddings/{id}), then run a query (POST…. Vss Search Index is an agent skill from open-edge-platform/edge-ai-libraries. Search a video library with natural language via the VSS Pipeline Manager - upload a video (POST /videos), generate its embeddings (POST /videos/search-embeddings/{id}), then run a query (POST /search/query) with optional tag and time filters and read the ranked clip results.
Vss Search Index fits situations like: the user says search my videos; find something in the videos; wants to ingest/index a video for search.
Run `npx skills add open-edge-platform/edge-ai-libraries --skill vss-search-index -a claude-code`. Or copy the skill folder (sample-applications/video-search-and-summarization/.github/skills/vss-search-index in open-edge-platform/edge-ai-libraries) into .claude/skills/vss-search-index in your project. Claude Code loads it when a task matches its description.
Run `npx skills add open-edge-platform/edge-ai-libraries --skill vss-search-index -a codex`. Or copy the skill folder (sample-applications/video-search-and-summarization/.github/skills/vss-search-index in open-edge-platform/edge-ai-libraries) into .agents/skills/vss-search-index 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 open-edge-platform/edge-ai-libraries --skill vss-search-index -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vss-search-index, .gemini/skills/vss-search-index, .github/skills/vss-search-index and .opencode/skills/vss-search-index in your project.
Going by SKILL.md and its folder, Vss Search Index needs a shell for the scripts in its folder and the command-line tools its instructions call (curl, jq, bash and git). Our summary lists: A Bash shell; Docker.
SKILL.md contains no URLs. Its commands use curl and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Vss Search Index is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.2k tokens (SKILL.md is roughly 8.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 860 tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Vss Search Index: Chroma Vector Database (Orchestra-Research/AI-Research-SKILLs, 13k stars), SageMaker Serving Image Selection (huggingface/skills, 11k stars), Codebase Management (giancarloerra/SocratiCode, 3.3k stars) and CLIP Image-Text Matching (Orchestra-Research/AI-Research-SKILLs, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
open-edge-platform (a GitHub organization) maintains it in open-edge-platform/edge-ai-libraries, which has 171 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on October 10, 2026.
Source: open-edge-platform/edge-ai-libraries on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.