@litfamily/litgravity 0.1.9 → 0.1.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/lib/list.mjs CHANGED
@@ -1,5 +1,5 @@
1
1
  import { agentNames } from './bundle.mjs';
2
- import { SKILL_ROUTES, KEYWORD_ROUTES, MOVED_SKILLS, movedInstallLine } from '../plugin/hooks/lib/routes.mjs';
2
+ import { SKILL_ROUTES, KEYWORD_ROUTES, MOVED_SKILLS, EXTENSIONS_CLI, extensionLines } from '../plugin/hooks/lib/routes.mjs';
3
3
 
4
4
  // The route listing a user can read without starting agy: every skill with the words that reach it, what it is for and,
5
5
  // for a skill that moved to wjgoarxiv-skills, the plugin that holds it now. It reads the same tables the router and the
@@ -25,7 +25,10 @@ export function list({ flags = {}, print = console.log }) {
25
25
  print(` ${r.when}`);
26
26
  print(` ${how}`);
27
27
  }
28
- if (rows.some((r) => r.moved)) print(`A moved skill installs with: ${movedInstallLine('<id>')}`);
28
+ if (rows.some((r) => r.moved)) {
29
+ print(`A moved skill installs with \`${EXTENSIONS_CLI} install <id>\` (a dry run; add --yes), and \`${EXTENSIONS_CLI} list\` shows what is installed. By hand, the same steps are these four lines, pasted in order with its id:`);
30
+ for (const line of extensionLines('<id>')) print(` ${line}`);
31
+ }
29
32
  print(`Agents: ${agents.join(', ')}`);
30
33
  return 0;
31
34
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@litfamily/litgravity",
3
- "version": "0.1.9",
3
+ "version": "0.1.10",
4
4
  "description": "Installer for LitGravity: skills, hooks and agents that help Google's Antigravity CLI (agy) plan, build, check and hand off work.",
5
5
  "keywords": [
6
6
  "antigravity",
@@ -1,7 +1,7 @@
1
1
  import { existsSync, mkdirSync, readFileSync, renameSync, writeFileSync } from 'node:fs';
2
2
  import { join } from 'node:path';
3
3
  import { homedir } from 'node:os';
4
- import { MOVED_SKILLS, movedInstallLine } from './routes.mjs';
4
+ import { MOVED_SKILLS, EXTENSION_BACKUPS, EXTENSIONS_CLI, extensionLines } from './routes.mjs';
5
5
 
6
6
  // The file-making skills are LitFamily extensions on the wjgoarxiv-skills shelf. The installer prints this notice
7
7
  // after a successful install or update and leaves a flag; the next real SessionStart hands it to the model once and
@@ -16,15 +16,20 @@ export function litgravityData(env = process.env) {
16
16
  export const oldRuntimeDir = (data) => join(data, 'runtime');
17
17
  const flagFile = (data) => join(data, 'extensions-notice.json');
18
18
 
19
- export function extensionNotice(data) {
19
+ /** `findings`: how many things `extensions check` asked to act on when the notice was queued (0 or absent: none). */
20
+ export function extensionNotice(data, { findings = 0 } = {}) {
20
21
  const lines = [
21
22
  'LitGravity is the LitFamily core for agy. It is complete and works on its own.',
22
23
  `The ${Object.keys(MOVED_SKILLS).length} skills that make files (decks, documents, figures, design, video covers) are LitFamily extensions now, kept on the extension shelf at ${EXTENSION_SHELF}.`,
23
- 'Install the ones you use alongside LitGravity to get the full LitFamily experience:',
24
+ `Install the ones you use alongside LitGravity to get the full LitFamily experience. The short route is one command in a terminal: \`${EXTENSIONS_CLI} install <id>\` shows what it would do and adds the skill with --yes (--project for one workspace); \`${EXTENSIONS_CLI} list\`, \`update\`, \`remove\` and \`check\` manage them after that.`,
25
+ 'By hand it is the same steps: clone the shelf once, then paste these four lines per skill, with its id. They list any same-name skill agy could load, move an existing copy into a dated folder under ' + EXTENSION_BACKUPS + ', copy the skill in and write a receipt. Run them again to update.',
24
26
  ` git clone ${EXTENSION_SHELF}`,
25
- ` ${movedInstallLine('<id>')}`,
27
+ ...extensionLines('<id>').map((line) => ` ${line}`),
26
28
  '`npx @litfamily/litgravity list` names the ids. A new conversation, or /skills reload, picks a copy up.',
27
29
  ];
30
+ if (findings > 0) {
31
+ lines.push(`\`${EXTENSIONS_CLI} check\` found ${findings} thing${findings === 1 ? '' : 's'} to look at among the extension copies already on this machine (a duplicate, or a copy without a receipt). Nothing was changed; run it to see each one with its fix.`);
32
+ }
28
33
  const runtime = oldRuntimeDir(data);
29
34
  if (existsSync(runtime)) {
30
35
  lines.push(`Earlier releases left their engines in ${runtime}. Nothing reads that folder now and the extensions keep their own, so you can delete it: rm -rf "${runtime}"`);
@@ -32,21 +37,21 @@ export function extensionNotice(data) {
32
37
  return lines;
33
38
  }
34
39
 
35
- export function queueExtensionNotice(data, version) {
40
+ export function queueExtensionNotice(data, version, { findings = 0 } = {}) {
36
41
  mkdirSync(data, { recursive: true });
37
42
  const tmp = `${flagFile(data)}.tmp-${process.pid}`;
38
- writeFileSync(tmp, `${JSON.stringify({ version, queuedAt: new Date().toISOString(), shown: false })}\n`);
43
+ writeFileSync(tmp, `${JSON.stringify({ version, queuedAt: new Date().toISOString(), shown: false, findings })}\n`);
39
44
  renameSync(tmp, flagFile(data));
40
45
  return flagFile(data);
41
46
  }
42
47
 
43
- /** True once per queued notice: the first caller marks it shown. */
48
+ /** The queued notice's options once per queued notice (the first caller marks it shown), otherwise false. */
44
49
  export function takeExtensionNotice(data) {
45
50
  try {
46
51
  const flag = JSON.parse(readFileSync(flagFile(data), 'utf8'));
47
52
  if (!flag || flag.shown !== false) return false;
48
53
  writeFileSync(flagFile(data), `${JSON.stringify({ ...flag, shown: true, shownAt: new Date().toISOString() })}\n`);
49
- return true;
54
+ return { findings: Number(flag.findings) || 0 };
50
55
  } catch {
51
56
  return false;
52
57
  }
@@ -1,7 +1,7 @@
1
1
  import { existsSync, readdirSync, readFileSync, statSync } from 'node:fs';
2
2
  import { dirname, join } from 'node:path';
3
3
  import { PLUGIN_ROOT, sessionPath, safeId } from './common.mjs';
4
- import { MOVED_SKILLS, movedInstallLine } from './routes.mjs';
4
+ import { MOVED_SKILLS, extensionLines, extensionCommand } from './routes.mjs';
5
5
 
6
6
  // The route a `lit` prompt finds already active in this conversation. A damaged, journal-only or odd-shaped state
7
7
  // counts as nothing active, so the prompt gets the full activation and rewrites the state.
@@ -76,7 +76,7 @@ export function resumeNote(plan) {
76
76
 
77
77
  // A moved skill's route reads its pointer stub; the note says so up front, with the install line, so the turn gives
78
78
  // that line (or hands over to the installed copy) and builds nothing from memory.
79
- const movedNote = (id) => `\`${id}\` is a LitFamily extension now, kept in wjgoarxiv-skills (variants/litgravity/${id}/); the file above is its pointer stub. If the stub finds no installed copy, give the user this install line and make nothing: ${movedInstallLine(id)}`;
79
+ const movedNote = (id) => `\`${id}\` is a LitFamily extension now, kept in wjgoarxiv-skills (variants/litgravity/${id}/); the file above is its pointer stub. If the stub finds no installed copy, make nothing and give the user the one command that installs it from a terminal (it prints its plan without --yes), \`${extensionCommand(id)}\`, or these four lines pasted in order:\n${extensionLines(id).join('\n')}`;
80
80
 
81
81
  export function activation(hit, conversationId, kind = 'ignite') {
82
82
  const id = safeId(conversationId);
@@ -62,8 +62,34 @@ export const MOVED_SKILLS = {
62
62
  'lit-typographic-motion': 'video-covers',
63
63
  'readme-studio': 'video-covers',
64
64
  };
65
- /** The one line that installs a moved skill for agy: copy its folder from a local clone into the user skills folder. */
66
- export const movedInstallLine = (id) => `mkdir -p ~/.gemini/config/skills && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/${id}" ~/.gemini/config/skills/`;
65
+ // Every folder agy 1.5.6 loads a bare skill from (probed 2026-11-12). A same-name skill in any of them competes with an
66
+ // installed copy, and agy keeps one without a word, so the preflight looks in all four.
67
+ export const AGY_SKILL_FOLDERS = ['.agents/skills', '_agents/skills', '~/.gemini/config/skills', '~/.gemini/skills'];
68
+ // Where a replaced or removed copy goes: a dated folder outside every folder above, so agy never loads it again.
69
+ export const EXTENSION_BACKUPS = '~/.gemini/extension-backups';
70
+ const CLONE = '<path to your wjgoarxiv-skills clone>';
71
+ const SCOPE_FOLDERS = { user: '~/.gemini/config/skills', project: '.agents/skills' };
72
+
73
+ /**
74
+ * The four lines that install, update or (the second alone) remove a moved skill, pasted one at a time in zsh or bash:
75
+ * look for every same-name skill, move an existing copy whole into a dated backup, copy into the emptied place, write
76
+ * a receipt inside the copy. Project scope runs in the workspace root.
77
+ */
78
+ export function extensionSteps(id, scope = 'user') {
79
+ const root = SCOPE_FOLDERS[scope];
80
+ const dest = `${root}/${id}`;
81
+ const stamp = `$(date +%Y%m%d-%H%M%S)${scope === 'project' ? '-project' : ''}`;
82
+ return {
83
+ preflight: `find ${AGY_SKILL_FOLDERS.join(' ')} -maxdepth 2 -name SKILL.md -exec grep -l -E '^name: *"?${id}"? *$' {} + 2>/dev/null`,
84
+ moveAside: `if [ -e ${dest} ] || [ -L ${dest} ]; then b=${EXTENSION_BACKUPS}/${stamp}; mkdir -p "$b" && mv ${dest} "$b/" && echo "moved to $b/${id}"; fi`,
85
+ copy: `mkdir -p ${root} && [ ! -e ${dest} ] && cp -R "${CLONE}/variants/litgravity/${id}" ${dest}`,
86
+ receipt: `printf '{"id":"%s","source":"%s","variant":"litgravity","installed_at":"%s"}\\n' ${id} "${CLONE}/variants/litgravity/${id}" "$(date -u +%Y-%m-%dT%H:%M:%SZ)" > ${dest}/.litfamily-extension.json`,
87
+ };
88
+ }
89
+ export const extensionLines = (id, scope = 'user') => Object.values(extensionSteps(id, scope));
90
+ // The same four steps done by LitGravity's own CLI (`litgravity extensions`), a dry run until --yes.
91
+ export const EXTENSIONS_CLI = 'npx @litfamily/litgravity extensions';
92
+ export const extensionCommand = (id, scope = 'user') => `${EXTENSIONS_CLI} install ${id}${scope === 'project' ? ' --project' : ''} --yes`;
67
93
  // Skill ids that are another name for a skill: typed whole, slashed or after `lit`, they take its route.
68
94
  export const SKILL_ALIASES = { 'lit-rewind': 'lit-adhd' };
69
95
  const skillId = (word) => (SKILL_IDS.has(word) ? word : SKILL_ALIASES[word]);
@@ -41,8 +41,9 @@ run((payload) => {
41
41
  // The installer queued the extensions notice; a real conversation (one with an id) takes it once. The doctor's hook
42
42
  // smoke sends an empty payload, so it never uses the notice up.
43
43
  const data = litgravityData();
44
- if (payload.conversationId && takeExtensionNotice(data)) {
45
- parts.push(`LitGravity was installed or updated just before this conversation. Once, in your first reply and after answering the user, add this short note in the user's language and keep the commands as written. Do not bring it up again.\n${extensionNotice(data).join('\n')}`);
44
+ const queued = payload.conversationId ? takeExtensionNotice(data) : false;
45
+ if (queued) {
46
+ parts.push(`LitGravity was installed or updated just before this conversation. Once, in your first reply and after answering the user, add this short note in the user's language and keep the commands as written. Do not bring it up again.\n${extensionNotice(data, queued).join('\n')}`);
46
47
  }
47
48
  const ws = workspaceOf(payload);
48
49
  const handoff = join(ws, '.litgravity', 'handoff', 'latest.md');
@@ -2,6 +2,6 @@
2
2
  "$schema": "https://antigravity.google/schemas/v1/plugin.json",
3
3
  "name": "litgravity",
4
4
  "description": "LitFamily workflows for the Antigravity CLI: bare lit activation, planning, evidence-bound execution, review, research, handoff and Korean prose care.",
5
- "version": "0.1.9",
5
+ "version": "0.1.10",
6
6
  "logo": "assets/logo.svg"
7
7
  }
@@ -12,10 +12,13 @@ The figure needs Python with matplotlib. LitGravity ships no plotting engine and
12
12
 
13
13
  1. **The installed figure skill.** `lit-scientific-visualization` moved to wjgoarxiv-skills; LitGravity keeps only a stub of that name. Look for the user's installed copy with `read_file`: first `~/.gemini/config/skills/lit-scientific-visualization/SKILL.md`, then `.agents/skills/lit-scientific-visualization/SKILL.md` in the workspace. When one is there, follow its own runtime section (its folder is the root for every path it names, and its engine caches outside this plugin), still under this file's authority and figure rules.
14
14
  2. **A local matplotlib.** When no copy is installed but the project already has a Python environment that imports matplotlib (or the user named an interpreter), run the plotting script with it; the style preset below keeps the figure in the house style.
15
- 3. **BLOCKED.** When neither exists, or `run_command` is refused, mark the figure step `BLOCKED` in one line of the report, give the optional install line from the stub, and keep the TSV as the evidence:
15
+ 3. **BLOCKED.** When neither exists, or `run_command` is refused, mark the figure step `BLOCKED` in one line of the report, give the optional install lines from the stub (pasted in order: look for same-name copies, move an old copy aside, copy, write the receipt), and keep the TSV as the evidence:
16
16
 
17
17
  ```bash
18
- mkdir -p ~/.gemini/config/skills && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-scientific-visualization" ~/.gemini/config/skills/
18
+ find .agents/skills _agents/skills ~/.gemini/config/skills ~/.gemini/skills -maxdepth 2 -name SKILL.md -exec grep -l -E '^name: *"?lit-scientific-visualization"? *$' {} + 2>/dev/null
19
+ if [ -e ~/.gemini/config/skills/lit-scientific-visualization ] || [ -L ~/.gemini/config/skills/lit-scientific-visualization ]; then b=~/.gemini/extension-backups/$(date +%Y%m%d-%H%M%S); mkdir -p "$b" && mv ~/.gemini/config/skills/lit-scientific-visualization "$b/" && echo "moved to $b/lit-scientific-visualization"; fi
20
+ mkdir -p ~/.gemini/config/skills && [ ! -e ~/.gemini/config/skills/lit-scientific-visualization ] && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-scientific-visualization" ~/.gemini/config/skills/lit-scientific-visualization
21
+ printf '{"id":"%s","source":"%s","variant":"litgravity","installed_at":"%s"}\n' lit-scientific-visualization "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-scientific-visualization" "$(date -u +%Y-%m-%dT%H:%M:%SZ)" > ~/.gemini/config/skills/lit-scientific-visualization/.litfamily-extension.json
19
22
  ```
20
23
 
21
24
  Never copy the skill in or install packages yourself, and never claim a figure that was not drawn and looked at. A headless run that cannot plot stops the figure step, never the run.
@@ -11,25 +11,38 @@ This file keeps the id. `lit frontend …`, `lit ui …`, a `lit` prompt that as
11
11
 
12
12
  ## Install it in agy
13
13
 
14
- wjgoarxiv-skills is public at https://github.com/wjgoarxiv/wjgoarxiv-skills. Clone it (`git clone https://github.com/wjgoarxiv/wjgoarxiv-skills`), then copy the skill folder into agy's user skills, which every workspace sees:
14
+ The short route is LitGravity's own command, run in a terminal: `npx @litfamily/litgravity extensions install frontend-ui-ux` prints what it would do, and the same with `--yes` does it (`--project` for one workspace). It fetches the skill, stops if another skill named frontend-ui-ux sits where agy loads skills, moves an old copy aside and writes the receipt; `extensions update`, `remove` and `check` do the rest. The lines below are the same steps by hand.
15
+
16
+ wjgoarxiv-skills is public at https://github.com/wjgoarxiv/wjgoarxiv-skills. Clone it (`git clone https://github.com/wjgoarxiv/wjgoarxiv-skills`), then paste these four lines one at a time (zsh or bash) in the workspace you use agy in. They put the skill in agy's user skills, which every workspace sees:
15
17
 
16
18
  ```bash
17
- mkdir -p ~/.gemini/config/skills && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/frontend-ui-ux" ~/.gemini/config/skills/
19
+ find .agents/skills _agents/skills ~/.gemini/config/skills ~/.gemini/skills -maxdepth 2 -name SKILL.md -exec grep -l -E '^name: *"?frontend-ui-ux"? *$' {} + 2>/dev/null
20
+ if [ -e ~/.gemini/config/skills/frontend-ui-ux ] || [ -L ~/.gemini/config/skills/frontend-ui-ux ]; then b=~/.gemini/extension-backups/$(date +%Y%m%d-%H%M%S); mkdir -p "$b" && mv ~/.gemini/config/skills/frontend-ui-ux "$b/" && echo "moved to $b/frontend-ui-ux"; fi
21
+ mkdir -p ~/.gemini/config/skills && [ ! -e ~/.gemini/config/skills/frontend-ui-ux ] && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/frontend-ui-ux" ~/.gemini/config/skills/frontend-ui-ux
22
+ printf '{"id":"%s","source":"%s","variant":"litgravity","installed_at":"%s"}\n' frontend-ui-ux "<path to your wjgoarxiv-skills clone>/variants/litgravity/frontend-ui-ux" "$(date -u +%Y-%m-%dT%H:%M:%SZ)" > ~/.gemini/config/skills/frontend-ui-ux/.litfamily-extension.json
18
23
  ```
19
24
 
20
- For one workspace only, run this in its root instead: `mkdir -p .agents/skills && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/frontend-ui-ux" .agents/skills/`.
25
+ Line one only looks: it prints every `SKILL.md` named frontend-ui-ux that agy could load, and nothing when there is none. agy keeps one same-name skill without a word, a workspace copy first, so move any other one it names aside too. Line two moves an existing copy whole into a dated folder under `~/.gemini/extension-backups/`, which agy never loads; line three copies into the emptied place; line four writes the receipt `.litfamily-extension.json` inside the copy.
26
+
27
+ For one workspace only, run line one, then these three in the workspace root:
28
+
29
+ ```bash
30
+ if [ -e .agents/skills/frontend-ui-ux ] || [ -L .agents/skills/frontend-ui-ux ]; then b=~/.gemini/extension-backups/$(date +%Y%m%d-%H%M%S)-project; mkdir -p "$b" && mv .agents/skills/frontend-ui-ux "$b/" && echo "moved to $b/frontend-ui-ux"; fi
31
+ mkdir -p .agents/skills && [ ! -e .agents/skills/frontend-ui-ux ] && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/frontend-ui-ux" .agents/skills/frontend-ui-ux
32
+ printf '{"id":"%s","source":"%s","variant":"litgravity","installed_at":"%s"}\n' frontend-ui-ux "<path to your wjgoarxiv-skills clone>/variants/litgravity/frontend-ui-ux" "$(date -u +%Y-%m-%dT%H:%M:%SZ)" > .agents/skills/frontend-ui-ux/.litfamily-extension.json
33
+ ```
21
34
 
22
- The folder is the whole skill, with its own scripts, references and engine locks. Its neighbours (visual-qa, the browser check that accepts a built interface) install the same way, one folder each. Start a new conversation, or type `/skills reload`; the skill then answers as `/frontend-ui-ux`, and `lit` prompts that reach this stub hand over to it. To update it, delete the copied folder and copy it again. The LitGravity installer writes only its own plugin folder, so upgrading or removing LitGravity leaves the copy alone, and the names never clash: this stub is `litgravity:frontend-ui-ux`, the copy is `frontend-ui-ux`.
35
+ The folder is the whole skill, with its own scripts, references and engine locks. Its neighbours (visual-qa, the browser check that accepts a built interface) install the same way, one folder each. Start a new conversation, or type `/skills reload`; the skill then answers as `/frontend-ui-ux`, and `lit` prompts that reach this stub hand over to it. To update it, run the same lines again: the old copy moves to a new dated backup and the receipt is rewritten. To remove it, run the second line alone. Nothing is deleted; clear old backups out of `~/.gemini/extension-backups/` when you no longer need them. The LitGravity installer writes only its own plugin folder, so upgrading or removing LitGravity leaves the copy alone, and the names never clash: this stub is `litgravity:frontend-ui-ux`, the copy is `frontend-ui-ux`.
23
36
 
24
37
  ## When this stub is read
25
38
 
26
39
  1. Look for the installed copy with `read_file`: first `~/.gemini/config/skills/frontend-ui-ux/SKILL.md`, then `.agents/skills/frontend-ui-ux/SKILL.md` in the workspace.
27
40
  2. **Found.** Read it and follow it for this task; its folder is the root for every relative path it names. It was written for agy and needs no LitGravity hook: every check it names is a command it tells you to run.
28
- 3. **Not found, asked directly.** Reply in a few lines: what frontend-ui-ux did, that it is a LitFamily extension now, kept in wjgoarxiv-skills (`variants/litgravity/frontend-ui-ux/`), the install line above, and that you made nothing yet. Do not build the page another way in its place; plain code edits to an existing interface stay with lit-code or litwork.
41
+ 3. **Not found, asked directly.** Reply in a few lines: what frontend-ui-ux did, that it is a LitFamily extension now, kept in wjgoarxiv-skills (`variants/litgravity/frontend-ui-ux/`), the `extensions install` command and the install lines above, and that you made nothing yet. Do not build the page another way in its place; plain code edits to an existing interface stay with lit-code or litwork.
29
42
  4. **Not found, inside a workflow.** A lit workflow that edits an interface keeps going without it: make the edit through lit-code or litwork, say once that frontend-ui-ux is not installed, and claim no design review.
30
43
 
31
44
  ## Hard stops
32
45
 
33
- - Give the install line with the placeholder; never a path from this machine.
46
+ - Give the install lines with the placeholder; never a path from this machine.
34
47
  - Never say an interface exists unless the installed copy made it and you looked at the result.
35
- - A headless run (`agy -p`) never copies the skill in itself: give the install line and stop.
48
+ - A headless run (`agy -p`) never copies the skill in itself: give the install lines and stop.
@@ -11,25 +11,38 @@ This file keeps the id. `lit diagram …`, `lit 다이어그램 …`, `lit 도
11
11
 
12
12
  ## Install it in agy
13
13
 
14
- wjgoarxiv-skills is public at https://github.com/wjgoarxiv/wjgoarxiv-skills. Clone it (`git clone https://github.com/wjgoarxiv/wjgoarxiv-skills`), then copy the skill folder into agy's user skills, which every workspace sees:
14
+ The short route is LitGravity's own command, run in a terminal: `npx @litfamily/litgravity extensions install lit-diagram-drawer` prints what it would do, and the same with `--yes` does it (`--project` for one workspace). It fetches the skill, stops if another skill named lit-diagram-drawer sits where agy loads skills, moves an old copy aside and writes the receipt; `extensions update`, `remove` and `check` do the rest. The lines below are the same steps by hand.
15
+
16
+ wjgoarxiv-skills is public at https://github.com/wjgoarxiv/wjgoarxiv-skills. Clone it (`git clone https://github.com/wjgoarxiv/wjgoarxiv-skills`), then paste these four lines one at a time (zsh or bash) in the workspace you use agy in. They put the skill in agy's user skills, which every workspace sees:
15
17
 
16
18
  ```bash
17
- mkdir -p ~/.gemini/config/skills && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-diagram-drawer" ~/.gemini/config/skills/
19
+ find .agents/skills _agents/skills ~/.gemini/config/skills ~/.gemini/skills -maxdepth 2 -name SKILL.md -exec grep -l -E '^name: *"?lit-diagram-drawer"? *$' {} + 2>/dev/null
20
+ if [ -e ~/.gemini/config/skills/lit-diagram-drawer ] || [ -L ~/.gemini/config/skills/lit-diagram-drawer ]; then b=~/.gemini/extension-backups/$(date +%Y%m%d-%H%M%S); mkdir -p "$b" && mv ~/.gemini/config/skills/lit-diagram-drawer "$b/" && echo "moved to $b/lit-diagram-drawer"; fi
21
+ mkdir -p ~/.gemini/config/skills && [ ! -e ~/.gemini/config/skills/lit-diagram-drawer ] && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-diagram-drawer" ~/.gemini/config/skills/lit-diagram-drawer
22
+ printf '{"id":"%s","source":"%s","variant":"litgravity","installed_at":"%s"}\n' lit-diagram-drawer "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-diagram-drawer" "$(date -u +%Y-%m-%dT%H:%M:%SZ)" > ~/.gemini/config/skills/lit-diagram-drawer/.litfamily-extension.json
18
23
  ```
19
24
 
20
- For one workspace only, run this in its root instead: `mkdir -p .agents/skills && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-diagram-drawer" .agents/skills/`.
25
+ Line one only looks: it prints every `SKILL.md` named lit-diagram-drawer that agy could load, and nothing when there is none. agy keeps one same-name skill without a word, a workspace copy first, so move any other one it names aside too. Line two moves an existing copy whole into a dated folder under `~/.gemini/extension-backups/`, which agy never loads; line three copies into the emptied place; line four writes the receipt `.litfamily-extension.json` inside the copy.
26
+
27
+ For one workspace only, run line one, then these three in the workspace root:
28
+
29
+ ```bash
30
+ if [ -e .agents/skills/lit-diagram-drawer ] || [ -L .agents/skills/lit-diagram-drawer ]; then b=~/.gemini/extension-backups/$(date +%Y%m%d-%H%M%S)-project; mkdir -p "$b" && mv .agents/skills/lit-diagram-drawer "$b/" && echo "moved to $b/lit-diagram-drawer"; fi
31
+ mkdir -p .agents/skills && [ ! -e .agents/skills/lit-diagram-drawer ] && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-diagram-drawer" .agents/skills/lit-diagram-drawer
32
+ printf '{"id":"%s","source":"%s","variant":"litgravity","installed_at":"%s"}\n' lit-diagram-drawer "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-diagram-drawer" "$(date -u +%Y-%m-%dT%H:%M:%SZ)" > .agents/skills/lit-diagram-drawer/.litfamily-extension.json
33
+ ```
21
34
 
22
- The folder is the whole skill, with its own scripts, references and engine locks. Its neighbours (lit-schematic and lit-scientific-visualization) install the same way, one folder each. Start a new conversation, or type `/skills reload`; the skill then answers as `/lit-diagram-drawer`, and `lit` prompts that reach this stub hand over to it. To update it, delete the copied folder and copy it again. The LitGravity installer writes only its own plugin folder, so upgrading or removing LitGravity leaves the copy alone, and the names never clash: this stub is `litgravity:lit-diagram-drawer`, the copy is `lit-diagram-drawer`.
35
+ The folder is the whole skill, with its own scripts, references and engine locks. Its neighbours (lit-schematic and lit-scientific-visualization) install the same way, one folder each. Start a new conversation, or type `/skills reload`; the skill then answers as `/lit-diagram-drawer`, and `lit` prompts that reach this stub hand over to it. To update it, run the same lines again: the old copy moves to a new dated backup and the receipt is rewritten. To remove it, run the second line alone. Nothing is deleted; clear old backups out of `~/.gemini/extension-backups/` when you no longer need them. The LitGravity installer writes only its own plugin folder, so upgrading or removing LitGravity leaves the copy alone, and the names never clash: this stub is `litgravity:lit-diagram-drawer`, the copy is `lit-diagram-drawer`.
23
36
 
24
37
  ## When this stub is read
25
38
 
26
39
  1. Look for the installed copy with `read_file`: first `~/.gemini/config/skills/lit-diagram-drawer/SKILL.md`, then `.agents/skills/lit-diagram-drawer/SKILL.md` in the workspace.
27
40
  2. **Found.** Read it and follow it for this task; its folder is the root for every relative path it names. It was written for agy and needs no LitGravity hook: every check it names is a command it tells you to run.
28
- 3. **Not found, asked directly.** Reply in a few lines: what lit-diagram-drawer did, that it is a LitFamily extension now, kept in wjgoarxiv-skills (`variants/litgravity/lit-diagram-drawer/`), the install line above, and that you made nothing yet. Do not draw the diagram another way in its place (a hand-written SVG, Mermaid, ASCII art).
29
- 4. **Not found, inside a workflow.** Inside a lit workflow (lit-loop, litwork, start-work, review-work) that reached this skill, write `lit-diagram-drawer not installed` once in the ledger and the reply with the install line, finish the parts that need no diagram, and mark the part that needs it BLOCKED, not done.
41
+ 3. **Not found, asked directly.** Reply in a few lines: what lit-diagram-drawer did, that it is a LitFamily extension now, kept in wjgoarxiv-skills (`variants/litgravity/lit-diagram-drawer/`), the `extensions install` command and the install lines above, and that you made nothing yet. Do not draw the diagram another way in its place (a hand-written SVG, Mermaid, ASCII art).
42
+ 4. **Not found, inside a workflow.** Inside a lit workflow (lit-loop, litwork, start-work, review-work) that reached this skill, write `lit-diagram-drawer not installed` once in the ledger and the reply with the install lines, finish the parts that need no diagram, and mark the part that needs it BLOCKED, not done.
30
43
 
31
44
  ## Hard stops
32
45
 
33
- - Give the install line with the placeholder; never a path from this machine.
46
+ - Give the install lines with the placeholder; never a path from this machine.
34
47
  - Never say a diagram exists unless the installed copy made it and you looked at the result.
35
- - A headless run (`agy -p`) never copies the skill in itself: give the install line and stop.
48
+ - A headless run (`agy -p`) never copies the skill in itself: give the install lines and stop.
@@ -11,25 +11,38 @@ This file keeps the id. `lit docx …`, `lit lit-docx …`, and `/litgravity:lit
11
11
 
12
12
  ## Install it in agy
13
13
 
14
- wjgoarxiv-skills is public at https://github.com/wjgoarxiv/wjgoarxiv-skills. Clone it (`git clone https://github.com/wjgoarxiv/wjgoarxiv-skills`), then copy the skill folder into agy's user skills, which every workspace sees:
14
+ The short route is LitGravity's own command, run in a terminal: `npx @litfamily/litgravity extensions install lit-docx` prints what it would do, and the same with `--yes` does it (`--project` for one workspace). It fetches the skill, stops if another skill named lit-docx sits where agy loads skills, moves an old copy aside and writes the receipt; `extensions update`, `remove` and `check` do the rest. The lines below are the same steps by hand.
15
+
16
+ wjgoarxiv-skills is public at https://github.com/wjgoarxiv/wjgoarxiv-skills. Clone it (`git clone https://github.com/wjgoarxiv/wjgoarxiv-skills`), then paste these four lines one at a time (zsh or bash) in the workspace you use agy in. They put the skill in agy's user skills, which every workspace sees:
15
17
 
16
18
  ```bash
17
- mkdir -p ~/.gemini/config/skills && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-docx" ~/.gemini/config/skills/
19
+ find .agents/skills _agents/skills ~/.gemini/config/skills ~/.gemini/skills -maxdepth 2 -name SKILL.md -exec grep -l -E '^name: *"?lit-docx"? *$' {} + 2>/dev/null
20
+ if [ -e ~/.gemini/config/skills/lit-docx ] || [ -L ~/.gemini/config/skills/lit-docx ]; then b=~/.gemini/extension-backups/$(date +%Y%m%d-%H%M%S); mkdir -p "$b" && mv ~/.gemini/config/skills/lit-docx "$b/" && echo "moved to $b/lit-docx"; fi
21
+ mkdir -p ~/.gemini/config/skills && [ ! -e ~/.gemini/config/skills/lit-docx ] && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-docx" ~/.gemini/config/skills/lit-docx
22
+ printf '{"id":"%s","source":"%s","variant":"litgravity","installed_at":"%s"}\n' lit-docx "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-docx" "$(date -u +%Y-%m-%dT%H:%M:%SZ)" > ~/.gemini/config/skills/lit-docx/.litfamily-extension.json
18
23
  ```
19
24
 
20
- For one workspace only, run this in its root instead: `mkdir -p .agents/skills && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-docx" .agents/skills/`.
25
+ Line one only looks: it prints every `SKILL.md` named lit-docx that agy could load, and nothing when there is none. agy keeps one same-name skill without a word, a workspace copy first, so move any other one it names aside too. Line two moves an existing copy whole into a dated folder under `~/.gemini/extension-backups/`, which agy never loads; line three copies into the emptied place; line four writes the receipt `.litfamily-extension.json` inside the copy.
26
+
27
+ For one workspace only, run line one, then these three in the workspace root:
28
+
29
+ ```bash
30
+ if [ -e .agents/skills/lit-docx ] || [ -L .agents/skills/lit-docx ]; then b=~/.gemini/extension-backups/$(date +%Y%m%d-%H%M%S)-project; mkdir -p "$b" && mv .agents/skills/lit-docx "$b/" && echo "moved to $b/lit-docx"; fi
31
+ mkdir -p .agents/skills && [ ! -e .agents/skills/lit-docx ] && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-docx" .agents/skills/lit-docx
32
+ printf '{"id":"%s","source":"%s","variant":"litgravity","installed_at":"%s"}\n' lit-docx "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-docx" "$(date -u +%Y-%m-%dT%H:%M:%SZ)" > .agents/skills/lit-docx/.litfamily-extension.json
33
+ ```
21
34
 
22
- The folder is the whole skill, with its own scripts, references and engine locks. Start a new conversation, or type `/skills reload`; the skill then answers as `/lit-docx`, and `lit` prompts that reach this stub hand over to it. To update it, delete the copied folder and copy it again. The LitGravity installer writes only its own plugin folder, so upgrading or removing LitGravity leaves the copy alone, and the names never clash: this stub is `litgravity:lit-docx`, the copy is `lit-docx`.
35
+ The folder is the whole skill, with its own scripts, references and engine locks. Start a new conversation, or type `/skills reload`; the skill then answers as `/lit-docx`, and `lit` prompts that reach this stub hand over to it. To update it, run the same lines again: the old copy moves to a new dated backup and the receipt is rewritten. To remove it, run the second line alone. Nothing is deleted; clear old backups out of `~/.gemini/extension-backups/` when you no longer need them. The LitGravity installer writes only its own plugin folder, so upgrading or removing LitGravity leaves the copy alone, and the names never clash: this stub is `litgravity:lit-docx`, the copy is `lit-docx`.
23
36
 
24
37
  ## When this stub is read
25
38
 
26
39
  1. Look for the installed copy with `read_file`: first `~/.gemini/config/skills/lit-docx/SKILL.md`, then `.agents/skills/lit-docx/SKILL.md` in the workspace.
27
40
  2. **Found.** Read it and follow it for this task; its folder is the root for every relative path it names. It was written for agy and needs no LitGravity hook: every check it names is a command it tells you to run.
28
- 3. **Not found, asked directly.** Reply in a few lines: what lit-docx did, that it is a LitFamily extension now, kept in wjgoarxiv-skills (`variants/litgravity/lit-docx/`), the install line above, and that you made nothing yet. Do not produce the .docx another way in its place (python-docx, pandoc, soffice).
29
- 4. **Not found, inside a workflow.** Inside a lit workflow (lit-loop, litwork, start-work, review-work) that reached this skill, write `lit-docx not installed` once in the ledger and the reply with the install line, finish the parts that need no document, and mark the part that needs it BLOCKED, not done.
41
+ 3. **Not found, asked directly.** Reply in a few lines: what lit-docx did, that it is a LitFamily extension now, kept in wjgoarxiv-skills (`variants/litgravity/lit-docx/`), the `extensions install` command and the install lines above, and that you made nothing yet. Do not produce the .docx another way in its place (python-docx, pandoc, soffice).
42
+ 4. **Not found, inside a workflow.** Inside a lit workflow (lit-loop, litwork, start-work, review-work) that reached this skill, write `lit-docx not installed` once in the ledger and the reply with the install lines, finish the parts that need no document, and mark the part that needs it BLOCKED, not done.
30
43
 
31
44
  ## Hard stops
32
45
 
33
- - Give the install line with the placeholder; never a path from this machine.
46
+ - Give the install lines with the placeholder; never a path from this machine.
34
47
  - Never say a document exists unless the installed copy made it and you looked at the result.
35
- - A headless run (`agy -p`) never copies the skill in itself: give the install line and stop.
48
+ - A headless run (`agy -p`) never copies the skill in itself: give the install lines and stop.
@@ -11,25 +11,38 @@ This file keeps the id. `lit deck …`, `lit slides …`, `lit pptx …`, a `lit
11
11
 
12
12
  ## Install it in agy
13
13
 
14
- wjgoarxiv-skills is public at https://github.com/wjgoarxiv/wjgoarxiv-skills. Clone it (`git clone https://github.com/wjgoarxiv/wjgoarxiv-skills`), then copy the skill folder into agy's user skills, which every workspace sees:
14
+ The short route is LitGravity's own command, run in a terminal: `npx @litfamily/litgravity extensions install lit-pptx` prints what it would do, and the same with `--yes` does it (`--project` for one workspace). It fetches the skill, stops if another skill named lit-pptx sits where agy loads skills, moves an old copy aside and writes the receipt; `extensions update`, `remove` and `check` do the rest. The lines below are the same steps by hand.
15
+
16
+ wjgoarxiv-skills is public at https://github.com/wjgoarxiv/wjgoarxiv-skills. Clone it (`git clone https://github.com/wjgoarxiv/wjgoarxiv-skills`), then paste these four lines one at a time (zsh or bash) in the workspace you use agy in. They put the skill in agy's user skills, which every workspace sees:
15
17
 
16
18
  ```bash
17
- mkdir -p ~/.gemini/config/skills && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-pptx" ~/.gemini/config/skills/
19
+ find .agents/skills _agents/skills ~/.gemini/config/skills ~/.gemini/skills -maxdepth 2 -name SKILL.md -exec grep -l -E '^name: *"?lit-pptx"? *$' {} + 2>/dev/null
20
+ if [ -e ~/.gemini/config/skills/lit-pptx ] || [ -L ~/.gemini/config/skills/lit-pptx ]; then b=~/.gemini/extension-backups/$(date +%Y%m%d-%H%M%S); mkdir -p "$b" && mv ~/.gemini/config/skills/lit-pptx "$b/" && echo "moved to $b/lit-pptx"; fi
21
+ mkdir -p ~/.gemini/config/skills && [ ! -e ~/.gemini/config/skills/lit-pptx ] && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-pptx" ~/.gemini/config/skills/lit-pptx
22
+ printf '{"id":"%s","source":"%s","variant":"litgravity","installed_at":"%s"}\n' lit-pptx "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-pptx" "$(date -u +%Y-%m-%dT%H:%M:%SZ)" > ~/.gemini/config/skills/lit-pptx/.litfamily-extension.json
18
23
  ```
19
24
 
20
- For one workspace only, run this in its root instead: `mkdir -p .agents/skills && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-pptx" .agents/skills/`.
25
+ Line one only looks: it prints every `SKILL.md` named lit-pptx that agy could load, and nothing when there is none. agy keeps one same-name skill without a word, a workspace copy first, so move any other one it names aside too. Line two moves an existing copy whole into a dated folder under `~/.gemini/extension-backups/`, which agy never loads; line three copies into the emptied place; line four writes the receipt `.litfamily-extension.json` inside the copy.
26
+
27
+ For one workspace only, run line one, then these three in the workspace root:
28
+
29
+ ```bash
30
+ if [ -e .agents/skills/lit-pptx ] || [ -L .agents/skills/lit-pptx ]; then b=~/.gemini/extension-backups/$(date +%Y%m%d-%H%M%S)-project; mkdir -p "$b" && mv .agents/skills/lit-pptx "$b/" && echo "moved to $b/lit-pptx"; fi
31
+ mkdir -p .agents/skills && [ ! -e .agents/skills/lit-pptx ] && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-pptx" .agents/skills/lit-pptx
32
+ printf '{"id":"%s","source":"%s","variant":"litgravity","installed_at":"%s"}\n' lit-pptx "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-pptx" "$(date -u +%Y-%m-%dT%H:%M:%SZ)" > .agents/skills/lit-pptx/.litfamily-extension.json
33
+ ```
21
34
 
22
- The folder is the whole skill, with its own scripts, references and engine locks. Start a new conversation, or type `/skills reload`; the skill then answers as `/lit-pptx`, and `lit` prompts that reach this stub hand over to it. To update it, delete the copied folder and copy it again. The LitGravity installer writes only its own plugin folder, so upgrading or removing LitGravity leaves the copy alone, and the names never clash: this stub is `litgravity:lit-pptx`, the copy is `lit-pptx`.
35
+ The folder is the whole skill, with its own scripts, references and engine locks. Start a new conversation, or type `/skills reload`; the skill then answers as `/lit-pptx`, and `lit` prompts that reach this stub hand over to it. To update it, run the same lines again: the old copy moves to a new dated backup and the receipt is rewritten. To remove it, run the second line alone. Nothing is deleted; clear old backups out of `~/.gemini/extension-backups/` when you no longer need them. The LitGravity installer writes only its own plugin folder, so upgrading or removing LitGravity leaves the copy alone, and the names never clash: this stub is `litgravity:lit-pptx`, the copy is `lit-pptx`.
23
36
 
24
37
  ## When this stub is read
25
38
 
26
39
  1. Look for the installed copy with `read_file`: first `~/.gemini/config/skills/lit-pptx/SKILL.md`, then `.agents/skills/lit-pptx/SKILL.md` in the workspace.
27
40
  2. **Found.** Read it and follow it for this task; its folder is the root for every relative path it names. It was written for agy and needs no LitGravity hook: every check it names is a command it tells you to run.
28
- 3. **Not found, asked directly.** Reply in a few lines: what lit-pptx did, that it is a LitFamily extension now, kept in wjgoarxiv-skills (`variants/litgravity/lit-pptx/`), the install line above, and that you made nothing yet. Do not write the deck another way in its place (python-pptx, soffice, an HTML page called slides).
29
- 4. **Not found, inside a workflow.** Inside a lit workflow (lit-loop, litwork, start-work, review-work) that reached this skill, write `lit-pptx not installed` once in the ledger and the reply with the install line, finish the parts that need no deck, and mark the part that needs it BLOCKED, not done.
41
+ 3. **Not found, asked directly.** Reply in a few lines: what lit-pptx did, that it is a LitFamily extension now, kept in wjgoarxiv-skills (`variants/litgravity/lit-pptx/`), the `extensions install` command and the install lines above, and that you made nothing yet. Do not write the deck another way in its place (python-pptx, soffice, an HTML page called slides).
42
+ 4. **Not found, inside a workflow.** Inside a lit workflow (lit-loop, litwork, start-work, review-work) that reached this skill, write `lit-pptx not installed` once in the ledger and the reply with the install lines, finish the parts that need no deck, and mark the part that needs it BLOCKED, not done.
30
43
 
31
44
  ## Hard stops
32
45
 
33
- - Give the install line with the placeholder; never a path from this machine.
46
+ - Give the install lines with the placeholder; never a path from this machine.
34
47
  - Never say a deck exists unless the installed copy made it and you looked at the result.
35
- - A headless run (`agy -p`) never copies the skill in itself: give the install line and stop.
48
+ - A headless run (`agy -p`) never copies the skill in itself: give the install lines and stop.
@@ -11,25 +11,38 @@ This file keeps the id. `lit schematic …`, `lit pid …`, `lit pfd …`, `lit
11
11
 
12
12
  ## Install it in agy
13
13
 
14
- wjgoarxiv-skills is public at https://github.com/wjgoarxiv/wjgoarxiv-skills. Clone it (`git clone https://github.com/wjgoarxiv/wjgoarxiv-skills`), then copy the skill folder into agy's user skills, which every workspace sees:
14
+ The short route is LitGravity's own command, run in a terminal: `npx @litfamily/litgravity extensions install lit-schematic` prints what it would do, and the same with `--yes` does it (`--project` for one workspace). It fetches the skill, stops if another skill named lit-schematic sits where agy loads skills, moves an old copy aside and writes the receipt; `extensions update`, `remove` and `check` do the rest. The lines below are the same steps by hand.
15
+
16
+ wjgoarxiv-skills is public at https://github.com/wjgoarxiv/wjgoarxiv-skills. Clone it (`git clone https://github.com/wjgoarxiv/wjgoarxiv-skills`), then paste these four lines one at a time (zsh or bash) in the workspace you use agy in. They put the skill in agy's user skills, which every workspace sees:
15
17
 
16
18
  ```bash
17
- mkdir -p ~/.gemini/config/skills && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-schematic" ~/.gemini/config/skills/
19
+ find .agents/skills _agents/skills ~/.gemini/config/skills ~/.gemini/skills -maxdepth 2 -name SKILL.md -exec grep -l -E '^name: *"?lit-schematic"? *$' {} + 2>/dev/null
20
+ if [ -e ~/.gemini/config/skills/lit-schematic ] || [ -L ~/.gemini/config/skills/lit-schematic ]; then b=~/.gemini/extension-backups/$(date +%Y%m%d-%H%M%S); mkdir -p "$b" && mv ~/.gemini/config/skills/lit-schematic "$b/" && echo "moved to $b/lit-schematic"; fi
21
+ mkdir -p ~/.gemini/config/skills && [ ! -e ~/.gemini/config/skills/lit-schematic ] && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-schematic" ~/.gemini/config/skills/lit-schematic
22
+ printf '{"id":"%s","source":"%s","variant":"litgravity","installed_at":"%s"}\n' lit-schematic "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-schematic" "$(date -u +%Y-%m-%dT%H:%M:%SZ)" > ~/.gemini/config/skills/lit-schematic/.litfamily-extension.json
18
23
  ```
19
24
 
20
- For one workspace only, run this in its root instead: `mkdir -p .agents/skills && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-schematic" .agents/skills/`.
25
+ Line one only looks: it prints every `SKILL.md` named lit-schematic that agy could load, and nothing when there is none. agy keeps one same-name skill without a word, a workspace copy first, so move any other one it names aside too. Line two moves an existing copy whole into a dated folder under `~/.gemini/extension-backups/`, which agy never loads; line three copies into the emptied place; line four writes the receipt `.litfamily-extension.json` inside the copy.
26
+
27
+ For one workspace only, run line one, then these three in the workspace root:
28
+
29
+ ```bash
30
+ if [ -e .agents/skills/lit-schematic ] || [ -L .agents/skills/lit-schematic ]; then b=~/.gemini/extension-backups/$(date +%Y%m%d-%H%M%S)-project; mkdir -p "$b" && mv .agents/skills/lit-schematic "$b/" && echo "moved to $b/lit-schematic"; fi
31
+ mkdir -p .agents/skills && [ ! -e .agents/skills/lit-schematic ] && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-schematic" .agents/skills/lit-schematic
32
+ printf '{"id":"%s","source":"%s","variant":"litgravity","installed_at":"%s"}\n' lit-schematic "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-schematic" "$(date -u +%Y-%m-%dT%H:%M:%SZ)" > .agents/skills/lit-schematic/.litfamily-extension.json
33
+ ```
21
34
 
22
- The folder is the whole skill, with its own scripts, references and engine locks. Its neighbours (lit-diagram-drawer and lit-scientific-visualization) install the same way, one folder each. Start a new conversation, or type `/skills reload`; the skill then answers as `/lit-schematic`, and `lit` prompts that reach this stub hand over to it. To update it, delete the copied folder and copy it again. The LitGravity installer writes only its own plugin folder, so upgrading or removing LitGravity leaves the copy alone, and the names never clash: this stub is `litgravity:lit-schematic`, the copy is `lit-schematic`.
35
+ The folder is the whole skill, with its own scripts, references and engine locks. Its neighbours (lit-diagram-drawer and lit-scientific-visualization) install the same way, one folder each. Start a new conversation, or type `/skills reload`; the skill then answers as `/lit-schematic`, and `lit` prompts that reach this stub hand over to it. To update it, run the same lines again: the old copy moves to a new dated backup and the receipt is rewritten. To remove it, run the second line alone. Nothing is deleted; clear old backups out of `~/.gemini/extension-backups/` when you no longer need them. The LitGravity installer writes only its own plugin folder, so upgrading or removing LitGravity leaves the copy alone, and the names never clash: this stub is `litgravity:lit-schematic`, the copy is `lit-schematic`.
23
36
 
24
37
  ## When this stub is read
25
38
 
26
39
  1. Look for the installed copy with `read_file`: first `~/.gemini/config/skills/lit-schematic/SKILL.md`, then `.agents/skills/lit-schematic/SKILL.md` in the workspace.
27
40
  2. **Found.** Read it and follow it for this task; its folder is the root for every relative path it names. It was written for agy and needs no LitGravity hook: every check it names is a command it tells you to run.
28
- 3. **Not found, asked directly.** Reply in a few lines: what lit-schematic did, that it is a LitFamily extension now, kept in wjgoarxiv-skills (`variants/litgravity/lit-schematic/`), the install line above, and that you made nothing yet. Do not draw the schematic another way in its place (a hand-written SVG, a box-and-arrow diagram).
29
- 4. **Not found, inside a workflow.** Inside a lit workflow (lit-loop, litwork, start-work, review-work) that reached this skill, write `lit-schematic not installed` once in the ledger and the reply with the install line, finish the parts that need no schematic, and mark the part that needs it BLOCKED, not done.
41
+ 3. **Not found, asked directly.** Reply in a few lines: what lit-schematic did, that it is a LitFamily extension now, kept in wjgoarxiv-skills (`variants/litgravity/lit-schematic/`), the `extensions install` command and the install lines above, and that you made nothing yet. Do not draw the schematic another way in its place (a hand-written SVG, a box-and-arrow diagram).
42
+ 4. **Not found, inside a workflow.** Inside a lit workflow (lit-loop, litwork, start-work, review-work) that reached this skill, write `lit-schematic not installed` once in the ledger and the reply with the install lines, finish the parts that need no schematic, and mark the part that needs it BLOCKED, not done.
30
43
 
31
44
  ## Hard stops
32
45
 
33
- - Give the install line with the placeholder; never a path from this machine.
46
+ - Give the install lines with the placeholder; never a path from this machine.
34
47
  - Never say a schematic exists unless the installed copy made it and you looked at the result.
35
- - A headless run (`agy -p`) never copies the skill in itself: give the install line and stop.
48
+ - A headless run (`agy -p`) never copies the skill in itself: give the install lines and stop.
@@ -11,25 +11,38 @@ This file keeps the id. `lit figure …`, `lit plot …`, and `/litgravity:lit-s
11
11
 
12
12
  ## Install it in agy
13
13
 
14
- wjgoarxiv-skills is public at https://github.com/wjgoarxiv/wjgoarxiv-skills. Clone it (`git clone https://github.com/wjgoarxiv/wjgoarxiv-skills`), then copy the skill folder into agy's user skills, which every workspace sees:
14
+ The short route is LitGravity's own command, run in a terminal: `npx @litfamily/litgravity extensions install lit-scientific-visualization` prints what it would do, and the same with `--yes` does it (`--project` for one workspace). It fetches the skill, stops if another skill named lit-scientific-visualization sits where agy loads skills, moves an old copy aside and writes the receipt; `extensions update`, `remove` and `check` do the rest. The lines below are the same steps by hand.
15
+
16
+ wjgoarxiv-skills is public at https://github.com/wjgoarxiv/wjgoarxiv-skills. Clone it (`git clone https://github.com/wjgoarxiv/wjgoarxiv-skills`), then paste these four lines one at a time (zsh or bash) in the workspace you use agy in. They put the skill in agy's user skills, which every workspace sees:
15
17
 
16
18
  ```bash
17
- mkdir -p ~/.gemini/config/skills && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-scientific-visualization" ~/.gemini/config/skills/
19
+ find .agents/skills _agents/skills ~/.gemini/config/skills ~/.gemini/skills -maxdepth 2 -name SKILL.md -exec grep -l -E '^name: *"?lit-scientific-visualization"? *$' {} + 2>/dev/null
20
+ if [ -e ~/.gemini/config/skills/lit-scientific-visualization ] || [ -L ~/.gemini/config/skills/lit-scientific-visualization ]; then b=~/.gemini/extension-backups/$(date +%Y%m%d-%H%M%S); mkdir -p "$b" && mv ~/.gemini/config/skills/lit-scientific-visualization "$b/" && echo "moved to $b/lit-scientific-visualization"; fi
21
+ mkdir -p ~/.gemini/config/skills && [ ! -e ~/.gemini/config/skills/lit-scientific-visualization ] && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-scientific-visualization" ~/.gemini/config/skills/lit-scientific-visualization
22
+ printf '{"id":"%s","source":"%s","variant":"litgravity","installed_at":"%s"}\n' lit-scientific-visualization "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-scientific-visualization" "$(date -u +%Y-%m-%dT%H:%M:%SZ)" > ~/.gemini/config/skills/lit-scientific-visualization/.litfamily-extension.json
18
23
  ```
19
24
 
20
- For one workspace only, run this in its root instead: `mkdir -p .agents/skills && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-scientific-visualization" .agents/skills/`.
25
+ Line one only looks: it prints every `SKILL.md` named lit-scientific-visualization that agy could load, and nothing when there is none. agy keeps one same-name skill without a word, a workspace copy first, so move any other one it names aside too. Line two moves an existing copy whole into a dated folder under `~/.gemini/extension-backups/`, which agy never loads; line three copies into the emptied place; line four writes the receipt `.litfamily-extension.json` inside the copy.
26
+
27
+ For one workspace only, run line one, then these three in the workspace root:
28
+
29
+ ```bash
30
+ if [ -e .agents/skills/lit-scientific-visualization ] || [ -L .agents/skills/lit-scientific-visualization ]; then b=~/.gemini/extension-backups/$(date +%Y%m%d-%H%M%S)-project; mkdir -p "$b" && mv .agents/skills/lit-scientific-visualization "$b/" && echo "moved to $b/lit-scientific-visualization"; fi
31
+ mkdir -p .agents/skills && [ ! -e .agents/skills/lit-scientific-visualization ] && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-scientific-visualization" .agents/skills/lit-scientific-visualization
32
+ printf '{"id":"%s","source":"%s","variant":"litgravity","installed_at":"%s"}\n' lit-scientific-visualization "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-scientific-visualization" "$(date -u +%Y-%m-%dT%H:%M:%SZ)" > .agents/skills/lit-scientific-visualization/.litfamily-extension.json
33
+ ```
21
34
 
22
- The folder is the whole skill, with its own scripts, references and engine locks. Its neighbours (lit-diagram-drawer and lit-schematic) install the same way, one folder each. Start a new conversation, or type `/skills reload`; the skill then answers as `/lit-scientific-visualization`, and `lit` prompts that reach this stub hand over to it. To update it, delete the copied folder and copy it again. The LitGravity installer writes only its own plugin folder, so upgrading or removing LitGravity leaves the copy alone, and the names never clash: this stub is `litgravity:lit-scientific-visualization`, the copy is `lit-scientific-visualization`.
35
+ The folder is the whole skill, with its own scripts, references and engine locks. Its neighbours (lit-diagram-drawer and lit-schematic) install the same way, one folder each. Start a new conversation, or type `/skills reload`; the skill then answers as `/lit-scientific-visualization`, and `lit` prompts that reach this stub hand over to it. To update it, run the same lines again: the old copy moves to a new dated backup and the receipt is rewritten. To remove it, run the second line alone. Nothing is deleted; clear old backups out of `~/.gemini/extension-backups/` when you no longer need them. The LitGravity installer writes only its own plugin folder, so upgrading or removing LitGravity leaves the copy alone, and the names never clash: this stub is `litgravity:lit-scientific-visualization`, the copy is `lit-scientific-visualization`.
23
36
 
24
37
  ## When this stub is read
25
38
 
26
39
  1. Look for the installed copy with `read_file`: first `~/.gemini/config/skills/lit-scientific-visualization/SKILL.md`, then `.agents/skills/lit-scientific-visualization/SKILL.md` in the workspace.
27
40
  2. **Found.** Read it and follow it for this task; its folder is the root for every relative path it names. It was written for agy and needs no LitGravity hook: every check it names is a command it tells you to run.
28
- 3. **Not found, asked directly.** Reply in a few lines: what lit-scientific-visualization did, that it is a LitFamily extension now, kept in wjgoarxiv-skills (`variants/litgravity/lit-scientific-visualization/`), the install line above, and that you made nothing yet. Do not plot the figure another way in its place (an ad-hoc matplotlib script with no style or check).
29
- 4. **Not found, inside a workflow.** Inside a lit workflow (lit-loop, litwork, start-work, review-work) that reached this skill, write `lit-scientific-visualization not installed` once in the ledger and the reply with the install line, finish the parts that need no figure, and mark the part that needs it BLOCKED, not done.
41
+ 3. **Not found, asked directly.** Reply in a few lines: what lit-scientific-visualization did, that it is a LitFamily extension now, kept in wjgoarxiv-skills (`variants/litgravity/lit-scientific-visualization/`), the `extensions install` command and the install lines above, and that you made nothing yet. Do not plot the figure another way in its place (an ad-hoc matplotlib script with no style or check).
42
+ 4. **Not found, inside a workflow.** Inside a lit workflow (lit-loop, litwork, start-work, review-work) that reached this skill, write `lit-scientific-visualization not installed` once in the ledger and the reply with the install lines, finish the parts that need no figure, and mark the part that needs it BLOCKED, not done.
30
43
 
31
44
  ## Hard stops
32
45
 
33
- - Give the install line with the placeholder; never a path from this machine.
46
+ - Give the install lines with the placeholder; never a path from this machine.
34
47
  - Never say a figure exists unless the installed copy made it and you looked at the result.
35
- - A headless run (`agy -p`) never copies the skill in itself: give the install line and stop.
48
+ - A headless run (`agy -p`) never copies the skill in itself: give the install lines and stop.