Compile
apache/skywalking-nodejs
Compile / build / type-check the skywalking-nodejs agent. An agent skill from apache/skywalking-nodejs.
Official agent skill
Azure Functions Node Worker Critical Path
Mandatory human-intervention gate for critical Azure Functions Node.js worker code.
Install Azure Functions Node Worker Critical Path
$ npx skills add Azure/azure-functions-nodejs-worker --skill azure-functions-node-worker-critical-path -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Azure/azure-functions-nodejs-worker azure-functions-node-worker-critical-path --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/Azure/azure-functions-nodejs-worker.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/azure-functions-node-worker-critical-path .claude/skills/azure-functions-node-worker-critical-path && 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 "azure-functions-node-worker-critical-path" agent skill from https://github.com/Azure/azure-functions-nodejs-worker/tree/v3.x/.github/skills/azure-functions-node-worker-critical-path into .claude/skills/azure-functions-node-worker-critical-path/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-functions-node-worker-critical-path", 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/Azure/azure-functions-nodejs-worker/tree/v3.x/.github/skills/azure-functions-node-worker-critical-pathType 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 Azure/azure-functions-nodejs-worker --skill azure-functions-node-worker-critical-path -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Azure/azure-functions-nodejs-worker azure-functions-node-worker-critical-path --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/azure-functions-nodejs-worker.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/azure-functions-node-worker-critical-path .agents/skills/azure-functions-node-worker-critical-path && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "azure-functions-node-worker-critical-path" agent skill from https://github.com/Azure/azure-functions-nodejs-worker/tree/v3.x/.github/skills/azure-functions-node-worker-critical-path into .agents/skills/azure-functions-node-worker-critical-path/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-functions-node-worker-critical-path", 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 Azure/azure-functions-nodejs-worker --skill azure-functions-node-worker-critical-path -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Azure/azure-functions-nodejs-worker azure-functions-node-worker-critical-path --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/azure-functions-nodejs-worker.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/azure-functions-node-worker-critical-path .cursor/skills/azure-functions-node-worker-critical-path && 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 "azure-functions-node-worker-critical-path" agent skill from https://github.com/Azure/azure-functions-nodejs-worker/tree/v3.x/.github/skills/azure-functions-node-worker-critical-path into .cursor/skills/azure-functions-node-worker-critical-path/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-functions-node-worker-critical-path", 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/Azure/azure-functions-nodejs-worker.git --path .github/skills/azure-functions-node-worker-critical-path--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 Azure/azure-functions-nodejs-worker --skill azure-functions-node-worker-critical-path -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Azure/azure-functions-nodejs-worker azure-functions-node-worker-critical-path --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/azure-functions-nodejs-worker.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/azure-functions-node-worker-critical-path .gemini/skills/azure-functions-node-worker-critical-path && 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 "azure-functions-node-worker-critical-path" agent skill from https://github.com/Azure/azure-functions-nodejs-worker/tree/v3.x/.github/skills/azure-functions-node-worker-critical-path into .gemini/skills/azure-functions-node-worker-critical-path/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-functions-node-worker-critical-path", 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 Azure/azure-functions-nodejs-worker azure-functions-node-worker-critical-pathInstalls 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 Azure/azure-functions-nodejs-worker --skill azure-functions-node-worker-critical-path -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Azure/azure-functions-nodejs-worker.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/azure-functions-node-worker-critical-path .github/skills/azure-functions-node-worker-critical-path && 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 "azure-functions-node-worker-critical-path" agent skill from https://github.com/Azure/azure-functions-nodejs-worker/tree/v3.x/.github/skills/azure-functions-node-worker-critical-path into .github/skills/azure-functions-node-worker-critical-path/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-functions-node-worker-critical-path", 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 Azure/azure-functions-nodejs-worker --skill azure-functions-node-worker-critical-path -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Azure/azure-functions-nodejs-worker azure-functions-node-worker-critical-path --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/azure-functions-nodejs-worker.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/azure-functions-node-worker-critical-path .opencode/skills/azure-functions-node-worker-critical-path && 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 "azure-functions-node-worker-critical-path" agent skill from https://github.com/Azure/azure-functions-nodejs-worker/tree/v3.x/.github/skills/azure-functions-node-worker-critical-path into .opencode/skills/azure-functions-node-worker-critical-path/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-functions-node-worker-critical-path", 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.
Facts
- Skill name
azure-functions-node-worker-critical-path- GitHub stars
- 110
- Token cost
- ~2k tokens
- SKILL.md length
- 812 words
- Files
- 2 (incl. references)
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- MIT
At a glance
Mandatory human-intervention gate for critical Azure Functions Node.js worker code.
- Works in 5 steps: Classify Before Editing → Announce the Gate → Trace Blast Radius → …
- Tasks that involve gRPC and Protobuf
- SKILL.md covers Non-Negotiable Rule, Required Workflow, Automatic Gate Triggers and Enforcement Boundary
- Calls npm
What it does
Azure Functions Node Worker Critical Path is an agent skill from Azure/azure-functions-nodejs-worker, published by the product's own GitHub organization. Mandatory human-intervention gate for critical Azure Functions Node.js worker code. Use automatically or as /azure-functions-node-worker-critical-path for changes to Host-worker RPC/protobuf, gRPC startup, message routing, capabilities, app/module loading, programming-model registration, invocation conversion, specialization/environment/process state, hooks, termination, error sanitization, dependencies, bundling, packaging, pipelines, compatibility behavior, or tests that protect those paths. Classify risk…
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/critical-paths.md`).
It sits in Backend & APIs, covering gRPC and Protobuf. It works with Azure Functions, gRPC, Node.js and Microsoft Azure. The repository describes itself as: The Node.js worker for the Azure Functions runtime - https://functions.azure.com. The licence is MIT.
When your agent uses it
- Tasks that involve gRPC and Protobuf
Example prompts
- “/azure-functions-node-worker-critical-path”
Requirements
- Node.js
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 8c3b7f3. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
Shell commands in SKILL.md call:
npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
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.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Azure Functions Node Worker Critical Path loads about 2k tokens when it runs, and up to ~3.7k if it reads all its reference files. Until then it costs about 167 tokens; SKILL.md has 812 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.
Safety
Auto-check passed
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); files beside SKILL.md are not scanned.
SKILL.md
The full file from Azure/azure-functions-nodejs-worker at commit 8c3b7f3, republished under its MIT licence (© Azure). 812 words, ~1,977 tokens.
Download SKILL.mdSave it as
.claude/skills/azure-functions-node-worker-critical-path/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- azure-functions-node-worker-critical-path
- description
- Mandatory human-intervention gate for critical Azure Functions Node.js worker code. Use automatically or as /azure-functions-node-worker-critical-path for changes to Host-worker RPC/protobuf, gRPC startup, message routing, capabilities, app/module loading, programming-model registration, invocation conversion, specialization/environment/process state, hooks, termination, error sanitization, dependencies, bundling, packaging, pipelines, compatibility behavior, or tests that protect those paths. Classify risk, block AI-only approval, require the proper human review, and produce a review packet with validation evidence.
- argument-hint
- [diff, file, proposed change, or PR]
- user-invocable
- true
- disable-model-invocation
- false
Azure Functions Node.js Worker Critical Path
This skill is a review gate, not a general code review. Its purpose is to identify changes for which automated reasoning and tests are insufficient and a qualified human must make or approve the decision.
Apply azure-functions-node-worker for domain validation. Apply azure-functions-node-worker-security whenever the change affects a trust boundary, executable code selection, credentials, process isolation, availability controls, or dependencies.
Read critical-paths.md to classify affected files and semantic triggers.
Non-Negotiable Rule
Human approval cannot be supplied by Copilot, inferred from passing tests, or replaced by this skill. For a triggered change:
- do not label it approved, safe to merge, or fully complete without recorded human approval
- do not commit, merge, publish, or release it on the human's behalf
- do not weaken, bypass, or reinterpret the gate because the patch is small or generated
- identify the reviewing owner from
.github/CODEOWNERS; this repository currently assigns@azure/azure-functions-nodejs
Automated tools may prepare a local draft, tests, threat analysis, and review packet unless the change requires design approval before implementation.
Required Workflow
1. Classify Before Editing
Inspect the requested behavior and relevant diff. Classify by semantics as well as path:
Gate A - human decision before implementation: changes the wire contract, compatibility policy, trusted peer/endpoint, executable-code boundary, process isolation, environment/working-directory policy, termination guarantee, or shipped dependency/release behaviorGate B - human review before acceptance: modifies an implementation on a critical path without intentionally changing the established contractNot gated: does not affect a critical behavior and does not weaken tests or validation protecting one
If uncertain between two levels, use the stricter gate and state exactly what fact would lower it.
2. Announce the Gate
For Gate A, pause implementation until a human confirms the intended contract and tradeoff. Ask only the concrete decision needed, such as:
- What Host versions and message shapes must remain compatible?
- Is this path allowed to load outside the function app root?
- Which process state must survive specialization or failed reload?
- What shutdown deadline and failure behavior does the Host expect?
- Is the dependency/protocol change approved for the shipped worker?
For Gate B, a local uncommitted draft may proceed when requested, but mark it HUMAN REVIEW REQUIRED from the start and preserve that status through the final report.
Analysis-only requests do not require approval to investigate; they still require a human to accept any resulting critical-path recommendation.
3. Trace Blast Radius
Describe the affected end-to-end flow:
Host -> gRPC/protobuf -> event handler -> WorkerContext/AppContext -> programming model or module loader -> invocation/side effect -> response/log -> Host
Account for:
- supported Host and Node.js versions
- worker indexing and legacy Host indexing
- CommonJS and ESM loading
- warm invocations and concurrent asynchronous work
- specialization, retries, partial failures, and shutdown
- generated RPC artifacts and other repositories sharing the contract
- user/system error and log behavior
- bundle, package, and deployment artifacts
Show full SKILL.md (351 more words)Show less
4. Demand Discriminating Evidence
Require a focused regression test that would fail without the change and observes the critical boundary. Then require the checks selected by the domain and security skills.
Passing unit tests do not prove wire compatibility, security, race freedom, or production packaging. Require additional evidence where applicable:
- generated
.protodiff matched to Host schema and compatibility plan npm run host-sanityor cross-repository e2e evidence- focused concurrency or partial-failure test
- synthetic secret-leak regression
npm run webpackand shipped-artifact inspection- dependency advisory, provenance, runtime-reachability, and lockfile analysis
If a required environment is unavailable, mark the evidence missing. Do not silently downgrade the gate.
5. Produce the Human Review Packet
Use this exact structure:
HUMAN REVIEW REQUIRED
Gate: A - before implementation | B - before acceptance
Owner: @azure/azure-functions-nodejs (or more specific confirmed owner)
Decision needed: <one concrete decision>
Critical paths:
- <file/symbol and why it is critical>
Behavioral contract:
- Before: <current Host/worker/Node behavior>
- After: <proposed behavior>
- Must remain invariant: <compatibility and security properties>
Blast radius:
- <Host versions, Node versions, indexing modes, process/app state, artifacts>
Security analysis:
- <finding, no finding, or pending analysis with assumptions>
Validation evidence:
- PASS/FAIL/NOT RUN: <exact check and what it proves>
Residual risks or open decisions:
- <specific unresolved item>
Human decision: PENDINGKeep Human decision: PENDING until a human explicitly records approval. If approval is provided, record who approved, what decision they approved, and any conditions; do not generalize that approval to later changes.
Automatic Gate Triggers
Always trigger at least Gate B for changes that affect:
- startup argument parsing, gRPC endpoint/credentials, stream setup, routing, status/error response construction, or capabilities
- protobuf source, generated RPC artifacts, message fields/types, or Host-worker compatibility
- app-root, package entry point, glob, script path, export selection, require/import behavior, or core-module interception
- worker/function indexing choice, registration locks, programming-model selection, invocation conversion, or binding semantics
WorkerContext,AppContext, specialization,process.env, working directory, module/global state, or in-flight invocation behavior- app/invocation/log hook ordering, mutation, error propagation, or cleanup
- process listeners, event-loop blocking controls, retries/timeouts, stream close, or process exit
- error classification, sanitization, log category, or any Host-bound diagnostic that may contain credentials
- runtime dependency versions, install scripts, generated code tooling, webpack, worker config, NuGet package contents, or release pipelines
- removal or weakening of tests and assertions that protect any item above
Trigger Gate A when the intended contract or trust assumption changes, not merely because an implementation file is touched. See critical-paths.md for examples.
Enforcement Boundary
This skill makes Copilot detect and honor the human-review requirement, but a repository skill cannot technically prevent a GitHub merge. Enforce the policy in GitHub with CODEOWNERS-backed branch protection or rulesets requiring approving reviews from code owners, required status checks, stale-approval dismissal, and conversation resolution.
© Azure, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in .github/skills/azure-functions-node-worker-critical-path of Azure/azure-functions-nodejs-worker.
- SKILL.md
- references/critical-paths.md
Open the folder on GitHubat commit 8c3b7f3
Compare with similar skills
Azure Functions Node Worker Critical Path 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 |
|---|---|---|---|---|---|---|
| Azure Functions Node Worker Critical Path this skillAzure/azure-functions-nodejs-worker | 110 | — | ~2k | Automated safety check: Pass | MIT | |
| Compileapache/skywalking-nodejs | 180 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Fishjam JS Server SDKsoftware-mansion-labs/skills | 291 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Azure Functionsdavila7/claude-code-templates | 32k | 2 repos | ~344 | Automated safety check: Pass | MIT | |
| Adding Personhog RpcPostHog/posthog | 40k | — | ~2.1k | Automated safety check: Pass | Custom licence | |
| Cortexdb Memory Openclawliliang-cn/cortexdb | 274 | — | ~1.6k | Automated safety check: Pass | MIT |
Similar skills
Fishjam JS Server SDK
software-mansion-labs/skills
Node.js / TypeScript server SDK for Fishjam — backends that create rooms, mint peer tokens, listen to server notifications, and run agents.
Azure Functions
davila7/claude-code-templates
Expert patterns for Azure Functions development including isolated worker model, Durable Functions orchestration, cold start optimization, and production patterns.
- Official
Adding Personhog Rpc
PostHog/posthog
Guide for adding a new RPC to personhog-replica and personhog-router.
Cortexdb Memory Openclaw
liliang-cn/cortexdb
Give a Node.js agent (such as OpenClaw) durable, local-first memory plus a queryable SPARQL knowledge graph, backed by CortexDB through its gRPC sidecar and the cortexdb-client npm package.
Use Yaak
mountain-loop/yaak
A skill your agent uses when the user mentions Yaak, a Yaak workspace, or the yaak command, or asks to call, hit, or smoke test HTTP/REST endpoints, save or organize API requests for reuse or manual…
More from Azure/azure-functions-nodejs-worker
- Official
Azure Functions Node Worker
Azure/azure-functions-nodejs-worker
Repository-specific Azure Functions Node.js Host-worker architecture and change-validation workflow.
- Official
Azure Functions Node Worker Security
Azure/azure-functions-nodejs-worker
Security analysis for the Azure Functions Node.js worker. An agent skill from Azure/azure-functions-nodejs-worker.
Related
Categories
Questions about Azure Functions Node Worker Critical Path
What does Azure Functions Node Worker Critical Path do?
Mandatory human-intervention gate for critical Azure Functions Node.js worker code. Azure Functions Node Worker Critical Path is an agent skill from Azure/azure-functions-nodejs-worker, published by the product's own GitHub organization.js worker code.
When should I use Azure Functions Node Worker Critical Path?
Azure Functions Node Worker Critical Path fits situations like: tasks that involve gRPC and Protobuf.
How do I install Azure Functions Node Worker Critical Path in Claude Code?
Run `npx skills add Azure/azure-functions-nodejs-worker --skill azure-functions-node-worker-critical-path -a claude-code`. Or copy the skill folder (.github/skills/azure-functions-node-worker-critical-path in Azure/azure-functions-nodejs-worker) into .claude/skills/azure-functions-node-worker-critical-path in your project. Claude Code loads it when a task matches its description.
How do I install Azure Functions Node Worker Critical Path in Codex?
Run `npx skills add Azure/azure-functions-nodejs-worker --skill azure-functions-node-worker-critical-path -a codex`. Or copy the skill folder (.github/skills/azure-functions-node-worker-critical-path in Azure/azure-functions-nodejs-worker) into .agents/skills/azure-functions-node-worker-critical-path in your project. Codex loads it when a task matches its description.
Can I use Azure Functions Node Worker Critical Path in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Azure/azure-functions-nodejs-worker --skill azure-functions-node-worker-critical-path -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/azure-functions-node-worker-critical-path, .gemini/skills/azure-functions-node-worker-critical-path, .github/skills/azure-functions-node-worker-critical-path and .opencode/skills/azure-functions-node-worker-critical-path in your project.
What does Azure Functions Node Worker Critical Path need to run?
Going by SKILL.md and its folder, Azure Functions Node Worker Critical Path needs the command-line tools its instructions call (npm). Our summary lists: Node.js.
Does Azure Functions Node Worker Critical Path access the network?
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.
Is Azure Functions Node Worker Critical Path safe to install?
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. Review the folder before installing.
What licence does Azure Functions Node Worker Critical Path use?
Azure Functions Node Worker Critical Path is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Azure Functions Node Worker Critical Path use?
About 2k tokens (SKILL.md is roughly 7.9k 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 1.7k tokens, read only when the agent opens those files.
What are the alternatives to Azure Functions Node Worker Critical Path?
Skills that share tags, products or a category with Azure Functions Node Worker Critical Path: Compile (apache/skywalking-nodejs, 180 stars), Fishjam JS Server SDK (software-mansion-labs/skills, 291 stars), Azure Functions (davila7/claude-code-templates, 32k stars) and Adding Personhog Rpc (PostHog/posthog, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Azure Functions Node Worker Critical Path?
Azure (a GitHub organization, an official publisher) maintains it in Azure/azure-functions-nodejs-worker, which has 110 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 8, 2026.
Source: Azure/azure-functions-nodejs-worker on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.