@stphang/copilot-skills-pack 1.0.0

package/README.md

@@ -0,0 +1,60 @@
+# Copilot Skills Pack
+
+A shareable npm package containing VS Code Copilot agent skills.
+
+## Install Into a Project
+
+From the project where the skills should be installed, run:
+
+```powershell
+npx @stphang/copilot-skills-pack
+```
+
+This copies the bundled skills into `.github/skills/` in the current project. Existing skill files are preserved by default.
+
+## Options
+
+List the bundled skills:
+
+```powershell
+npx @stphang/copilot-skills-pack --list
+```
+
+Replace existing copies:
+
+```powershell
+npx @stphang/copilot-skills-pack --force
+```
+
+Install into another project directory:
+
+```powershell
+npx @stphang/copilot-skills-pack --target C:\path\to\project
+```
+
+The package exposes the `copilot-skills` executable. You can also invoke it explicitly:
+
+```powershell
+npx -p @stphang/copilot-skills-pack copilot-skills
+```
+
+## Included Skills
+
+- `create-skill-with-qna`
+- `hello-world`
+- `summarize-skills`
+
+## Publish
+
+Choose an available npm package name in `package.json`, then publish from this directory:
+
+```powershell
+npm login
+npm publish
+```
+
+The package is configured for public publication, so `npm publish` will publish it without requiring a paid private-package plan. After publishing, others can install the skills with:
+
+```powershell
+npx @stphang/copilot-skills-pack
+```

package/bin/cli.js

@@ -0,0 +1,103 @@
+#!/usr/bin/env node
+
+const fs = require('fs');
+const path = require('path');
+
+const packageRoot = path.resolve(__dirname, '..');
+const bundledSkills = path.join(packageRoot, 'skills');
+
+function printHelp() {
+  console.log(`Usage: npx copilot-skills-pack [options]
+
+Install the bundled skills into .github/skills in the current project.
+
+Options:
+  --target <dir>  Install into a different project directory
+  --force         Replace existing skill files
+  --list          List bundled skills without installing
+  --help          Show this help message`);
+}
+
+function parseArguments(argumentsList) {
+  const options = { force: false, list: false, target: process.cwd() };
+
+  for (let index = 0; index < argumentsList.length; index += 1) {
+    const argument = argumentsList[index];
+
+    if (argument === '--force') {
+      options.force = true;
+    } else if (argument === '--list') {
+      options.list = true;
+    } else if (argument === '--target') {
+      const target = argumentsList[index + 1];
+      if (!target) {
+        throw new Error('--target requires a directory path.');
+      }
+      options.target = path.resolve(target);
+      index += 1;
+    } else if (argument === '--help' || argument === '-h') {
+      options.help = true;
+    } else {
+      throw new Error(`Unknown option: ${argument}`);
+    }
+  }
+
+  return options;
+}
+
+function findSkillNames() {
+  return fs.readdirSync(bundledSkills, { withFileTypes: true })
+    .filter((entry) => entry.isDirectory())
+    .filter((entry) => fs.existsSync(path.join(bundledSkills, entry.name, 'SKILL.md')))
+    .map((entry) => entry.name)
+    .sort();
+}
+
+function copySkill(skillName, destinationRoot, force) {
+  const sourceFile = path.join(bundledSkills, skillName, 'SKILL.md');
+  const destinationDirectory = path.join(destinationRoot, skillName);
+  const destinationFile = path.join(destinationDirectory, 'SKILL.md');
+
+  if (fs.existsSync(destinationFile) && !force) {
+    return { skillName, status: 'skipped' };
+  }
+
+  fs.mkdirSync(destinationDirectory, { recursive: true });
+  fs.copyFileSync(sourceFile, destinationFile);
+  return { skillName, status: 'installed' };
+}
+
+function main() {
+  const options = parseArguments(process.argv.slice(2));
+  const skillNames = findSkillNames();
+
+  if (options.help) {
+    printHelp();
+    return;
+  }
+
+  if (options.list) {
+    console.log(skillNames.join('\n'));
+    return;
+  }
+
+  const destinationRoot = path.join(options.target, '.github', 'skills');
+  const results = skillNames.map((skillName) => copySkill(skillName, destinationRoot, options.force));
+  const installed = results.filter((result) => result.status === 'installed');
+  const skipped = results.filter((result) => result.status === 'skipped');
+
+  console.log(`Installed ${installed.length} skill(s) into ${destinationRoot}.`);
+  if (installed.length > 0) {
+    console.log(`  ${installed.map((result) => result.skillName).join(', ')}`);
+  }
+  if (skipped.length > 0) {
+    console.log(`Skipped ${skipped.length} existing skill(s). Use --force to replace them.`);
+  }
+}
+
+try {
+  main();
+} catch (error) {
+  console.error(`Error: ${error.message}`);
+  process.exitCode = 1;
+}

package/package.json

@@ -0,0 +1,26 @@
+{
+  "name": "@stphang/copilot-skills-pack",
+  "version": "1.0.0",
+  "description": "Shareable VS Code Copilot agent skills for project workspaces.",
+  "bin": {
+    "copilot-skills": "bin/cli.js"
+  },
+  "files": [
+    "bin",
+    "skills",
+    "README.md"
+  ],
+  "keywords": [
+    "github-copilot",
+    "copilot",
+    "agent-skills",
+    "vscode"
+  ],
+  "license": "MIT",
+  "publishConfig": {
+    "access": "public"
+  },
+  "engines": {
+    "node": ">=14"
+  }
+}

package/skills/create-skill-with-qna/SKILL.md

@@ -0,0 +1,37 @@
+---
+name: create-skill-with-qna
+description: 'Create a reusable VS Code agent skill through a concise requirements interview. Use when defining a skill from scratch, gathering its purpose, scenarios, workflow, inputs, outputs, constraints, or prompt examples.'
+argument-hint: 'Describe the skill you want to create.'
+user-invocable: true
+---
+
+# Create Skill With Q&A
+
+Guide the user through a short, structured interview and synthesize the answers into a valid, reusable skill file.
+
+## When to Use
+
+- Creating a new skill from scratch.
+- Defining a skill's purpose and intended outcomes.
+- Capturing usage scenarios, workflow steps, inputs, outputs, and constraints.
+- Reviewing a generated skill before using it.
+
+## Procedure
+
+1. Ask for the skill name.
+2. Ask for the primary purpose and desired outcome.
+3. Ask for intended usage scenarios.
+4. Ask for the workflow or steps the skill should follow.
+5. Ask for expected inputs, outputs, and constraints.
+6. Ask whether prompt templates or examples are wanted; include them only when explicitly requested or provided.
+7. Check whether the target skill already exists. Ask before overwriting an existing file.
+8. Generate `.github/skills/<skill-name>/SKILL.md` with matching folder and frontmatter names.
+9. Include a meaningful description, a `When to Use` section, and a clear step-by-step procedure.
+10. Validate the frontmatter and present a concise summary of the generated skill.
+
+## Interview Rules
+
+- Ask one concise question at a time.
+- Do not invent requirements, prompts, templates, or examples.
+- Normalize the filename to lowercase kebab-case while preserving the intended display name in the heading.
+- Keep the final skill focused and reusable.

package/skills/hello-world/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: hello-world
+description: 'Introduce programming by printing Hello World. Use for a first coding lesson or to verify that a compiler, interpreter, runtime, or project setup works.'
+argument-hint: 'Specify the programming language or runtime to use.'
+user-invocable: true
+---
+
+# Hello World
+
+Create the smallest useful program that prints `Hello World` and confirms the selected development environment can run it.
+
+## When to Use
+
+- Starting a first programming lesson.
+- Testing compiler or interpreter installation.
+- Verifying a project entry point and runtime command.
+
+## Procedure
+
+1. Identify the requested programming language and runtime.
+2. Create the conventional entry-point file for that language.
+3. Print exactly `Hello World` using the language's standard output API.
+4. Run the program with the project's normal command.
+5. Confirm the output and report the command used.
+
+## Review Checklist
+
+- Does the file use valid syntax for the selected language?
+- Does execution produce `Hello World` without extra output?
+- Is the documented run command appropriate for the current project?
+- Are setup failures reported clearly instead of being hidden?

package/skills/summarize-skills/SKILL.md

@@ -0,0 +1,46 @@
+---
+name: summarize-skills
+description: 'Summarize the skills available in .github/skills by counting valid skill folders and explaining each skill purpose. Use for repository skill discovery, onboarding, documentation, or checking skill organization.'
+argument-hint: 'Optionally specify a skills directory or filtering criterion.'
+user-invocable: true
+---
+
+# Summarize Skills
+
+## Description
+Summarize all valid skills defined under `.github/skills/` by listing how many there are and what each skill does.
+
+## Purpose
+- Provide a quick overview of available skills
+- Help users understand the role of each skill
+- Make it easier to discover and reuse skills
+
+## Usage Scenarios
+- Reviewing skills in a repository
+- Teaching beginners how skills are organized
+- Creating documentation or onboarding material
+
+## Procedure
+
+1. Scan `.github/skills/` for skill directories containing a `SKILL.md` file.
+2. Read each file's YAML frontmatter and collect its `name` and `description`.
+3. Confirm that each frontmatter `name` matches its parent folder name.
+4. Count the valid skills and summarize each purpose in a concise list or table.
+5. Report invalid or incomplete skill folders separately without silently treating them as valid skills.
+
+## Output Format
+
+Present:
+
+- the total number of valid skills
+- each skill name and its purpose
+- any folders missing `SKILL.md` or required frontmatter
+
+Prefer a compact Markdown table for the valid skills.
+
+## Review Checklist
+
+- Were only folders containing `SKILL.md` counted as skills?
+- Were `name` and `description` read from frontmatter rather than inferred from headings?
+- Does every reported skill name match its folder name?
+- Are invalid or incomplete entries clearly identified?