ghosty-acp 0.0.14 → 0.0.16
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/package.json +1 -1
- package/skills/README.md +1 -0
- package/skills/ghosty-agent/SKILL.md +12 -6
- package/skills/ghosty-factory/SKILL.md +101 -0
package/package.json
CHANGED
package/skills/README.md
CHANGED
|
@@ -15,6 +15,7 @@ npx skills add https://ghosty.studio
|
|
|
15
15
|
| `ghosty-docs` | read the Ghosty docs from an agent: markdown pages, `llms.txt`, the docs MCP server |
|
|
16
16
|
| `ghosty-acp` | connect Zed, VS Code, JetBrains or Neovim to the agent over ACP |
|
|
17
17
|
| `ghosty-recipe` | write or review an agent recipe (`.recipe.yaml`) to upload in the creator |
|
|
18
|
+
| `ghosty-factory` | prepare a repo for the Ghosty Software Factory: `AGENTS.md`, the `docs/agents/` knowledge base, `.ghosty/factory.md` (agent and model per role) |
|
|
18
19
|
|
|
19
20
|
This directory is mirrored from `public/skills/` in
|
|
20
21
|
[blissito/ghosty-studio](https://github.com/blissito/ghosty-studio). Docs: https://www.ghosty.studio/docs/configurar
|
|
@@ -5,7 +5,7 @@ license: MIT
|
|
|
5
5
|
compatibility: Needs Node 22+ (for npx @ghostystudio/cli) or curl, and network access to https://www.ghosty.studio
|
|
6
6
|
metadata:
|
|
7
7
|
author: ghosty-studio
|
|
8
|
-
version: "1.
|
|
8
|
+
version: "1.18"
|
|
9
9
|
---
|
|
10
10
|
|
|
11
11
|
# Configure a Ghosty Studio agent
|
|
@@ -77,9 +77,14 @@ legacy and always `true`.)
|
|
|
77
77
|
|
|
78
78
|
| User asks | Do |
|
|
79
79
|
|---|---|
|
|
80
|
-
| "create a new agent" | `ghosty agents create --name <name> [--engine <engine>] [--model <model-id>] [--prompt-file PROMPT.md] [--env K=V,…] --json` → `id`. A model outside the engine answers 400 with the valid list |
|
|
80
|
+
| "create a new agent" | `ghosty agents create --name <name> [--engine <engine>] [--model <model-id>] [--prompt-file PROMPT.md] [--env K=V,…] [--workspace <slug>] [--channels teams=off] --json` → `id`. A model outside the engine answers 400 with the valid list. `--workspace` = born in that workspace, owned by its owner, active in its Teams |
|
|
81
81
|
| "set its identity / persona / system prompt" | write it with `references/identity.md` to a file, `ghosty agents set <id> --prompt-file PROMPT.md`, then `ghosty agents restart <id>` only if `needsRestart` |
|
|
82
82
|
| "let it see my Drive / use my connector" | `ghosty agents set <id> --connect google-drive` (owner only; the account must have it connected first). Files are the ones the owner picked in Conectores → Google Drive |
|
|
83
|
+
| "edit its (long) prompt" | `ghosty agents get <id> --prompt-out PROMPT.md`, edit the file, `ghosty agents set <id> --prompt-file PROMPT.md` |
|
|
84
|
+
| "base its prompt on another agent's (a branch, a variant)" | write an overlay `{"edits":[{"what","find","replace","regex"?,"all"?}]}`, `ghosty agents set <id> --prompt-base <base-id> --prompt-overlay overlay.json --dry-run --out /tmp/p.md`, check, then without `--dry-run`. It regenerates when the base changes; its own prompt can't be edited while linked (`--prompt-base none` unlinks) |
|
|
85
|
+
| "give it the CRM / sales tools" | `ghosty agents set <id> --toolsets +crm` (a plain list replaces; `-x` removes) |
|
|
86
|
+
| "share it with / give access to <email>" | `ghosty agents share <id> <email> [--role editor\|admin]` (keeps ownership); `ghosty agents shares <id>` lists; `unshare` needs `--yes` |
|
|
87
|
+
| "turn off / on this skill" | `ghosty skills off\|on <id> <slug>` (its own or one of Ghosty's; `skills ls` shows `on`) |
|
|
83
88
|
| "delete this agent" | confirm with the user first, then `ghosty agents rm <id>` (owner only; `409` names the workspace where it is active) |
|
|
84
89
|
| "switch it to another engine" | `ghosty agents set <id> --engine <engine> [--model <model-id>]` (the model belongs to the NEW engine) |
|
|
85
90
|
| "change the model" | `ghosty agents get <id> --json` (lists `models`), then `ghosty agents set <id> --model <model-id>` (restarts by itself) |
|
|
@@ -94,15 +99,16 @@ legacy and always `true`.)
|
|
|
94
99
|
| "replay these real conversations" | `ghosty try <id> --replay sample.json --out ./replay [--max N]`; read `./replay/replay.json`; `--resume` if it was cut |
|
|
95
100
|
| "is it configured right? / why does it answer badly?" | `ghosty agents doctor <id> --json` → `checks[]` with `level` (ok/warn/error) and a `fix` command each; exit 1 = something to fix |
|
|
96
101
|
| "why did it fail? / it didn't answer" | `ghosty turns ls <id> --errors --since 24h --json` → failed turns with their `error` |
|
|
97
|
-
| "
|
|
102
|
+
| "what did it answer to that? / audit a reply" | `ghosty turns show <id> [turn-id] --json` → `input` (what came in) and `output` (what it answered), any engine or channel |
|
|
103
|
+
| "why was it slow? / where did the time go?" | `ghosty turns show <id> [turn-id] --json` → `byTool` (seconds per tool), `steps` (timeline), `totals.outputTokens`; pool engines only (`timeline: false` otherwise) |
|
|
98
104
|
| "is it running the new image? / it still behaves old" | `ghosty agents box <id> --check <path-the-new-image-brings> --json` → `stale`; if > 0, `ghosty agents box <id> --recycle`, one turn, check again (ACP: `agents restart`) |
|
|
99
105
|
| "which PDF templates does it have?" | `ghosty skills templates <id> --json` → `templates[]` with `source` (`agente:<skill>` or `casa`); its own go in `<skill>/pdf-templates/<name>.html` |
|
|
100
106
|
| "give it this database / what can it write" | `ghosty dbs ls <id>`, `ghosty dbs tables <id> <db>`, `ghosty dbs grant <id> <db> [--external-write t1,t2] [--external-rows t:col+col]` (tables it may write from WhatsApp/Messenger; tables where each customer sees only their own rows, matched by phone column — use it for any customers/orders table) |
|
|
101
107
|
| "copy its data from EasyBits" | `ghosty dbs import <id> <db> --from easybits:<db-id> --dry-run` first (needs `EASYBITS_API_KEY`), show the plan, then run without `--dry-run` (`--yes` if replacing rows) |
|
|
102
|
-
| "let it read / send this document" | `ghosty agents docs ls <id>`, `ghosty agents docs grant <id> "<name>" [--write] [--no-deliver]` |
|
|
108
|
+
| "let it read / send this document" | `ghosty agents docs ls <id>`, `ghosty agents docs grant <id> "<name>" [--write] [--no-deliver]`; a new one: `ghosty agents docs add <id> --url <url> \| --file <path> [--description T]` (uploads and grants) |
|
|
103
109
|
| "answer with voice notes" | `ghosty agents set <id> --voice elevenlabs:<voice-id>\|kokoro:em_santa --voice-replies auto` |
|
|
104
110
|
| "answer in this WhatsApp group / make the group team or customer" | personal WhatsApp only: `ghosty channels wa groups ls <id> --json`, then confirm with the user and `ghosty channels wa groups set <id> "<group>" --role equipo\|cliente --on --yes` (`--dry-run` first) |
|
|
105
|
-
| "move / migrate this WhatsApp number from EasyBits or Formmy" | Business: `ghosty channels whatsapp link <id> --integration <formmy-id> --answer on\|off --dry-run --json` → show `plan`; confirm with the user (on = answers real customers), then without `--dry-run` and `--yes`; back: `unlink`. Personal: `ghosty channels wa import <id> --from-file F` (EasyBits JSON) or `--from-dir DIR` (Baileys multi-file folder) `--own-number yes\|no --dry-run` (the user turns off EasyBits WITHOUT logout first), then `wa status` |
|
|
111
|
+
| "move / migrate this WhatsApp number from EasyBits or Formmy" | Business: `ghosty channels whatsapp link <id> --integration <formmy-id> --answer on\|off --dry-run --json` → show `plan`; confirm with the user (on = answers real customers), then without `--dry-run` and `--yes`; back: `unlink`. Its recent cards/messages/orders: `ghosty channels whatsapp history <id> --integration <formmy-id> --days 7 --dry-run`, then without `--dry-run` (`--yes`; re-running never duplicates). Personal: `ghosty channels wa import <id> --from-file F` (EasyBits JSON) or `--from-dir DIR` (Baileys multi-file folder) `--own-number yes\|no --dry-run` (the user turns off EasyBits WITHOUT logout first), then `wa status` |
|
|
106
112
|
| "answer this WhatsApp number" | confirm with the user (real customers), then `ghosty channels whatsapp enable <id> <number> --yes`; `--dry-run` shows the plan |
|
|
107
113
|
| "save my ElevenLabs / MercadoPago key" | never put the key in a command: ask the user to run `ghosty credentials set <provider>` themselves (hidden prompt), or use `--from-env VAR` |
|
|
108
114
|
| "remove this skill" | `ghosty skills rm <id> <slug> --yes` keeps a local copy and returns `restore`; `ghosty skills get <id> <slug> --out DIR` to back one up first (without `--out` it only lists) |
|
|
@@ -134,7 +140,7 @@ Read `references/api.md` for exact request/response shapes before calling.
|
|
|
134
140
|
- **Restart is not free**: it cuts a turn in progress. Batch changes, restart once at the end.
|
|
135
141
|
- Files go to the agent's working directory; tell the user the agent can `ls` them. Max 10 MB each.
|
|
136
142
|
- Never print the token back to the user or into logs.
|
|
137
|
-
- **Destructive commands need `--yes`** when you run them (no terminal): `agents rm`, `files rm`, `skills rm`, `credentials rm`, `board archive`, `dbs import` over existing rows, `channels whatsapp enable`, `channels wa groups set --on`, `channels whatsapp link|unlink`, `channels wa import`. Confirm with the user BEFORE adding it; prefer `--dry-run` first where it exists.
|
|
143
|
+
- **Destructive commands need `--yes`** when you run them (no terminal): `agents rm`, `files rm`, `skills rm`, `credentials rm`, `board archive`, `dbs import` over existing rows, `channels whatsapp enable`, `channels wa groups set --on`, `channels whatsapp link|unlink|history`, `channels wa import`, `agents unshare`. Confirm with the user BEFORE adding it; prefer `--dry-run` first where it exists.
|
|
138
144
|
|
|
139
145
|
## Verify
|
|
140
146
|
|
|
@@ -0,0 +1,101 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: ghosty-factory
|
|
3
|
+
description: Prepare and maintain a GitHub repo for the Ghosty Software Factory (@plan, @build, @check agents working from Ghosty Teams) — AGENTS.md, the docs/agents/ knowledge base, .ghosty/factory.md (which agent and model plays each role) and small, reviewable PRs. Use when the user mentions Ghosty Factory, Software Factory, @plan/@build/@check, .ghosty/factory.md, docs/agents or wants their repo "ready for agents".
|
|
4
|
+
license: MIT
|
|
5
|
+
compatibility: Any git repository hosted on GitHub. Network access to https://www.ghosty.studio for the docs.
|
|
6
|
+
metadata:
|
|
7
|
+
author: ghosty-studio
|
|
8
|
+
version: "1.0"
|
|
9
|
+
---
|
|
10
|
+
|
|
11
|
+
# Get a repo ready for the Ghosty Software Factory
|
|
12
|
+
|
|
13
|
+
The Software Factory is three agents working a GitHub repo from a Ghosty Teams room: `@plan`
|
|
14
|
+
writes a plan a person signs, `@build` builds it in a draft PR, `@check` reviews it with another
|
|
15
|
+
model. A person signs the plan and the PR. The goal is **PRs a person reviews in two minutes**,
|
|
16
|
+
so everything here serves that. Docs: https://www.ghosty.studio/docs/fabrica.md (English:
|
|
17
|
+
`/en/docs/factory.md`).
|
|
18
|
+
|
|
19
|
+
Everything below lives **in the repo**. Work on a branch and open a PR; never push to the default
|
|
20
|
+
branch.
|
|
21
|
+
|
|
22
|
+
## 1. `AGENTS.md` (the index)
|
|
23
|
+
|
|
24
|
+
Create or complete it at the repo root. Only commands that really exist in `package.json` (or
|
|
25
|
+
the project's equivalent):
|
|
26
|
+
|
|
27
|
+
```markdown
|
|
28
|
+
# AGENTS.md
|
|
29
|
+
|
|
30
|
+
## Comandos
|
|
31
|
+
- `npm ci` — instalar
|
|
32
|
+
- `npm run typecheck` — tipos
|
|
33
|
+
- `npm test` — pruebas
|
|
34
|
+
|
|
35
|
+
## Arquitectura
|
|
36
|
+
3–6 lines: main folders and what lives in each.
|
|
37
|
+
|
|
38
|
+
## Convenciones
|
|
39
|
+
- Small changes with tests; one PR per request.
|
|
40
|
+
|
|
41
|
+
## Qué no tocar
|
|
42
|
+
- `.github/` (CI and repo rules): a person reviews changes there.
|
|
43
|
+
- Secrets and `.env*` files.
|
|
44
|
+
|
|
45
|
+
## Conocimiento
|
|
46
|
+
Short notes in `docs/agents/`: decisions, pitfalls and glossary the code doesn't say by itself.
|
|
47
|
+
|
|
48
|
+
- [Topic](docs/agents/topic.md) — what it covers, in one line
|
|
49
|
+
```
|
|
50
|
+
|
|
51
|
+
If the repo already has `CLAUDE.md`, say so at the top of `AGENTS.md` and don't duplicate it.
|
|
52
|
+
|
|
53
|
+
## 2. The knowledge base: `docs/agents/`
|
|
54
|
+
|
|
55
|
+
One short note per topic. Each answers **what**, **why it was decided that way** and **how to
|
|
56
|
+
apply it**. Write only what the code doesn't say by itself: decisions, pitfalls that cost time,
|
|
57
|
+
vocabulary. Add one line per note to the "Conocimiento" section of `AGENTS.md`.
|
|
58
|
+
|
|
59
|
+
The factory reads it every turn: `@plan` cites the notes it used, `@build` writes or updates a
|
|
60
|
+
note **in the same PR** when a change settles a convention or finds a pitfall, and `@check`
|
|
61
|
+
flags a PR that contradicts a note. When you (a coding agent outside the factory) change a
|
|
62
|
+
convention in this repo, do the same: update the note in your PR.
|
|
63
|
+
|
|
64
|
+
## 3. `.ghosty/factory.md` (optional): who plays each role here
|
|
65
|
+
|
|
66
|
+
Overrides the workspace team for this repo. Frontmatter per role; the body is conventions that
|
|
67
|
+
travel with every factory turn and override the generic rules:
|
|
68
|
+
|
|
69
|
+
```markdown
|
|
70
|
+
---
|
|
71
|
+
plan: { agent: Planner }
|
|
72
|
+
build: { agent: Builder, model: opus }
|
|
73
|
+
check: { agent: Reviewer, model: flash }
|
|
74
|
+
---
|
|
75
|
+
Conventions of this repo that @plan, @build and @check must know:
|
|
76
|
+
- Tests run with `pnpm test` (Vitest).
|
|
77
|
+
- Never touch already-applied migrations in `prisma/migrations/`.
|
|
78
|
+
```
|
|
79
|
+
|
|
80
|
+
- `agent`: name or id of a Studio agent in the workspace. Ask the user; don't invent names.
|
|
81
|
+
- `model`: alias (`opus`, `sonnet`, `fable` for Claude; `pro`, `flash` for DeepSeek; `sol`,
|
|
82
|
+
`terra`, `luna` for Codex) or a full id. It must match that agent's engine.
|
|
83
|
+
- Roles you leave out use the workspace default.
|
|
84
|
+
|
|
85
|
+
## 4. What makes factory PRs pass on the first review
|
|
86
|
+
|
|
87
|
+
- **Tests that run by themselves** in CI on every PR (typecheck, lint, tests). The factory's
|
|
88
|
+
"Prepare repo" can add a CI workflow; if one exists, keep it green.
|
|
89
|
+
- **A way to run the app** (`start`, `preview` or `dev` script) so each PR gets a preview and
|
|
90
|
+
the verdict card gets screenshots.
|
|
91
|
+
- **Small PRs.** The platform marks a PR high-risk when it passes ~400 lines or touches auth,
|
|
92
|
+
migrations, dependencies, public API or `.github/`. Split big work.
|
|
93
|
+
- **`CODEOWNERS`** covering `.github/`, so a person reviews CI changes.
|
|
94
|
+
|
|
95
|
+
## Verify
|
|
96
|
+
|
|
97
|
+
- Every command in `AGENTS.md` runs.
|
|
98
|
+
- Every note in `docs/agents/` is linked from `AGENTS.md` and every link resolves.
|
|
99
|
+
- `.ghosty/factory.md` frontmatter only uses `plan`, `build` and `check`, with `agent`/`model`.
|
|
100
|
+
- Tell the user they can check the result in Ghosty Teams → `/factory` → the repo →
|
|
101
|
+
"Ready for agents" and "Team in this repo" (↻ refreshes it).
|