packages-worker-add-entrypoint

Scaffold a new sub-worker directory with entrypoint and shared config files.

3.4k|728|Updated Jun 28, 2022
One-click install
npx skills add https://github.com/linuxfoundation/crowd.dev --skill packages-worker-add-entrypoint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: packages-worker-add-entrypoint
Source: https://github.com/linuxfoundation/crowd.dev/tree/main/.claude/skills/packages-worker-add-entrypoint
Command: npx skills add https://github.com/linuxfoundation/crowd.dev --skill packages-worker-add-entrypoint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a guided scaffold to add a new sub-worker inside packages_worker, enabling a scalable and consistent extension pattern for additional workers.

Core Features & Use Cases

  • Scaffold a complete sub-worker directory structure under services/apps/packages_worker, mirroring existing workers.
  • Generate entrypoint ts file and shared config/types files, following the single-service multi-entry-point structure.
  • Use when you need to add a new worker (e.g., npm, osv, scorecard) to packages_worker and maintain consistency with existing tooling.

Quick Start

Create a new entrypoint skeleton for a named worker inside packages_worker following the described structure.

Frequently Asked Questions about packages-worker-add-entrypoint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold a new sub-worker under packages_worker?

To scaffold a sub-worker under packages_worker, use a guided generator that creates the complete directory structure, bin entrypoint, shared config, and Docker build templates to ensure consistent multi-entry-point patterns.

What is the multi-entry-point pattern for adding npm or osv workers?

The multi-entry-point pattern is a single-service architecture where each worker, such as npm or osv, gets its own bin entrypoint file and worker directory while sharing common config and types within the packages_worker structure.

How do I add a new worker to packages_worker and maintain consistency with existing tooling?

Add a new worker by generating a skeleton that mirrors existing workers, automatically creating the required TypeScript entrypoint, worker directory, and shared configuration files to maintain consistency with existing tooling.

Do I need Docker build templates when creating a packages_worker entrypoint?

Yes, Docker build templates are required to satisfy the git-ready entrypoint starter requirements, ensuring the newly scaffolded sub-worker includes proper containerization configuration alongside its bin entrypoint and shared config.

Can I use this scaffold to add any type of worker to packages_worker?

Yes, you can use this scaffold to add various workers like npm, osv, or scorecard to packages_worker, as it enforces a scalable and consistent extension pattern for additional workers.