nexscope 1.0.0

package/README.md

@@ -0,0 +1,93 @@
+# npx
+
+
+
+## Getting started
+
+To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+
+Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
+
+## Add your files
+
+- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
+- [ ] [Add files using the command line](https://docs.gitlab.com/topics/git/add_files/#add-files-to-a-git-repository) or push an existing Git repository with the following command:
+
+```
+cd existing_repo
+git remote add origin https://git.ziniao.com/nexscope/cient/npx.git
+git branch -M master
+git push -uf origin master
+```
+
+## Integrate with your tools
+
+- [ ] [Set up project integrations](https://git.ziniao.com/nexscope/cient/npx/-/settings/integrations)
+
+## Collaborate with your team
+
+- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
+- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
+- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
+- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
+- [ ] [Set auto-merge](https://docs.gitlab.com/user/project/merge_requests/auto_merge/)
+
+## Test and Deploy
+
+Use the built-in continuous integration in GitLab.
+
+- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/)
+- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
+- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
+- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
+- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
+
+***
+
+# Editing this README
+
+When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
+
+## Suggestions for a good README
+
+Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
+
+## Name
+Choose a self-explaining name for your project.
+
+## Description
+Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
+
+## Badges
+On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
+
+## Visuals
+Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
+
+## Installation
+Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
+
+## Usage
+Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
+
+## Support
+Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
+
+## Roadmap
+If you have ideas for releases in the future, it is a good idea to list them in the README.
+
+## Contributing
+State if you are open to contributions and what your requirements are for accepting them.
+
+For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
+
+You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
+
+## Authors and acknowledgment
+Show your appreciation to those who have contributed to the project.
+
+## License
+For open source projects, say how it is licensed.
+
+## Project status
+If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

package/bin/nexscope.js

@@ -0,0 +1,7 @@
+#!/usr/bin/env node
+
+'use strict';
+
+const { run } = require('../src/index');
+
+run(process.argv.slice(2));

package/package.json

@@ -0,0 +1,20 @@
+{
+  "name": "nexscope",
+  "version": "1.0.0",
+  "description": "NexScope CLI tool",
+  "main": "src/index.js",
+  "bin": {
+    "nexscope": "bin/nexscope.js"
+  },
+  "scripts": {
+    "test": "node bin/nexscope.js --help"
+  },
+  "keywords": [
+    "nexscope",
+    "cli"
+  ],
+  "license": "MIT",
+  "engines": {
+    "node": ">=14.0.0"
+  }
+}

package/src/commands/hello.js

@@ -0,0 +1,36 @@
+'use strict';
+
+/**
+ * hello command - example command showing how to write subcommands
+ * Usage: nexscope hello [name]
+ */
+
+function printHelp() {
+  console.log(`
+Usage: nexscope hello [name]
+
+Say hello to someone.
+
+Arguments:
+  name    The name to greet (default: World)
+
+Options:
+  --help, -h    Show help
+
+Examples:
+  nexscope hello
+  nexscope hello Alice
+`);
+}
+
+function run(args) {
+  if (args.includes('--help') || args.includes('-h')) {
+    printHelp();
+    return;
+  }
+
+  const name = args[0] || 'World';
+  console.log(`Hello, ${name}! Welcome to NexScope.`);
+}
+
+module.exports = { run };

package/src/commands/install.js

@@ -0,0 +1,180 @@
+'use strict';
+
+const { spawn } = require('child_process');
+const https = require('https');
+
+const SKILLS_REPO = 'nexscope-ai/eCommerce-Skills';
+const REPO_API = 'https://api.github.com/repos/nexscope-ai/eCommerce-Skills/contents';
+
+function printHelp() {
+  console.log(`
+Usage: nexscope install [options]
+
+Install eCommerce skills from the official NexScope skills repository.
+
+Options:
+  -name <skill>        Install a specific skill by name
+  --list               List all available skills
+  -g, --global         Install globally (user-level)
+  -a, --agent <agent>  Install to a specific agent directory (e.g. claude-code, cursor)
+  --help, -h           Show help
+
+Examples:
+  nexscope install                              Install all skills
+  nexscope install -name brand-monitoring       Install a specific skill
+  nexscope install -g                           Install all skills globally
+  nexscope install -a claude-code               Install to claude-code agent directory
+  nexscope install -name brand-monitoring -g    Install specific skill globally
+  nexscope install --list                       List available skills
+`);
+}
+
+function get(url) {
+  return new Promise((resolve, reject) => {
+    https.get(url, { headers: { 'User-Agent': 'nexscope-cli' } }, (res) => {
+      let data = '';
+      res.on('data', (chunk) => (data += chunk));
+      res.on('end', () => {
+        if (res.statusCode === 200) resolve(data);
+        else reject(new Error(`HTTP ${res.statusCode}: ${url}`));
+      });
+    }).on('error', reject);
+  });
+}
+
+async function fetchSkillList() {
+  const data = await get(REPO_API);
+  return JSON.parse(data).filter((i) => i.type === 'dir').map((i) => i.name);
+}
+
+// Parse directory-related flags to pass through to npx skills
+function parseDirFlags(args) {
+  const flags = [];
+
+  if (args.includes('--global') || args.includes('-g')) {
+    flags.push('-g');
+  }
+
+  const agentIndex = args.findIndex((a) => a === '--agent' || a === '-a');
+  if (agentIndex !== -1 && args[agentIndex + 1]) {
+    flags.push('--agent', args[agentIndex + 1]);
+  }
+
+  return flags;
+}
+
+function installOne(skillName, dirFlags) {
+  return new Promise((resolve) => {
+    const skillsArgs = ['skills', 'add', SKILLS_REPO, '--skill', skillName, '-y', ...dirFlags];
+    const proc = spawn('npx', skillsArgs, { shell: true });
+
+    let output = '';
+    proc.stdout.on('data', (d) => (output += d.toString()));
+    proc.stderr.on('data', (d) => (output += d.toString()));
+
+    proc.on('close', (code) => {
+      resolve({ skillName, success: code === 0, output });
+    });
+  });
+}
+
+function runSkillsSync(skillsArgs) {
+  return new Promise((resolve) => {
+    const proc = spawn('npx', ['skills', ...skillsArgs], { shell: true, stdio: 'inherit' });
+    proc.on('close', (code) => resolve(code));
+  });
+}
+
+async function run(args) {
+  if (args.includes('--help') || args.includes('-h')) {
+    printHelp();
+    return;
+  }
+
+  if (args.includes('--list')) {
+    await runSkillsSync(['add', SKILLS_REPO, '--list']);
+    return;
+  }
+
+  const dirFlags = parseDirFlags(args);
+  const nameIndex = args.indexOf('-name');
+
+  if (nameIndex !== -1) {
+    const skillName = args[nameIndex + 1];
+    if (!skillName) {
+      console.error('Error: -name requires a skill name.');
+      console.error("Run 'nexscope install --help' for usage.");
+      process.exit(1);
+    }
+    // Single skill: pass through output directly
+    const code = await runSkillsSync(['add', SKILLS_REPO, '--skill', skillName, '-y', ...dirFlags]);
+    printThankYou();
+    process.exit(code || 0);
+  } else {
+    // All skills: fetch list then install concurrently
+    process.stdout.write('Fetching skill list... ');
+    const skills = await fetchSkillList();
+    console.log(`${skills.length} skills found.\n`);
+
+    console.log(`Installing all skills concurrently...\n`);
+
+    // Track per-skill status
+    const status = {};
+    skills.forEach((s) => (status[s] = 'pending'));
+
+    function printStatus() {
+      process.stdout.write('\x1B[2J\x1B[0f'); // clear screen
+      console.log(`Installing ${skills.length} skills concurrently...\n`);
+      for (const s of skills) {
+        const icon =
+          status[s] === 'pending' ? '⏳' :
+          status[s] === 'running' ? '⚙ ' :
+          status[s] === 'done'    ? '✓ ' : '✗ ';
+        console.log(`  ${icon} ${s}`);
+      }
+    }
+
+    printStatus();
+
+    const promises = skills.map((skillName) => {
+      status[skillName] = 'running';
+      printStatus();
+      return installOne(skillName, dirFlags).then((result) => {
+        status[skillName] = result.success ? 'done' : 'failed';
+        printStatus();
+        return result;
+      });
+    });
+
+    const results = await Promise.all(promises);
+
+    const succeeded = results.filter((r) => r.success);
+    const failed = results.filter((r) => !r.success);
+
+    console.log(`\n${succeeded.length}/${skills.length} skills installed successfully.`);
+
+    if (failed.length > 0) {
+      console.log('\nFailed skills:');
+      failed.forEach((r) => console.log(`  ✗ ${r.skillName}`));
+    }
+
+    printThankYou();
+    process.exit(failed.length > 0 ? 1 : 0);
+  }
+}
+
+function printThankYou() {
+  const purple = '\x1B[95m';
+  const reset = '\x1B[0m';
+  console.log(`
+${purple}╔═══════════════════════════════════════════════╗
+║                                               ║
+║   Thank you for using NexScope Skills!        ║
+║                                               ║
+║   Visit us at: https://www.nexscope.ai/       ║
+║                                               ║
+╚═══════════════════════════════════════════════╝${reset}
+`);
+}
+
+module.exports = { run };

package/src/index.js

@@ -0,0 +1,53 @@
+'use strict';
+
+const commands = {
+  hello: require('./commands/hello'),
+  install: require('./commands/install'),
+};
+
+function printHelp() {
+  console.log(`
+Usage: nexscope <command> [options]
+
+Commands:
+  hello [name]    Say hello (example command)
+  install         Install eCommerce skills
+
+Options:
+  --help, -h      Show help
+  --version, -v   Show version
+
+Run 'nexscope <command> --help' for more info on a command.
+`);
+}
+
+function printVersion() {
+  const pkg = require('../package.json');
+  console.log(pkg.version);
+}
+
+function run(args) {
+  if (!args.length || args[0] === '--help' || args[0] === '-h') {
+    printHelp();
+    return;
+  }
+
+  if (args[0] === '--version' || args[0] === '-v') {
+    printVersion();
+    return;
+  }
+
+  const commandName = args[0];
+  const commandArgs = args.slice(1);
+  const command = commands[commandName];
+
+  if (!command) {
+    console.error(`Unknown command: ${commandName}`);
+    console.error(`Run 'nexscope --help' to see available commands.`);
+    process.exit(1);
+  }
+
+  command.run(commandArgs);
+}
+
+module.exports = { run };