@supa-magic/spm 0.3.0 → 0.3.1

package/dist/bin/spm.js

@@ -79,6 +79,25 @@ const writeConfig = (config, root) => {
   const configPath = getConfigPath(root);
   writeFileSync(configPath, stringify(config), "utf-8");
 };
+const addConfigEntry = ({
+  providerPath,
+  kind,
+  name,
+  source
+}) => {
+  const { config } = readConfig();
+  const provider = Object.values(config.providers).find(
+    (p) => p.path === providerPath
+  );
+  if (!provider) {
+    throw new Error(`Provider with path "${providerPath}" not found in config`);
+  }
+  if (!provider[kind]) {
+    provider[kind] = {};
+  }
+  provider[kind][name] = source;
+  writeConfig(config);
+};
 const green = "\x1B[32m";
 const red = "\x1B[31m";
 const cyan = "\x1B[36m";
@@ -370,8 +389,8 @@ const downloadFile = async (source) => {
   const content = await getContent(source);
   return { content, source };
 };
-const template = '# Skillset Integration\n\nYou are integrating a new skillset into the project. Analyze the existing project setup and intelligently integrate the new files.\n\n## Context\n\n- **Downloaded files**: `{{downloadDir}}`\n- **Provider directory**: `{{providerDir}}`\n- **Skillset**: `{{skillsetName}}` v`{{skillsetVersion}}`\n- **Source**: `{{source}}`\n- **Config file**: `{{configPath}}`\n\nIdentical files have already been removed from the download folder. Only files that need action remain. If the download folder is empty, skip to the config update step.\n\n## Output Format\n\nCRITICAL — follow exactly:\n- NEVER wrap output in code blocks or backticks\n- NEVER write conversational text ("Now let me...", "Let me check...", "The files are...")\n- NEVER use emojis\n- Output ONLY structured log lines\n- Step headers are plain text ending with `...` — these are parsed by the CLI to drive spinner states\n- Items below headers are indented with 2 spaces and use `• ` prefix\n- File lists use ASCII tree: `├─`, `└─`, `│`\n- End with `Done` on its own line\n\nStep headers (use these exactly):\n\n1. `Analyzing existing setup...`\n2. `Analyzing downloaded files...`\n3. `Detecting conflicts...`\n4. `Integrating...`\n5. `Updating config...`\n6. `Running setup...` (only if a setup file exists)\n7. `Done`\n\nExample output:\n\nAnalyzing existing setup...\n  • 4 skills, 2 rules, 1 hook\n\nAnalyzing downloaded files...\n  • skills: git, github, implement\n  • rules: coding\n  • hook: biome-format\n\nDetecting conflicts...\n  • No conflicts\n\nIntegrating...\n  • skills/git/SKILL.md\n  • skills/git/branch.md\n  • skills/github/SKILL.md\n\nUpdating config...\n  • skillset: skill-creator@1.0.0\n\nRunning setup...\n  • Configured MCP server: biome\n\nDone\n\n## Step 1: Analyzing existing setup\n\nRead the provider directory (`{{providerDir}}`) and catalog what is already in place: skills, rules, agents, hooks, mcp servers files.\n\n## Step 2: Analyzing downloaded files\n\nRead all files in `{{downloadDir}}`. Only files present in this folder need to be installed.\n\n## Step 3: Detecting conflicts\n\nFor each downloaded file, check if a file with the same name exists in the provider directory.\n\n- **No existing file** → install as new\n- **Different skillset version** → replace silently (new version supersedes)\n- **Same version or no version info** → conflict — ask the user:\n\nDetecting conflicts...\n  • rules/coding.md — local has custom rules\n  • Choose: (r)eplace / (s)kip / (m)erge\n\nWait for response before proceeding.\n\n## Step 4: Integrating\n\nInstall files into `{{providerDir}}`, following the directory structure from the download folder.\n\n**Integrate, don\'t copy.** When a new skill can leverage existing project conventions, adapt it:\n\n- If the project has `rules/coding.md` with specific conventions → make new skills follow those rules instead of their own defaults\n- If existing skills handle branching or committing → reference them instead of duplicating instructions\n- If the project has naming conventions, testing patterns, or architectural rules → align new skills with them\n\n## Step 5: Updating config\n\nUpdate `{{configPath}}`:\n\n- Under the provider with path `{{providerDir}}`, add the skillset entry under `skillsets`:\n  `{{skillsetName}}: "{{source}}@{{skillsetVersion}}"`\n- Do NOT add individual skill, agent, or file names to the config\n- The `skills` map is reserved for standalone skill installations\n\n{{setupSection}}\n\n## Rules\n\n- Setup files are NOT installed — they contain instructions to configure the project\n- Do not delete or modify existing files in the provider directory unless resolving a conflict\n- Do NOT delete the download folder — cleanup is handled externally\n';
-const skillTemplate = '# Skill Integration\n\nYou are integrating a single skill into the project. Analyze the existing project setup and intelligently integrate the new files.\n\n## Context\n\n- **Downloaded files**: `{{downloadDir}}`\n- **Provider directory**: `{{providerDir}}`\n- **Skill**: `{{skillName}}`\n- **Source**: `{{source}}`\n- **Config file**: `{{configPath}}`\n\nIdentical files have already been removed from the download folder. Only files that need action remain. If the download folder is empty, skip to the config update step.\n\n## Output Format\n\nCRITICAL — follow exactly:\n- NEVER wrap output in code blocks or backticks\n- NEVER write conversational text ("Now let me...", "Let me check...", "The files are...")\n- NEVER use emojis\n- Output ONLY structured log lines\n- Step headers are plain text ending with `...` — these are parsed by the CLI to drive spinner states\n- Items below headers are indented with 2 spaces and use `• ` prefix\n- File lists use ASCII tree: `├─`, `└─`, `│`\n- End with `Done` on its own line\n\nStep headers (use these exactly):\n\n1. `Analyzing existing setup...`\n2. `Analyzing downloaded files...`\n3. `Detecting conflicts...`\n4. `Integrating...`\n5. `Updating config...`\n6. `Done`\n\nExample output:\n\nAnalyzing existing setup...\n  • 4 skills, 2 rules, 1 hook\n\nAnalyzing downloaded files...\n  • skill: git (3 files)\n\nDetecting conflicts...\n  • No conflicts\n\nIntegrating...\n  • skills/git/SKILL.md\n  • skills/git/branch.md\n\nUpdating config...\n  • skill: git\n\nDone\n\n## Step 1: Analyzing existing setup\n\nRead the provider directory (`{{providerDir}}`) and catalog what is already in place: skills, rules, agents, hooks, mcp servers files.\n\n## Step 2: Analyzing downloaded files\n\nRead all files in `{{downloadDir}}`. Only files present in this folder need to be installed.\n\n## Step 3: Detecting conflicts\n\nFor each downloaded file, check if a file with the same name exists in the provider directory.\n\n- **No existing file** → install as new\n- **Different content** → replace silently\n- **Same content** → skip (should already be pruned)\n\nDetecting conflicts...\n  • rules/coding.md — local has custom rules\n  • Choose: (r)eplace / (s)kip / (m)erge\n\nWait for response before proceeding.\n\n## Step 4: Integrating\n\nInstall files into `{{providerDir}}/skills/{{skillName}}/`, following the directory structure from the download folder.\n\n**Integrate, don\'t copy.** When a new skill can leverage existing project conventions, adapt it:\n\n- If the project has `rules/coding.md` with specific conventions → make new skills follow those rules instead of their own defaults\n- If existing skills handle branching or committing → reference them instead of duplicating instructions\n- If the project has naming conventions, testing patterns, or architectural rules → align new skills with them\n\n## Step 5: Updating config\n\nUpdate `{{configPath}}`:\n\n- Under the provider with path `{{providerDir}}`, add the skill entry under `skills`:\n  `{{skillName}}: "{{source}}"`\n- The `skillsets` map is reserved for skillset installations\n\n## Rules\n\n- Do not delete or modify existing files in the provider directory unless resolving a conflict\n- Do NOT delete the download folder — cleanup is handled externally\n';
+const template = '# Skillset Integration\n\nYou are integrating a new skillset into the project. Analyze the existing project setup and intelligently integrate the new files.\n\n## Context\n\n- **Downloaded files**: `{{downloadDir}}`\n- **Provider directory**: `{{providerDir}}`\n- **Skillset**: `{{skillsetName}}` v`{{skillsetVersion}}`\n\nIdentical files have already been removed from the download folder. Only files that need action remain. If the download folder is empty, output `Done` immediately.\n\n## Output Format\n\nCRITICAL — follow exactly:\n- NEVER wrap output in code blocks or backticks\n- NEVER write conversational text ("Now let me...", "Let me check...", "The files are...")\n- NEVER use emojis\n- Output ONLY structured log lines\n- Step headers are plain text ending with `...` — these are parsed by the CLI to drive spinner states\n- Items below headers are indented with 2 spaces and use `• ` prefix\n- File lists use ASCII tree: `├─`, `└─`, `│`\n- End with `Done` on its own line\n\nStep headers (use these exactly):\n\n1. `Analyzing existing setup...`\n2. `Analyzing downloaded files...`\n3. `Detecting conflicts...`\n4. `Integrating...`\n5. `Running setup...` (only if a setup file exists)\n6. `Done`\n\nExample output:\n\nAnalyzing existing setup...\n  • 4 skills, 2 rules, 1 hook\n\nAnalyzing downloaded files...\n  • skills: git, github, implement\n  • rules: coding\n  • hook: biome-format\n\nDetecting conflicts...\n  • No conflicts\n\nIntegrating...\n  • skills/git/SKILL.md\n  • skills/git/branch.md\n  • skills/github/SKILL.md\n\nRunning setup...\n  • Configured MCP server: biome\n\nDone\n\n## Step 1: Analyzing existing setup\n\nRead the provider directory (`{{providerDir}}`) and catalog what is already in place: skills, rules, agents, hooks, mcp servers files.\n\n## Step 2: Analyzing downloaded files\n\nRead all files in `{{downloadDir}}`. Only files present in this folder need to be installed.\n\n## Step 3: Detecting conflicts\n\nFor each downloaded file, check if a file with the same name exists in the provider directory.\n\n- **No existing file** → install as new\n- **Different skillset version** → replace silently (new version supersedes)\n- **Same version or no version info** → conflict — ask the user:\n\nDetecting conflicts...\n  • rules/coding.md — local has custom rules\n  • Choose: (r)eplace / (s)kip / (m)erge\n\nWait for response before proceeding.\n\n## Step 4: Integrating\n\nInstall files into `{{providerDir}}`, following the directory structure from the download folder.\n\n**Integrate, don\'t copy.** When a new skill can leverage existing project conventions, adapt it:\n\n- If the project has `rules/coding.md` with specific conventions → make new skills follow those rules instead of their own defaults\n- If existing skills handle branching or committing → reference them instead of duplicating instructions\n- If the project has naming conventions, testing patterns, or architectural rules → align new skills with them\n\n{{setupSection}}\n\n## Rules\n\n- Setup files are NOT installed — they contain instructions to configure the project\n- Do not delete or modify existing files in the provider directory unless resolving a conflict\n- Do NOT delete the download folder — cleanup is handled externally\n';
+const skillTemplate = '# Skill Integration\n\nYou are integrating a single skill into the project. Analyze the existing project setup and intelligently integrate the new files.\n\n## Context\n\n- **Downloaded files**: `{{downloadDir}}`\n- **Provider directory**: `{{providerDir}}`\n- **Skill**: `{{skillName}}`\n\nIdentical files have already been removed from the download folder. Only files that need action remain. If the download folder is empty, output `Done` immediately.\n\n## Output Format\n\nCRITICAL — follow exactly:\n- NEVER wrap output in code blocks or backticks\n- NEVER write conversational text ("Now let me...", "Let me check...", "The files are...")\n- NEVER use emojis\n- Output ONLY structured log lines\n- Step headers are plain text ending with `...` — these are parsed by the CLI to drive spinner states\n- Items below headers are indented with 2 spaces and use `• ` prefix\n- File lists use ASCII tree: `├─`, `└─`, `│`\n- End with `Done` on its own line\n\nStep headers (use these exactly):\n\n1. `Analyzing existing setup...`\n2. `Analyzing downloaded files...`\n3. `Detecting conflicts...`\n4. `Integrating...`\n5. `Done`\n\nExample output:\n\nAnalyzing existing setup...\n  • 4 skills, 2 rules, 1 hook\n\nAnalyzing downloaded files...\n  • skill: git (3 files)\n\nDetecting conflicts...\n  • No conflicts\n\nIntegrating...\n  • skills/git/SKILL.md\n  • skills/git/branch.md\n\nDone\n\n## Step 1: Analyzing existing setup\n\nRead the provider directory (`{{providerDir}}`) and catalog what is already in place: skills, rules, agents, hooks, mcp servers files.\n\n## Step 2: Analyzing downloaded files\n\nRead all files in `{{downloadDir}}`. Only files present in this folder need to be installed.\n\n## Step 3: Detecting conflicts\n\nFor each downloaded file, check if a file with the same name exists in the provider directory.\n\n- **No existing file** → install as new\n- **Different content** → replace silently\n- **Same content** → skip (should already be pruned)\n\nDetecting conflicts...\n  • rules/coding.md — local has custom rules\n  • Choose: (r)eplace / (s)kip / (m)erge\n\nWait for response before proceeding.\n\n## Step 4: Integrating\n\nInstall files into `{{providerDir}}/skills/{{skillName}}/`, following the directory structure from the download folder.\n\n**Integrate, don\'t copy.** When a new skill can leverage existing project conventions, adapt it:\n\n- If the project has `rules/coding.md` with specific conventions → make new skills follow those rules instead of their own defaults\n- If existing skills handle branching or committing → reference them instead of duplicating instructions\n- If the project has naming conventions, testing patterns, or architectural rules → align new skills with them\n\n## Rules\n\n- Do not delete or modify existing files in the provider directory unless resolving a conflict\n- Do NOT delete the download folder — cleanup is handled externally\n';
 const buildSetupSection = (setupFile) => setupFile ? [
   "## Step 6: Running setup",
   "",
@@ -379,14 +398,14 @@ const buildSetupSection = (setupFile) => setupFile ? [
   "Setup files configure the project environment (e.g. MCP servers, LSP, tooling).",
   "Do NOT copy the setup file into the provider directory — only execute its instructions."
 ].join("\n") : "";
-const buildInstructions = (input) => template.replace(/\{\{downloadDir\}\}/g, input.downloadDir).replace(/\{\{providerDir\}\}/g, input.providerDir).replace(/\{\{skillsetName\}\}/g, input.skillsetName).replace(/\{\{skillsetVersion\}\}/g, input.skillsetVersion).replace(/\{\{source\}\}/g, input.source).replace(/\{\{configPath\}\}/g, input.configPath).replace("{{setupSection}}", buildSetupSection(input.setupFile));
+const buildInstructions = (input) => template.replace(/\{\{downloadDir\}\}/g, input.downloadDir).replace(/\{\{providerDir\}\}/g, input.providerDir).replace(/\{\{skillsetName\}\}/g, input.skillsetName).replace(/\{\{skillsetVersion\}\}/g, input.skillsetVersion).replace("{{setupSection}}", buildSetupSection(input.setupFile));
 const writeInstructionsFile = (input) => {
   const filePath = join(tmpdir(), "spm", `install-${input.skillsetName}.md`);
   mkdirSync(dirname(filePath), { recursive: true });
   writeFileSync(filePath, buildInstructions(input), "utf-8");
   return filePath;
 };
-const buildSkillInstructions = (input) => skillTemplate.replace(/\{\{downloadDir\}\}/g, input.downloadDir).replace(/\{\{providerDir\}\}/g, input.providerDir).replace(/\{\{skillName\}\}/g, input.skillName).replace(/\{\{source\}\}/g, input.source).replace(/\{\{configPath\}\}/g, input.configPath);
+const buildSkillInstructions = (input) => skillTemplate.replace(/\{\{downloadDir\}\}/g, input.downloadDir).replace(/\{\{providerDir\}\}/g, input.providerDir).replace(/\{\{skillName\}\}/g, input.skillName);
 const writeSkillInstructionsFile = (input) => {
   const filePath = join(tmpdir(), "spm", `install-skill-${input.skillName}.md`);
   mkdirSync(dirname(filePath), { recursive: true });
@@ -1027,6 +1046,7 @@ const installSkillsetFlow = async (input, stepper, startedAt) => {
     stepper.succeed(`Skipped ${pruned} unchanged file(s)`);
   }
   const model = skillset.provider === "claude" ? "haiku" : void 0;
+  const source = `https://github.com/${location.owner}/${location.repository}/blob/${location.ref}/${location.path}`;
   const result = await installSkillset(
     {
       downloadDir,
@@ -1034,12 +1054,17 @@ const installSkillsetFlow = async (input, stepper, startedAt) => {
       providerDir: providerFullPath,
       skillsetName: skillset.name,
       skillsetVersion: skillset.version,
-      source: `@${location.owner}/${location.repository}`,
       configPath: getConfigPath(),
       model
     },
     stepper
   );
+  addConfigEntry({
+    providerPath: provider.path,
+    kind: "skillsets",
+    name: skillset.name,
+    source
+  });
   await rm(downloadDir, { recursive: true, force: true });
   const spmDir = join(projectRoot, ".spm");
   const remaining = await readdir(spmDir).catch(() => []);
@@ -1089,18 +1114,23 @@ const installSkillFlow = async (identifier, stepper, startedAt) => {
     stepper.succeed(`Skipped ${pruned} unchanged file(s)`);
   }
   const model = providerName === "claude" ? "haiku" : void 0;
-  const source = `@${resolved.location.owner}/${resolved.location.repository}`;
+  const source = `https://github.com/${resolved.location.owner}/${resolved.location.repository}/blob/${resolved.location.ref}/${resolved.location.path}`;
   const result = await installSingleSkill(
     {
       downloadDir,
       providerDir: providerFullPath,
       skillName: resolved.name,
-      source,
       configPath: getConfigPath(),
       model
     },
     stepper
   );
+  addConfigEntry({
+    providerPath,
+    kind: "skills",
+    name: resolved.name,
+    source
+  });
   await rm(downloadDir, { recursive: true, force: true });
   const spmDir = join(projectRoot, ".spm");
   const remaining = await readdir(spmDir).catch(() => []);
@@ -1153,7 +1183,7 @@ const banner = (version2) => [
   `${shade}▝▜${light}████▛▘  ${reset$1}${dim}v${version2} ✨ supa-magic${reset$1}`,
   `${shade}  ▘${light}  ▝`
 ].join("\n");
-const version = "0.3.0";
+const version = "0.3.1";
 const program = new Command();
 const gray = "\x1B[90m";
 const reset = "\x1B[0m";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@supa-magic/spm",
-  "version": "0.3.0",
+  "version": "0.3.1",
   "description": "CLI tool for managing AI skillsets",
   "license": "MIT",
   "contributors": [