operating-script

Generate ESM-compliant Gulp task modules with JSDoc and registration steps.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/k2works/getting-started-algorithm --skill operating-script
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: operating-script
Source: https://github.com/k2works/getting-started-algorithm/tree/main/.agents/skills/operating-script
Command: npx skills add https://github.com/k2works/getting-started-algorithm --skill operating-script

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction and inconsistency of manually writing and registering Gulp operational scripts by providing a standard template, naming conventions, and required registration steps to ensure tasks are discoverable and maintainable across environments.

Core Features & Use Cases

  • Standardized Templates: Provides an ESM-based script skeleton with sections for configuration, helpers, JSDoc, and required help tasks.
  • Naming & Task Conventions: Enforces file and Gulp task naming patterns ({category}_{env}.js and category:env:action) so teams maintain predictable task names.
  • Integration Steps: Guides updating gulpfile.js, .env.example, and reusing shared helper modules to register and test new tasks.
  • Use Case: When adding a staging deploy pipeline, scaffold deploy_stg.js with provision and deploy tasks, hook it into gulpfile.js, and validate with npx gulp deploy:stg:help.

Quick Start

Use the operating-script skill to generate a new Gulp task file (for example deploy_stg.js) following the template, add the required {category}:help task, update gulpfile.js imports, and confirm operation with npx gulp {category}:help.

Frequently Asked Questions about operating-script

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

FAQPage Schema
How do I create consistent Gulp scripts for deployment automation?

To create consistent Gulp scripts for deployment automation, generate ESM-compliant task modules with JSDoc, environment-prefixed variables, and a help task. Update gulpfile.js imports and validate new operational scripts using npx gulp category:help.

What is the best way to structure Gulp tasks for staging and production environments?

Structuring Gulp tasks for staging and production involves using standardized file naming like deploy_stg.js and task conventions like category:env:action. This ensures predictable, discoverable task names across different deployment and operational scenarios.

How do I add a new staging deploy pipeline to an existing gulpfile.js?

Adding a staging deploy pipeline requires scaffolding a deploy_stg.js file with provision and deploy tasks, hooking it into gulpfile.js imports, reusing shared helper modules, and confirming operation with npx gulp deploy:stg:help.

Does Gulp support ESM modules for operational scripts?

Gulp supports ESM modules for operational scripts by using an ESM-based script skeleton. This skeleton includes dedicated sections for configuration, helpers, JSDoc, and required help tasks to maintain project maintenance scripts.

Why do my Gulp operational tasks lack discoverability across environments?

Gulp operational tasks lack discoverability when standard templates and naming conventions are not applied. Enforcing file patterns like category_env.js and task patterns like category:env:action ensures tasks remain predictable and maintainable.

What do I need to update when adding new Gulp operational scripts?

When adding new Gulp operational scripts, you must update gulpfile.js imports, add required category:help tasks, update .env.example with environment-prefixed variables, and reuse shared helper modules for proper registration.