palskills 1.0.1 → 1.0.3

package/README.md

@@ -2,29 +2,7 @@
 
 **AI-powered development pipeline** — a suite of 5 Hermes Agent skills that orchestrate the full development lifecycle: context retrieval → planning → execution via Codex CLI → archival.
 
-```
-User Prompt
-     │
-     ▼
-┌──────────────────────────────────────────────────────┐
-│                                                      │
-│  🔮 Astralym — State Machine Core                    │
-│     Routes every prompt through the pipeline          │
-│                                                      │
-│     ├─► 📖 Lyleen — Palbox Reader & Bootstrapper     │
-│     │   Checks .palbox/ for context; creates if new   │
-│     │                                                 │
-│     ├─► 🐉 Jetdragon — Planner                       │
-│     │   Asks clarifying questions → detailed plan     │
-│     │                                                 │
-│     ├─► ⚔️ Anubis — Codex Development Engine         │
-│     │   Builds Codex prompt → codex exec (SOLID+SRP)  │
-│     │                                                 │
-│     └─► 📝 Panthalus — Palbox Archivist              │
-│         Records plan + execution → .palbox/history/   │
-│                                                      │
-└──────────────────────────────────────────────────────┘
-```
+![Palskills Pipeline](assets/pipeline.jpg?v=2)
 
 ## Skills
 

package/bin/palskills.js

@@ -111,19 +111,19 @@ ALL code, comments, docstrings, variable names, and commit messages MUST be in E
 
 ## Palbox Knowledge Graph (CRITICAL)
 ### Before you start ANY task
-1. **Check if `.palbox/` exists.** If not, the project hasn't been bootstrapped yet.
+1. **Check if .palbox/ exists.** If not, the project has not been bootstrapped yet.
 2. **Read the core nodes:**
-   - `.palbox/README.md` — project identity, tech stack, goals
-   - `.palbox/architecture.md` — folder structure, design patterns, key modules
-   - `.palbox/methods.md` — coding conventions, testing strategy, git workflow
+   - .palbox/README.md — project identity, tech stack, goals
+   - .palbox/architecture.md — folder structure, design patterns, key modules
+   - .palbox/methods.md — coding conventions, testing strategy, git workflow
 3. **Search for related past work:**
-   - Search for keywords in `.palbox/flows/` and `.palbox/history/`
-   - Follow `[[wikilinks]]` to discover connected context
-4. **Read relevant flows** in `.palbox/flows/` — they document how features work end-to-end
-5. **Read relevant history** in `.palbox/history/` — past plans, executions, lessons learned
+   - Search for keywords in .palbox/flows/ and .palbox/history/
+   - Follow wikilinks to discover connected context
+4. **Read relevant flows** in .palbox/flows/ — they document how features work end-to-end
+5. **Read relevant history** in .palbox/history/ — past plans, executions, lessons learned
 
 ### After you complete a task
-- Record what you did. The Palskills system (Panthalus) will create a `.palbox/history/YYYY-MM-DD-feature.md` node with `[[wikilinks]]` to related entries.
+- Record what you did. The Palskills system (Panthalus) will create a .palbox/history/YYYY-MM-DD-feature.md node with wikilinks to related entries.
 - If you discovered new patterns, conventions, or pitfalls, note them — they enrich the graph.
 `;
 }
@@ -159,15 +159,15 @@ ALL code, comments, docs, variable names, and commit messages MUST be in English
 
 ### Project Context — Palbox Knowledge Graph
 Before you start ANY task:
-1. **Check if `.palbox/` exists.** Read the core nodes:
-   - `.palbox/README.md` — project identity, stack, goals
-   - `.palbox/architecture.md` — folder structure, patterns, key modules
-   - `.palbox/methods.md` — conventions, testing, git workflow
-2. **Search `.palbox/flows/` and `.palbox/history/`** for related past work.
-3. **Follow `[[wikilinks]]`** — they connect related nodes in the knowledge graph.
+1. **Check if .palbox/ exists.** Read the core nodes:
+   - .palbox/README.md — project identity, stack, goals
+   - .palbox/architecture.md — folder structure, patterns, key modules
+   - .palbox/methods.md — conventions, testing, git workflow
+2. **Search .palbox/flows/ and .palbox/history/** for related past work.
+3. **Follow wikilinks** — they connect related nodes in the knowledge graph.
 
 After completing work:
-- The Palskills system (Panthalus) records to `.palbox/history/` with bi-directional links.
+- The Palskills system (Panthalus) records to .palbox/history/ with bi-directional links.
 
 ### Code Quality
 - No file exceeds 200 lines without strong justification.
@@ -219,15 +219,15 @@ ALL code, comments, docstrings, variable names, function names, and commit messa
 
 ## Project Context — Palbox Knowledge Graph
 Before starting any task:
-1. Check if `.palbox/` exists. Read the core nodes:
-   - `.palbox/README.md` — project identity, stack, goals
-   - `.palbox/architecture.md` — folder structure, patterns, key modules
-   - `.palbox/methods.md` — conventions, testing, git workflow
-2. Search `.palbox/flows/` and `.palbox/history/` for related past work.
-3. Follow `[[wikilinks]]` — they connect related nodes in the knowledge graph.
+1. Check if .palbox/ exists. Read the core nodes:
+   - .palbox/README.md — project identity, stack, goals
+   - .palbox/architecture.md — folder structure, patterns, key modules
+   - .palbox/methods.md — conventions, testing, git workflow
+2. Search .palbox/flows/ and .palbox/history/ for related past work.
+3. Follow wikilinks — they connect related nodes in the knowledge graph.
 
 After completing work:
-- The Palskills system (Panthalus) records your session to `.palbox/history/` with bi-directional `[[wikilinks]]`.
+- The Palskills system (Panthalus) records your session to .palbox/history/ with bi-directional wikilinks.
 - If you discovered patterns, pitfalls, or conventions worth preserving, note them.
 `;
 }

package/install.js

@@ -0,0 +1,38 @@
+#!/usr/bin/env node
+const fs = require('fs');
+const path = require('path');
+const os = require('os');
+
+const GREEN = '\x1b[32m';
+const YELLOW = '\x1b[33m';
+const NC = '\x1b[0m';
+
+const hermesHome = process.env.HERMES_HOME || path.join(os.homedir(), '.hermes');
+const target = path.join(hermesHome, 'skills', 'palskills');
+const src = path.join(__dirname, '..', 'skills');
+
+console.log('╔══════════════════════════════════════╗');
+console.log('║     Palskills Installer             ║');
+console.log('╚══════════════════════════════════════╝');
+console.log('');
+
+if (!fs.existsSync(src)) {
+  console.log(`  ${YELLOW}⚠${NC}  Skills source not found. Skipping.`);
+  process.exit(0);
+}
+
+fs.mkdirSync(target, { recursive: true });
+
+const skills = fs.readdirSync(src);
+for (const skill of skills) {
+  const skillMd = path.join(src, skill, 'SKILL.md');
+  if (fs.existsSync(skillMd)) {
+    const dest = path.join(target, skill);
+    fs.mkdirSync(dest, { recursive: true });
+    fs.copyFileSync(skillMd, path.join(dest, 'SKILL.md'));
+    console.log(`  ${GREEN}✓${NC} ${skill}`);
+  }
+}
+
+console.log('');
+console.log(`  ${GREEN}✅ Done!${NC} Skills installed to ${target}`);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "palskills",
-  "version": "1.0.1",
+  "version": "1.0.3",
   "description": "AI-powered development pipeline — 5 Hermes Agent skills orchestrated as a knowledge graph",
   "keywords": [
     "hermes-agent",
@@ -30,9 +30,9 @@
   "files": [
     "skills/",
     "bin/",
-    "install.sh"
+    "install.js"
   ],
   "scripts": {
-    "postinstall": "bash install.sh"
+    "postinstall": "node install.js"
   }
 }

package/install.sh

@@ -1,43 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-
-HERMES_SKILLS="${HERMES_HOME:-$HOME/.hermes}/skills"
-TARGET="${HERMES_SKILLS}/palskills"
-
-echo "╔══════════════════════════════════════╗"
-echo "║     Palskills Installer             ║"
-echo "╚══════════════════════════════════════╝"
-echo ""
-
-# Check Hermes skills directory
-if [ ! -d "$HERMES_SKILLS" ]; then
-    echo "📁 Creating Hermes skills directory: $HERMES_SKILLS"
-    mkdir -p "$HERMES_SKILLS"
-fi
-
-# Install each skill
-SKILLS_DIR="$(cd "$(dirname "$0")" && pwd)/skills"
-
-for skill in astralym lyleen jetdragon anubis panthalus; do
-    if [ -f "$SKILLS_DIR/$skill/SKILL.md" ]; then
-        echo "📦 Installing: $skill"
-        mkdir -p "$TARGET/$skill"
-        cp "$SKILLS_DIR/$skill/SKILL.md" "$TARGET/$skill/SKILL.md"
-    else
-        echo "⚠️  Warning: $skill/SKILL.md not found, skipping"
-    fi
-done
-
-echo ""
-echo "✅ Palskills installed to: $TARGET"
-echo ""
-echo "Skills ready:"
-ls -1 "$TARGET"/*/SKILL.md | while read f; do
-    dir=$(basename "$(dirname "$f")")
-    echo "  • $dir"
-done
-echo ""
-echo "Usage: In Hermes Agent, invoke any skill by name:"
-echo "  - 'Load the astralym skill'"
-echo "  - 'Use lyleen to check palbox'"
-echo "  - 'Run jetdragon for planning'"