
from awesome-omni-skills50
Decision-focused Node.js guidance for framework choice, async patterns, security, testing, and architecture — teaches how to think about Node.js projects rather
Practical, decision-oriented Node.js guidance: helps agents and operators choose frameworks, design async patterns, enforce security, and structure architecture. Emphasises provenance — preserving upstream workflow and copied support files — and teaches decision-making rather than rote code copying.
Use this skill when making architecture or framework decisions, designing async patterns, planning validation/testing strategies, or preparing a provenance-grounded review or PR. Activate when the task requires preserving upstream files, enumerating trade-offs, or producing an auditable reviewer packet.
Inferred compatibility: codex-cli, claude-code, cursor, gemini-cli, opencode (listed in frontmatter).
A Node.js best-practices reference skill repackaged from an upstream 'antigravity-awesome-skills' repo. The SKILL.md is primarily an editorial/provenance wrapper with embedded decision trees, checklists, and comparison tables covering framework selection, async patterns, security, testing, and architecture. No scripts are bundled — it's a pure reference/knowledge skill. The provenance boilerplate adds significant noise and the skill tries to be both a workflow executor and a static reference guide, doing neither well. Content itself is decent general Node.js guidance but not actionable as a skill workflow.
The skill is essentially a static reference document about Node.js best practices, wrapped in a heavy provenance/operating-table layer from an 'awesome-skills' packaging pipeline. Security score is high because there are no scripts, no network calls, no destructive commands — it's purely informational. Code quality is middling because the SKILL.md is verbose, repetitive, and mixes editorial packaging concerns with developer guidance. Architecture is low due to monolithic single-file approach, no scripts/ or references/ directories, vague output contracts, and the provenance layer adds complexity without value. Usefulness is moderate — the Node.js guidance itself is reasonable but generic and available from many free sources; the skill doesn't automate anything or provide unique workflow value.
Azure Identity SDK (TypeScript) v2
Authenticate to Azure services from TypeScript using DefaultAzureCredential, Managed Identity, service principals, and credential chains with provenance-preserv
Conductor Revert (Git-aware Revert Track)
Git-aware revert workflow for reverting tracks, phases, or tasks while preserving provenance and upstream workflow; includes safety checks and an execution plan
Security Threat Model (Repository-grounded)
Generate an evidence-backed, repository-specific threat model that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and prioritized miti
Context Restoration — Code Refactoring
Workflow and best practices for restoring and preserving project context during code refactoring, with provenance and selective file restoration.
HelpDesk Automation (Rube MCP)
Automate HelpDesk workflows via Rube MCP (Composio): list and paginate tickets, manage views, use canned responses, and inspect custom fields while preserving u
Azure Event Hubs (Rust) — Workflow
Run and review Azure Event Hubs workflows in Rust: send/receive events, batch sends, partitioned consumption and checkpointing with preserved provenance.
Azure.Messaging.EventGrid (.NET) v2
Workflow skill for Azure Event Grid (.NET): publish and consume EventGrid and CloudEvents, with examples for publishing, pull delivery, and Azure Functions trig
AgentPhone (Telephony)
Manage AgentPhone telephony workflows: create agents, buy/release numbers, make calls, send/receive SMS, configure webhooks, and inspect transcripts/usage.
Learning Opportunities
Adds short interactive learning exercises during AI-assisted coding to help developers understand design decisions and new code before merging.
PostgreSQL Table Design
Operational workflow for PostgreSQL schema design: data types, indexing, constraints, partitioning, RLS, and best-practice examples for safe migrations and scal