spirewise 1.0.0

package/README.md

@@ -0,0 +1,68 @@
+# spirewise
+
+Installable **Agent Skills** for copywriting — generate ready-to-paste copy for
+your **F6S** and **LinkedIn** company pages, with strict character-limit safety.
+Works with **GitHub Copilot**, **Claude Code**, and **Cursor**.
+
+## Install
+
+No clone needed — run it with `npx`:
+
+```bash
+# install every skill
+npx spirewise install --all
+
+# install a single skill
+npx spirewise install f6s-copywriting
+
+# install several
+npx spirewise install f6s-copywriting linkedin-copywriting
+
+# interactive picker
+npx spirewise install
+
+# list what's available
+npx spirewise list
+```
+
+Or install the CLI globally:
+
+```bash
+npm install -g spirewise
+spirewise install --all
+```
+
+## Choose the target agent / folder
+
+```bash
+spirewise install --all --agent claude    # ~/.claude/skills  (default)
+spirewise install --all --agent copilot   # ~/.copilot/skills
+spirewise install --all --agent cursor    # ~/.cursor/skills
+spirewise install --all --target ./skills # any custom folder
+```
+
+Run `spirewise --help` for all options.
+
+## Skills included
+
+| Skill | Output file | Purpose |
+|-------|-------------|---------|
+| `f6s-copywriting` | `f6s/f6s-profile-copy.txt` | Full F6S startup profile copy |
+| `linkedin-copywriting` | `linkedin copywriting/linkedin-page-copy.txt` | Full LinkedIn Company Page copy |
+
+Each skill keeps **every field below** the platform's character limit (with ~10%
+headroom) and verifies counts before finishing.
+
+## Usage after install
+
+Once installed, just ask your agent:
+
+> "Write our F6S profile copy"
+> "Create the LinkedIn company page copy"
+
+The agent follows the skill: gathers your company details, writes the `.txt`
+file in the right folder, and confirms all character counts stay under limit.
+
+## License
+
+MIT

package/bin/cli.js

@@ -0,0 +1,169 @@
+#!/usr/bin/env node
+'use strict';
+
+/**
+ * spirewise — install copywriting Agent Skills into your AI agent.
+ *
+ * Usage:
+ *   npx spirewise list
+ *   npx spirewise install --all
+ *   npx spirewise install f6s-copywriting
+ *   npx spirewise install f6s-copywriting linkedin-copywriting
+ *   npx spirewise install                       (interactive picker)
+ *   npx spirewise install --agent cursor --all
+ *   npx spirewise install --target ./my/skills --all
+ */
+
+const fs = require('fs');
+const path = require('path');
+const readline = require('readline');
+
+const PKG_ROOT = path.resolve(__dirname, '..');
+const SKILLS_DIR = path.join(PKG_ROOT, 'skills');
+
+const c = {
+  reset: '\x1b[0m', blue: '\x1b[1;34m', green: '\x1b[1;32m',
+  yellow: '\x1b[1;33m', red: '\x1b[1;31m', dim: '\x1b[2m',
+};
+const info = (m) => console.log(`${c.blue}==>${c.reset} ${m}`);
+const ok = (m) => console.log(`${c.green} ok${c.reset} ${m}`);
+const warn = (m) => console.error(`${c.yellow}  !${c.reset} ${m}`);
+const die = (m) => { console.error(`${c.red}err${c.reset} ${m}`); process.exit(1); };
+
+const AGENT_DIRS = {
+  claude: path.join(os_home(), '.claude', 'skills'),
+  copilot: path.join(os_home(), '.copilot', 'skills'),
+  cursor: path.join(os_home(), '.cursor', 'skills'),
+};
+
+function os_home() {
+  return process.env.HOME || process.env.USERPROFILE || require('os').homedir();
+}
+
+function availableSkills() {
+  if (!fs.existsSync(SKILLS_DIR)) return [];
+  return fs.readdirSync(SKILLS_DIR, { withFileTypes: true })
+    .filter((d) => d.isDirectory() && fs.existsSync(path.join(SKILLS_DIR, d.name, 'SKILL.md')))
+    .map((d) => d.name)
+    .sort();
+}
+
+function copyDir(src, dest) {
+  fs.mkdirSync(dest, { recursive: true });
+  for (const entry of fs.readdirSync(src, { withFileTypes: true })) {
+    const s = path.join(src, entry.name);
+    const d = path.join(dest, entry.name);
+    if (entry.isDirectory()) copyDir(s, d);
+    else fs.copyFileSync(s, d);
+  }
+}
+
+function installSkill(skill, targetDir) {
+  const src = path.join(SKILLS_DIR, skill);
+  if (!fs.existsSync(src)) die(`Skill '${skill}' not found in package.`);
+  const dest = path.join(targetDir, skill);
+  copyDir(src, dest);
+  ok(`installed ${skill} ${c.dim}-> ${dest}${c.reset}`);
+}
+
+function usage() {
+  console.log(`spirewise — install copywriting Agent Skills
+
+Usage:
+  spirewise list
+  spirewise install [skill ...] [options]
+
+Commands:
+  list                  List available skills
+  install               Install skills (default command)
+
+Options:
+  --all                 Install every available skill
+  --agent <name>        Target agent: claude | copilot | cursor (default: claude)
+  --target <dir>        Install into a specific folder (overrides --agent)
+  -h, --help            Show this help
+
+Available skills:
+${availableSkills().map((s) => '  - ' + s).join('\n') || '  (none found)'}
+
+Examples:
+  npx spirewise install --all
+  npx spirewise install f6s-copywriting
+  npx spirewise install --agent cursor --all
+`);
+}
+
+function parseArgs(argv) {
+  const opts = { all: false, agent: 'claude', target: null, skills: [] };
+  for (let i = 0; i < argv.length; i++) {
+    const a = argv[i];
+    if (a === '--all') opts.all = true;
+    else if (a === '--agent') opts.agent = argv[++i] || die('--agent needs a value');
+    else if (a === '--target') opts.target = argv[++i] || die('--target needs a value');
+    else if (a === '-h' || a === '--help') { usage(); process.exit(0); }
+    else if (a.startsWith('-')) die(`Unknown option: ${a}`);
+    else opts.skills.push(a);
+  }
+  return opts;
+}
+
+function pick(available) {
+  return new Promise((resolve) => {
+    if (!process.stdin.isTTY) {
+      die("No skills specified. Use --all or name skills (run in a terminal for the picker).");
+    }
+    info('Select skills to install (space-separated numbers, or "a" for all):');
+    available.forEach((s, i) => console.log(`  ${i + 1}) ${s}`));
+    const rl = readline.createInterface({ input: process.stdin, output: process.stdout });
+    rl.question('  > ', (answer) => {
+      rl.close();
+      const t = answer.trim().toLowerCase();
+      if (t === 'a') return resolve(available.slice());
+      const chosen = [];
+      for (const tok of t.split(/\s+/)) {
+        const idx = parseInt(tok, 10) - 1;
+        if (idx >= 0 && idx < available.length) chosen.push(available[idx]);
+      }
+      resolve(chosen);
+    });
+  });
+}
+
+async function main() {
+  let argv = process.argv.slice(2);
+  let command = 'install';
+  if (argv[0] === 'list' || argv[0] === 'install') { command = argv[0]; argv = argv.slice(1); }
+  else if (argv[0] === '-h' || argv[0] === '--help') { usage(); return; }
+
+  const available = availableSkills();
+  if (available.length === 0) die('No skills found in package.');
+
+  if (command === 'list') {
+    info('Available skills:');
+    available.forEach((s) => console.log('  - ' + s));
+    return;
+  }
+
+  const opts = parseArgs(argv);
+
+  if (opts.agent && !AGENT_DIRS[opts.agent] && !opts.target) {
+    die(`Unknown agent '${opts.agent}' (use claude | copilot | cursor)`);
+  }
+  const targetDir = opts.target ? path.resolve(opts.target) : AGENT_DIRS[opts.agent];
+
+  let selected = opts.all ? available.slice() : opts.skills.slice();
+  if (selected.length === 0) selected = await pick(available);
+  if (selected.length === 0) die('Nothing selected.');
+
+  for (const s of selected) {
+    if (!available.includes(s)) die(`Unknown skill '${s}'. Run "spirewise list" to see options.`);
+  }
+
+  info(`Target: ${targetDir}`);
+  fs.mkdirSync(targetDir, { recursive: true });
+  for (const s of selected) installSkill(s, targetDir);
+  ok(`Done. Installed ${selected.length} skill(s).`);
+  info('Restart your agent or reload skills if needed.');
+}
+
+main().catch((e) => die(e && e.message ? e.message : String(e)));

package/package.json

@@ -0,0 +1,34 @@
+{
+  "name": "spirewise",
+  "version": "1.0.0",
+  "description": "Installable Agent Skills for copywriting (F6S & LinkedIn company pages) for GitHub Copilot, Claude Code, and Cursor.",
+  "bin": {
+    "spirewise": "bin/cli.js"
+  },
+  "files": [
+    "bin/",
+    "skills/"
+  ],
+  "scripts": {
+    "test": "node bin/cli.js list"
+  },
+  "keywords": [
+    "agent-skills",
+    "skills",
+    "copywriting",
+    "f6s",
+    "linkedin",
+    "github-copilot",
+    "claude-code",
+    "cursor",
+    "cli"
+  ],
+  "license": "MIT",
+  "engines": {
+    "node": ">=14"
+  },
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/spirerise/spirewise.git"
+  }
+}

package/skills/README.md

@@ -0,0 +1,66 @@
+# Copywriting Skills
+
+Portable [Agent Skills](https://code.visualstudio.com/) for generating
+ready-to-paste copy for company profile pages, with strict character-limit safety.
+
+## Skills
+
+| Skill | Output | Purpose |
+|-------|--------|---------|
+| `f6s-copywriting` | `f6s/f6s-profile-copy.txt` | Full F6S startup profile copy |
+| `linkedin-copywriting` | `linkedin copywriting/linkedin-page-copy.txt` | Full LinkedIn Company Page copy |
+
+Each skill writes one plain-text file and keeps **every field below** the
+platform's character limit (with ~10% headroom).
+
+## How to use with each agent
+
+These follow the standard `SKILL.md` format (YAML frontmatter + instructions), so
+they work anywhere a skill folder is recognized. To activate:
+
+- **Claude Code**: copy a skill folder into `.claude/skills/` (or `~/.claude/skills/`),
+  then ask e.g. "write our F6S profile".
+- **GitHub Copilot**: reference the skill file in chat, or place it where your
+  Copilot setup loads skills/instructions, then ask for the F6S/LinkedIn copy.
+- **Cursor**: point Cursor at the relevant `SKILL.md` (e.g. add it to context or
+  your rules) and ask for the copy.
+
+Either way, just ask the agent to "create the F6S page copy" or "write the
+LinkedIn company page copy" and it will follow the skill: gather inputs, write the
+`.txt` file in the right folder, and verify all character counts.
+
+## Install via command
+
+The easiest way is the npm CLI (skills are bundled in the package):
+
+```bash
+npx spirewise install --all                 # install every skill
+npx spirewise install f6s-copywriting       # install just one
+npx spirewise install                       # interactive picker
+npx spirewise list                          # list available skills
+```
+
+Target a specific agent or folder:
+
+```bash
+npx spirewise install --all --agent claude   # ~/.claude/skills (default)
+npx spirewise install --all --agent copilot  # ~/.copilot/skills
+npx spirewise install --all --agent cursor   # ~/.cursor/skills
+npx spirewise install --all --target ./skills
+```
+
+### No-Node fallback: `install.sh`
+
+If you can't use npm, the bundled `install.sh` does the same over `curl`:
+
+```bash
+# from a clone
+./install.sh --all
+
+# remote
+curl -fsSL https://raw.githubusercontent.com/spirerise/spirewise/main/install.sh | bash -s -- --all
+```
+
+Run `./install.sh --help` or `npx spirewise --help` for all options.
+
+

package/skills/f6s-copywriting/SKILL.md

@@ -0,0 +1,132 @@
+---
+name: f6s-copywriting
+description: >-
+  Generate complete, ready-to-paste copywriting for an F6S (f6s.com) startup/company
+  profile page. Use when the user asks to "write our F6S profile", "create F6S
+  copy", "fill out F6S page", or prepare content for an accelerator / investor
+  application on F6S. Produces a single .txt file under an `f6s/` folder in the
+  project root, with every field kept STRICTLY under its character limit.
+---
+
+# F6S Profile Copywriting
+
+Produce field-by-field copy for an F6S company profile, save it to a plain-text
+file, and guarantee every field stays **below** the platform character limits.
+
+## When to use
+
+The user wants copy for their F6S page (startup directory, accelerator/investor
+applications, hiring, or funding). If you lack details about the company, ask a
+few focused questions first (see "Inputs needed").
+
+## Inputs needed
+
+Before writing, gather (ask the user, or infer from the repo/website if available):
+
+- Company name and a one-line description of what it does
+- Industry / market and target customer
+- Stage (idea, MVP, pre-revenue, seed, scale, etc.) and business model
+- Key traction (users, revenue, growth, partnerships, awards, press)
+- What they are seeking (funding, talent, partners, customers)
+- Founders / key team, location, founded date, website, social links
+
+If the user says "just draft it", make reasonable, clearly-marked placeholder
+assumptions (e.g. `[FOUNDED: 2023]`) rather than blocking.
+
+## Output location
+
+1. Create a folder named `f6s` in the **project root** if it does not exist.
+2. Write a single file: `f6s/f6s-profile-copy.txt`.
+3. Use UTF-8 plain text only (no markdown styling inside the .txt).
+
+## F6S fields and HARD character limits
+
+Treat these as ceilings. **Always stay below the limit** — leave ~10% headroom
+and never emit a field that reaches or exceeds the cap. After writing each field,
+count the characters and trim if needed.
+
+| Field                  | Limit (chars) | Target (stay under) | Notes |
+|------------------------|---------------|---------------------|-------|
+| Company name           | 50            | ≤ 40                | Public/legal name |
+| Tagline / one-liner    | 140           | ≤ 120               | Plain, specific, no hype |
+| Short description      | 255           | ≤ 230               | 1–2 sentences, what + for whom |
+| Full description       | 2000          | ≤ 1800              | Mission, product, differentiation, goals |
+| Product description    | 1000          | ≤ 900               | Features + what makes it different |
+| Business model         | 500           | ≤ 450               | How you make money |
+| Traction / achievements| 1000          | ≤ 900               | Concrete metrics, awards, press |
+| Needs / what we seek   | 500           | ≤ 450               | Funding / talent / partners |
+| Team member bio (each) | 500           | ≤ 450               | Per person |
+| Market / industry tags | n/a (select)  | —                   | Pick from F6S list |
+
+If the platform shows a different live limit than above, obey the live limit and
+keep the same "stay under" headroom rule.
+
+## Copy rules (F6S style)
+
+- Be **specific and factual**. Avoid "best", "world-class", "#1", "revolutionary".
+- Lead with the problem and the customer, then the solution.
+- Use real numbers for traction; if unknown, insert a clear `[PLACEHOLDER]`.
+- Write in third person or first-person plural ("we") consistently.
+- No keyword stuffing; F6S profiles are read by humans (accelerators/investors).
+
+## Required .txt output template
+
+Write the file using exactly this structure. Put the live character count in
+brackets after each filled field, e.g. `(118/140)`.
+
+```
+F6S PROFILE COPY — <Company Name>
+Generated: <YYYY-MM-DD>
+
+[COMPANY NAME]            (xx/50)
+<value>
+
+[TAGLINE / ONE-LINER]    (xx/140)
+<value>
+
+[SHORT DESCRIPTION]      (xx/255)
+<value>
+
+[FULL DESCRIPTION]       (xx/2000)
+<value>
+
+[PRODUCT DESCRIPTION]    (xx/1000)
+<value>
+
+[BUSINESS MODEL]         (xx/500)
+<value>
+
+[TRACTION & ACHIEVEMENTS](xx/1000)
+<value>
+
+[NEEDS / SEEKING]        (xx/500)
+<value>
+
+[MARKET / INDUSTRY]
+<comma-separated tags>
+
+[LOCATION]
+<city, country>
+
+[FOUNDED]
+<month year>
+
+[WEBSITE]
+<url>
+
+[SOCIAL LINKS]
+LinkedIn: <url>
+X/Twitter: <url>
+Other: <url>
+
+[TEAM]
+- <Name> — <Role> — <≤450 char bio> — <LinkedIn url>
+```
+
+## Verification checklist (run before finishing)
+
+1. The `f6s/` folder exists in the project root and contains `f6s-profile-copy.txt`.
+2. Every length-limited field shows a `(count/limit)` and `count < limit` with headroom.
+3. No field is empty unless intentionally a `[PLACEHOLDER]`.
+4. No banned hype words; tone is factual and specific.
+5. Confirm counts programmatically (e.g. `awk`/`wc -m` per field) — do not trust eyeballing.

package/skills/linkedin-copywriting/SKILL.md

@@ -0,0 +1,120 @@
+---
+name: linkedin-copywriting
+description: >-
+  Generate complete, ready-to-paste copywriting for a LinkedIn Company Page.
+  Use when the user asks to "write our LinkedIn page", "create LinkedIn company
+  copy", "fill out the About section", or prepare LinkedIn page content. Produces
+  a single .txt file under a `linkedin copywriting/` folder in the project root,
+  with every field kept STRICTLY under its character limit.
+---
+
+# LinkedIn Company Page Copywriting
+
+Produce field-by-field copy for a LinkedIn **Company Page**, save it to a plain-text
+file, and guarantee every field stays **below** LinkedIn's character limits.
+
+## When to use
+
+The user wants copy for their LinkedIn company/organization page (tagline, About
+section, specialties, etc.). If company details are missing, ask focused
+questions first (see "Inputs needed").
+
+## Inputs needed
+
+Before writing, gather (ask the user, or infer from the repo/website if available):
+
+- Company name and what it does in one line
+- Industry, target audience, and core offerings
+- Mission / values and key differentiators
+- Top keywords customers/recruiters would search (for tagline + specialties + SEO)
+- Website, headquarters location, company size, founded year
+
+If the user says "just draft it", use clearly-marked placeholders (e.g.
+`[FOUNDED: 2023]`) instead of blocking.
+
+## Output location
+
+1. Create a folder named `linkedin copywriting` in the **project root** if it does not exist.
+2. Write a single file: `linkedin copywriting/linkedin-page-copy.txt`.
+3. Use UTF-8 plain text only (no markdown styling inside the .txt).
+
+## LinkedIn Company Page fields and HARD character limits
+
+Treat these as ceilings. **Always stay below the limit** — leave ~10% headroom
+and never emit a field that reaches or exceeds the cap. Count characters per
+field and trim if needed.
+
+| Field                        | Limit (chars) | Target (stay under) | Notes |
+|------------------------------|---------------|---------------------|-------|
+| Company name                 | 100           | ≤ 90                | Official name |
+| Tagline                      | 120           | ≤ 110               | Appears under the name; keyword-rich |
+| About / Overview             | 2000          | ≤ 1800              | Front-load value in first ~150 chars (preview) |
+| Specialty (each item)        | 30            | ≤ 28                | Up to 20 items total |
+| Specialties (total count)    | 20 items      | ≤ 20                | Keyword phrases |
+| Custom button / CTA text     | (preset)      | —                   | Choose from LinkedIn presets |
+| Featured post / update text  | 3000          | ≤ 2700              | If drafting a launch/intro post |
+
+If LinkedIn shows a different live limit than above, obey the live limit and keep
+the same "stay under" headroom rule.
+
+## Copy rules (LinkedIn style)
+
+- **Front-load the About section**: the first ~150 characters show as a preview
+  before "see more", so lead with the strongest value statement and keywords.
+- Write for both **humans and search** — include the terms recruiters, customers,
+  and partners would search, naturally (no stuffing).
+- Tagline should be benefit- or keyword-led, not a slogan with no information.
+- Specialties = short keyword phrases (services, technologies, markets), each ≤ 28 chars.
+- Tone: professional, confident, specific. Avoid empty hype.
+- End the About section with a clear next step (visit site, follow, contact).
+
+## Required .txt output template
+
+Write the file using exactly this structure. Put the live character count in
+brackets after each filled field, e.g. `(108/120)`.
+
+```
+LINKEDIN COMPANY PAGE COPY — <Company Name>
+Generated: <YYYY-MM-DD>
+
+[COMPANY NAME]           (xx/100)
+<value>
+
+[TAGLINE]                (xx/120)
+<value>
+
+[ABOUT / OVERVIEW]       (xx/2000)
+<value (first ~150 chars are the preview — make them count)>
+
+[SPECIALTIES]            (count: xx/20)
+1. <item> (xx/30)
+2. <item> (xx/30)
+...
+
+[WEBSITE]
+<url>
+
+[INDUSTRY]
+<value>
+
+[COMPANY SIZE]
+<range, e.g. 11-50 employees>
+
+[HEADQUARTERS]
+<city, country>
+
+[FOUNDED]
+<year>
+
+[OPTIONAL — LAUNCH/INTRO POST]  (xx/3000)
+<value>
+```
+
+## Verification checklist (run before finishing)
+
+1. The `linkedin copywriting/` folder exists in the project root and contains
+   `linkedin-page-copy.txt`.
+2. Every length-limited field shows a `(count/limit)` and `count < limit` with headroom.
+3. Specialties: ≤ 20 items, each ≤ 28 chars.
+4. About section's first ~150 chars work as a standalone preview hook.
+5. Confirm counts programmatically (e.g. `awk`/`wc -m` per field) — do not trust eyeballing.