NestJS Expert
Jeffallan/claude-skills
Scaffolds NestJS modules, controllers, services, DTOs and guards for TypeScript backends, with validation, JWT and Passport auth, Swagger docs and unit and E2E tests.
Scaffolds and wires a new NestJS service/module for the Video Search & Summarization sample app's pipeline-manager using the repo's real conventions.
$ npx skills add open-edge-platform/edge-ai-libraries --skill vss-add-nest-module -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install open-edge-platform/edge-ai-libraries vss-add-nest-module --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-add-nest-module .claude/skills/vss-add-nest-module && 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-add-nest-module" agent skill from https://github.com/open-edge-platform/edge-ai-libraries/tree/main/sample-applications/video-search-and-summarization/.github/skills/vss-add-nest-module into .claude/skills/vss-add-nest-module/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vss-add-nest-module", 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-add-nest-moduleType 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-add-nest-module -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install open-edge-platform/edge-ai-libraries vss-add-nest-module --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-add-nest-module .agents/skills/vss-add-nest-module && 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-add-nest-module" agent skill from https://github.com/open-edge-platform/edge-ai-libraries/tree/main/sample-applications/video-search-and-summarization/.github/skills/vss-add-nest-module into .agents/skills/vss-add-nest-module/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vss-add-nest-module", 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-add-nest-module -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install open-edge-platform/edge-ai-libraries vss-add-nest-module --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-add-nest-module .cursor/skills/vss-add-nest-module && 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-add-nest-module" agent skill from https://github.com/open-edge-platform/edge-ai-libraries/tree/main/sample-applications/video-search-and-summarization/.github/skills/vss-add-nest-module into .cursor/skills/vss-add-nest-module/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vss-add-nest-module", 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-add-nest-module--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-add-nest-module -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install open-edge-platform/edge-ai-libraries vss-add-nest-module --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-add-nest-module .gemini/skills/vss-add-nest-module && 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-add-nest-module" agent skill from https://github.com/open-edge-platform/edge-ai-libraries/tree/main/sample-applications/video-search-and-summarization/.github/skills/vss-add-nest-module into .gemini/skills/vss-add-nest-module/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vss-add-nest-module", 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-add-nest-moduleInstalls 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-add-nest-module -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-add-nest-module .github/skills/vss-add-nest-module && 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-add-nest-module" agent skill from https://github.com/open-edge-platform/edge-ai-libraries/tree/main/sample-applications/video-search-and-summarization/.github/skills/vss-add-nest-module into .github/skills/vss-add-nest-module/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vss-add-nest-module", 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-add-nest-module -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-add-nest-module --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-add-nest-module .opencode/skills/vss-add-nest-module && 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-add-nest-module" agent skill from https://github.com/open-edge-platform/edge-ai-libraries/tree/main/sample-applications/video-search-and-summarization/.github/skills/vss-add-nest-module into .opencode/skills/vss-add-nest-module/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vss-add-nest-module", 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-add-nest-moduleScaffolds and wires a new NestJS service/module for the Video Search & Summarization sample app's pipeline-manager using the repo's real conventions.
Vss Add Nest Module is an agent skill 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. Use when asked to add a new service/module to pipeline-manager, extend the VSS orchestrator, add a new endpoint/queue/event to pipeline-manager, or scaffold a NestJS module the repo way for the video-search-and-summarization sample app.
Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 30 other files, including scripts, reference files and assets (for example `BENCHMARK.md`, `assets/module-template/controllers/example.controller.ts` and `assets/module-template/example.module.ts`).
It sits in Backend & APIs, covering Summarization and Project scaffolding. It works with NestJS, OpenAPI and TypeORM. 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.
11 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit cdf860c. 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/ (TypeScript, from the files we listed), which the agent can run.
Shell commands in SKILL.md call:
npmbashFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use npm, 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 Add Nest Module loads about 2.5k tokens when it runs, and up to ~5.4k if it reads all its reference files. Until then it costs about 102 tokens; SKILL.md has 666 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 cdf860c, republished under its Apache-2.0 licence (© open-edge-platform). 666 words, ~2,458 tokens.
.claude/skills/vss-add-nest-module/SKILL.md (or your agent's skills folder). This skill also uses 22 other files; get the full folder from GitHub.Use this when adding a new pipeline-manager/src/<feature>/ capability. First read nearby modules again (summary, search, video-upload, state-manager) because this repo has concrete patterns that matter more than generic NestJS advice.
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 first tries to find an existing VSS checkout -
walking up from the current directory and inspecting the enclosing git repo - and
reuses it without ever re-cloning. Only when no checkout is found does it do a
shallow, single-branch, sparse checkout of just
sample-applications/video-search-and-summarization from main. It prints the
resolved app root on stdout:
# SKILL_DIR is THIS skill's own directory (shown to you when the skill loads);
# in-repo it is .github/skills/vss-add-nest-module. Works the same if the skill is installed standalone.
SKILL_DIR=".github/skills/vss-add-nest-module"
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.
Most feature modules use this shape:
src/<feature>/
<feature>.module.ts
controllers/<feature>.controller.ts
services/<feature>.service.ts
services/<feature>-db.service.ts # only when TypeORM-backed
queues/<feature>-queue.service.ts # only when tick/event queued
models/<feature>.model.ts
models/<feature>.entity.ts # only when persistedWhy: controllers stay thin, services hold orchestration, *-db.service.ts isolates TypeORM repository access, queues are event-driven processors, and models/ keeps DTO/interfaces/entities close to the feature.
Real examples:
// summary/summary.module.ts
@Module({
imports: [VideoUploadModule, StateManagerModule],
controllers: [SummaryController],
providers: [SummaryService],
})
export class SummaryModule {}// search/search.module.ts
@Module({
providers: [SearchStateService, SearchDbService, SearchShimService],
controllers: [SearchController],
imports: [HttpModule, TypeOrmModule.forFeature([SearchEntity]), VideoUploadModule],
exports: [],
})
export class SearchModule {}Use interfaces for internal shapes and Swagger classes for request/response documentation, as in summary/models/summary-pipeline.model.ts and search/model/search.model.ts.
export class SearchQueryDTO {
@ApiProperty({ description: 'Search query string', example: 'person walking' })
query: string;
@ApiPropertyOptional({ description: 'Comma-separated tags to filter by' })
tags?: string;
}Why: controllers can type request bodies while Swagger gets concrete classes with decorators.
Entity pattern:
@Entity('search')
export class SearchEntity {
@PrimaryGeneratedColumn()
dbId?: number;
@Column({ unique: true })
queryId: string;
@Column('jsonb', { nullable: true })
results: SearchResult[];
}Repository pattern:
@Injectable()
export class SearchDbService {
constructor(
@InjectRepository(SearchEntity)
private searchRepo: Repository<SearchEntity>,
) {}
async read(queryId: string): Promise<SearchEntity | null> {
const search = await this.searchRepo.findOne({ where: { queryId } });
return search ?? null;
}
}Wire the entity in two places:
TypeOrmModule.forFeature([NewEntity]).app.module.ts: add NewEntity to TypeOrmModule.forRoot({ entities: [...] }).Why: forFeature enables repository injection in the feature; the root entity list lets TypeORM create/sync the table.
Controllers inject services using the repo's $name property style and expose REST routes with @ApiTags, @ApiOperation, @ApiBody, @ApiParam, and response decorators.
@ApiTags('Search')
@Controller('search')
export class SearchController {
constructor(private $search: SearchStateService) {}
@Post('')
@ApiOperation({ summary: 'Add a new search query' })
@ApiBody({ type: SearchQueryDTO })
async addQuery(@Body() reqBody: SearchQueryDTO) {
return await this.$search.newQuery(reqBody.query);
}
}Why: validation/errors and orchestration live in services; controllers translate HTTP to typed service calls.
Import modules that export the services you need. Examples:
SummaryModule imports VideoUploadModule and StateManagerModule to inject VideoService, AppConfigService, StateService, UiService.VideoUploadModule exports AppConfigService, FeaturesService, VideoService, VideoDbService.StateManagerModule exports StateService, UiService, AudioQueueService.If another module must inject your service, add it to exports.
Why: Nest resolves providers only across module boundaries through imports/exports.
Define new event names in src/events/Pipeline.events.ts, src/events/app.events.ts, or src/events/socket.events.ts. Use dot-delimited names because root wiring uses:
EventEmitterModule.forRoot({ delimiter: '.', maxListeners: 5 })Emit and listen like existing services:
this.$emitter.emit(SearchEvents.RUN_QUERY, res.queryId);
@OnEvent(SearchEvents.RUN_QUERY)
async reRunQuery(queryId: string) { ... }Pipeline examples include pipeline.summary.start, pipeline.chunking.complete, and pipeline.summary.stream. App tick events are emitted by AppService and consumed by queues.
Why: event enums prevent string drift and decouple controllers/services/queues/gateways.
Queue processors are injectable services under state-manager/queues or a feature queues/ folder. They keep in-memory waiting/processing state, enqueue on a domain event, process on AppEvents.FAST_TICK, emit progress/completion events, and remove stale work on AppEvents.SUMMARY_REMOVED.
@Injectable()
export class SummaryQueueService {
waiting: SummaryQueueItem[] = [];
processing: SummaryQueueItem[] = [];
@OnEvent(PipelineEvents.SUMMARY_TRIGGER)
streamTrigger({ stateId }: PipelineDTOBase) {
this.waiting.push({ stateId, taskType: 'videoSummary' });
}
@OnEvent(AppEvents.FAST_TICK)
processQueue() {
if (this.waiting.length > 0 && this.$inferenceCount.hasLlmSlots()) {
const queueItem = this.waiting.shift()!;
this.processing.push(queueItem);
this.startVideoSummary(queueItem);
}
}
}Why: long-running work is throttled centrally and does not block HTTP requests.
Add socket event enum values to src/events/socket.events.ts, emit them from state/services, and add @OnEvent(...) handlers in sockets/events.gateway.ts.
@OnEvent(SocketEvent.SEARCH_UPDATE)
searchUpdate(payload: SearchQuery) {
this.server.emit('search:update', payload);
}For state-specific updates, join clients to a state room and emit names like summary:sync/${stateId}/status.
Why: services remain transport-agnostic; only the gateway knows Socket.IO event names and rooms.
Add config keys in src/config/configuration.ts, then inject ConfigService:
constructor(private $config: ConfigService) {}
const endPoint: string = this.$config.get('search.endpoint')!;
const maxConcurrent = this.$config.get<number>('openai.vlmCaptioning.concurrent')!;Why: this app centralizes environment parsing and nested config names (search.endpoint, datastore.bucketName, tick.fastInterval).
In src/app.module.ts:
import { NewFeatureModule } from './new-feature/new-feature.module';
import { NewFeatureEntity } from './new-feature/models/new-feature.entity';
@Module({
imports: [
// existing imports...
TypeOrmModule.forRoot({
// existing options...
entities: [StateEntity, VideoEntity, SearchEntity, TagEntity, NewFeatureEntity],
}),
NewFeatureModule,
],
})
export class AppModule {}Place EventEmitterModule.forRoot(...) once only; do not add another root event emitter.
From pipeline-manager/, run existing checks only:
npm run build
npm test -- --runInBand
npm run lintIf changing only docs or templates, no app build is required. If adding entities, verify migrations/sync behavior is acceptable for this sample (synchronize: true, migrationsRun: true are already set).
See references/nest-conventions.md for a catalog of actual repo conventions and file references. Use assets/module-template/ as a starting scaffold, then rename example to the real feature.
© 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 22 other files (scripts, references, assets) in sample-applications/video-search-and-summarization/.github/skills/vss-add-nest-module of open-edge-platform/edge-ai-libraries.
Open the folder on GitHubat commit cdf860c
Vss Add Nest Module 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 Add Nest Module this skillopen-edge-platform/edge-ai-libraries | 169 | — | ~2.5k | Automated safety check: Pass | Apache-2.0 | |
| NestJS ExpertJeffallan/claude-skills | 12k | — | ~2k | Automated safety check: Pass | MIT | |
| VibexRaja0sama/vibex | 388 | — | ~7.8k | Automated safety check: Pass | MIT | |
| ToolJet Marketplace Plugin BuilderToolJet/ToolJet | 41k | — | ~2.1k | Automated safety check: Pass | AGPL-3.0 | |
| Backendredis/RedisInsight | 8.9k | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Twenty Entity Runner Actionstwentyhq/twenty | 58k | — | ~3.1k | Automated safety check: Pass | Custom licence |
Jeffallan/claude-skills
Scaffolds NestJS modules, controllers, services, DTOs and guards for TypeScript backends, with validation, JWT and Passport auth, Swagger docs and unit and E2E tests.
Raja0sama/vibex
Diagrams and checkable docs from a codebase. An agent skill from Raja0sama/vibex.
ToolJet/ToolJet
Turns an API description, such as an OpenAPI file or a Postman collection, into a connector plugin for ToolJet's marketplace and checks it with the repo's validator.
redis/RedisInsight
NestJS backend development patterns for the RedisInsight API: module structure, services, controllers, DTOs, dependency injection, and error handling.
twentyhq/twenty
Step four of adding a syncable entity in the Twenty server: write create, update and delete action handlers that run workspace migrations against the database.
samchon/nestia
Defines the nestia product contract, workspace layout, package boundaries, the Go plugin composition model, and canonical commands.
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
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…
open-edge-platform/edge-ai-libraries
Helps developers understand and safely modify the DLStreamer/GStreamer Pipeline Server (EVAM) video ingestion pipelines in the video-search-and-summarization sample app.
Categories
Scaffolds and wires a new NestJS service/module for the Video Search & Summarization sample app's pipeline-manager using the repo's real conventions. Vss Add Nest Module is an agent skill 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.
Vss Add Nest Module fits situations like: asked to add a new service/module to pipeline-manager; extend the VSS orchestrator; add a new endpoint/queue/event to pipeline-manager; scaffold a NestJS module the repo way for the video-search-and-summarization sample app.
Run `npx skills add open-edge-platform/edge-ai-libraries --skill vss-add-nest-module -a claude-code`. Or copy the skill folder (sample-applications/video-search-and-summarization/.github/skills/vss-add-nest-module in open-edge-platform/edge-ai-libraries) into .claude/skills/vss-add-nest-module 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-add-nest-module -a codex`. Or copy the skill folder (sample-applications/video-search-and-summarization/.github/skills/vss-add-nest-module in open-edge-platform/edge-ai-libraries) into .agents/skills/vss-add-nest-module 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-add-nest-module -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-add-nest-module, .gemini/skills/vss-add-nest-module, .github/skills/vss-add-nest-module and .opencode/skills/vss-add-nest-module in your project.
Going by SKILL.md and its folder, Vss Add Nest Module needs TypeScript for the scripts in its folder and the command-line tools its instructions call (npm and bash). Our summary lists: Node.js.
SKILL.md contains no URLs. Its commands use npm, 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 Add Nest Module is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.5k tokens (SKILL.md is roughly 9.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 3k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Vss Add Nest Module: NestJS Expert (Jeffallan/claude-skills, 12k stars), Vibex (Raja0sama/vibex, 388 stars), ToolJet Marketplace Plugin Builder (ToolJet/ToolJet, 41k stars) and Backend (redis/RedisInsight, 8.9k 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 169 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on October 9, 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.