@vatio-ai/skills 1.9.0 → 1.12.0
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.
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
{
|
|
6
6
|
"name": "vatio",
|
|
7
7
|
"source": "./",
|
|
8
|
-
"description": "
|
|
8
|
+
"description": "The Vatio plugin for Claude Code: build a conversational agent for your app with one prompt, then improve it daily with vatio-improve."
|
|
9
9
|
}
|
|
10
10
|
]
|
|
11
11
|
}
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "vatio",
|
|
3
|
-
"description": "
|
|
4
|
-
"version": "1.
|
|
3
|
+
"description": "The Vatio plugin for Claude Code: build a conversational agent for your app with one prompt, then improve it daily with vatio-improve.",
|
|
4
|
+
"version": "1.12.0",
|
|
5
5
|
"author": { "name": "Vatio", "url": "https://vatio.ai" },
|
|
6
6
|
"homepage": "https://vatio.ai/docs",
|
|
7
7
|
"repository": "https://github.com/vatio-ai/skills",
|
package/README.md
CHANGED
|
@@ -1,43 +1,39 @@
|
|
|
1
|
-
# Vatio
|
|
1
|
+
# Vatio: the Claude Code plugin for your app’s agent
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
Already have an app and users? Describe the conversational agent you want in
|
|
4
|
+
Claude Code. `vatio-init` builds it from your project; [Vatio](https://vatio.ai)
|
|
5
|
+
runs it with an inbox, human handoff and evaluation checks. You try the preview
|
|
6
|
+
and approve publication.
|
|
7
|
+
|
|
8
|
+
After launch, report mistakes in the inbox and make `/vatio:vatio-improve` your
|
|
9
|
+
daily routine. Claude prepares fixes, Vatio tests the reported cases, and you
|
|
10
|
+
approve the update. You do not need to write code yourself; you need access to
|
|
11
|
+
your app’s project in Claude Code.
|
|
4
12
|
|
|
5
13
|
| Skill | What it does |
|
|
6
14
|
|---|---|
|
|
7
15
|
| `vatio-init` | The first one in a project: looks at what is already there (a `vatio.yml` anywhere in the repository, the app's code) and recommends from it. With no agent yet, builds one: asks the owner what the code does not answer, writes `vatio.yml`, pushes it and hands over a link to try. With one, gets a developer who joined the project up to speed |
|
|
8
|
-
| `vatio-improve` | Takes every reply your supervisors reported in the inbox in one session: reads `vatio flags`, fixes each cause, `vatio push`, proves it with `vatio eval` (in the background in Claude Code) and publishes with `vatio publish` |
|
|
16
|
+
| `vatio-improve` | Takes every reply your supervisors reported in the inbox in one session: reads `vatio flags`, fixes each cause, `vatio push`, proves it with `vatio eval` (in the background in Claude Code) and publishes with `vatio publish` after your approval |
|
|
9
17
|
| `vatio-share-session` | Sends the Claude Code session to the Vatio team when you ask it to, or offers to when the other two finish (send it, not now, or don't ask again), after showing you what goes (images left out, anything that looks like a secret redacted), with your feedback if you want to add some |
|
|
10
18
|
|
|
11
19
|
The skills are short on purpose. They tell your coding agent when to reach for
|
|
12
20
|
the Vatio CLI; the instructions themselves come from the platform when it runs
|
|
13
21
|
`vatio docs` or `vatio flags`, so they are never out of date.
|
|
14
22
|
|
|
15
|
-
## Install
|
|
16
|
-
|
|
17
|
-
Any coding agent, from the root of your project:
|
|
18
|
-
|
|
19
|
-
```
|
|
20
|
-
npx @vatio-ai/skills
|
|
21
|
-
```
|
|
22
|
-
|
|
23
|
-
It copies the skills into `.agents/skills/` (Codex, Cursor, Gemini CLI,
|
|
24
|
-
GitHub Copilot, OpenCode and others) and `.claude/skills/` (Claude Code). Run
|
|
25
|
-
it again to update them.
|
|
26
|
-
|
|
27
|
-
Or with the open [skills](https://skills.sh) CLI, which asks which agents you
|
|
28
|
-
use and installs for those:
|
|
23
|
+
## Install in Claude Code
|
|
29
24
|
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
```
|
|
25
|
+
In your app’s project, run these commands one at a time and follow the
|
|
26
|
+
installation panel:
|
|
33
27
|
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
```
|
|
28
|
+
```text
|
|
37
29
|
/plugin marketplace add vatio-ai/skills
|
|
38
30
|
/plugin install vatio@vatio
|
|
39
31
|
```
|
|
40
32
|
|
|
33
|
+
Then ask: “Use vatio-init to build a support agent for this app. Connect it to
|
|
34
|
+
our existing users and features, define its permissions and human handoff,
|
|
35
|
+
and give me a preview to try before publishing.”
|
|
36
|
+
|
|
41
37
|
Claude Code does not update plugins from other people's marketplaces on its own:
|
|
42
38
|
turn it on once in `/plugin` → **Marketplaces** → **vatio** → **Enable
|
|
43
39
|
auto-update**, or run `claude plugin update vatio@vatio`.
|
|
@@ -63,3 +59,16 @@ Vatio, so a pull request cannot be merged here: open an issue describing the
|
|
|
63
59
|
change instead.
|
|
64
60
|
|
|
65
61
|
MIT licensed.
|
|
62
|
+
|
|
63
|
+
## Other coding agents
|
|
64
|
+
|
|
65
|
+
From the root of your project:
|
|
66
|
+
|
|
67
|
+
```bash
|
|
68
|
+
npx @vatio-ai/skills
|
|
69
|
+
```
|
|
70
|
+
|
|
71
|
+
This copies the skills into `.agents/skills/` and `.claude/skills/`.
|
|
72
|
+
Run it again to update them. Any coding agent that reads those skills can
|
|
73
|
+
follow the same procedures. You can also use `npx skills add vatio-ai/skills`
|
|
74
|
+
with the [skills CLI](https://skills.sh).
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@vatio-ai/skills",
|
|
3
|
-
"version": "1.
|
|
4
|
-
"description": "
|
|
3
|
+
"version": "1.12.0",
|
|
4
|
+
"description": "The Vatio plugin for Claude Code: build a conversational agent for your app with one prompt, then improve it daily with vatio-improve.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"vatio",
|
|
7
7
|
"agent-skills",
|
|
@@ -22,26 +22,34 @@ top. Follow those instructions; they take precedence over anything below.
|
|
|
22
22
|
|
|
23
23
|
In short:
|
|
24
24
|
|
|
25
|
-
1.
|
|
25
|
+
1. Read each report's **Diagnosis** first: it says whose it is to fix, from
|
|
26
|
+
what that turn did. **Your backend**: a tool call to it failed. **Your
|
|
27
|
+
agent**: everything answered and the reply was still wrong, so the fix is
|
|
28
|
+
in `vatio.yml`, knowledge or a tool's definition. **Vatio**: the model
|
|
29
|
+
provider or Vatio failed and Vatio wrote the reply itself. Do not change
|
|
30
|
+
the agent for those: tell the developer, who can remove the report, and
|
|
31
|
+
if they keep happening, `vatio feedback`.
|
|
32
|
+
2. Group the reports by cause, and fix each cause where it lives:
|
|
26
33
|
`vatio.yml`, a knowledge entry, a tool, or the developer's backend a tool
|
|
27
34
|
calls. `vatio tools --env live` shows each tool's error rate, timeouts and
|
|
28
35
|
latency, and the calls that failed with what the backend answered: a
|
|
29
36
|
failing tool rarely gets reported, because the agent apologizes and moves
|
|
30
37
|
on. Fix those too.
|
|
31
|
-
|
|
38
|
+
3. `vatio push`. It updates preview and runs no tests. No branch or
|
|
32
39
|
environment to set up: preview is the one.
|
|
33
|
-
|
|
40
|
+
4. `vatio eval` tests every report against preview. It can take several
|
|
34
41
|
minutes, so in Claude Code start it with the Bash tool's
|
|
35
42
|
`run_in_background` and read its report when it finishes. Iterate (fix,
|
|
36
43
|
push, eval) until the reports pass and nothing that passes on live fails.
|
|
37
|
-
|
|
38
|
-
|
|
44
|
+
A case marked "not tested (Vatio's side)" says nothing about your fix:
|
|
45
|
+
run `vatio eval` again. Name reports by id (`F-7K2QX`).
|
|
46
|
+
5. Show the developer what passes now, and `vatio publish` once they agree:
|
|
39
47
|
it changes what visitors get. If it is refused, follow its message: it
|
|
40
48
|
says what to run. Never pass `--force` unless the developer explicitly
|
|
41
49
|
asks for it.
|
|
42
|
-
|
|
50
|
+
6. If the digest, an error or the docs left you guessing, say so:
|
|
43
51
|
`vatio feedback "what you were doing and what was missing"`.
|
|
44
|
-
|
|
52
|
+
7. Last, in Claude Code, offer to send this session to the Vatio team, as
|
|
45
53
|
the `vatio-share-session` skill says. It starts with
|
|
46
54
|
`vatio share-session --should-ask`: if that prints `no`, say nothing.
|
|
47
55
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: vatio-init
|
|
3
|
-
description: The first Vatio skill in a project. Looks at what is already there — a vatio.yml anywhere in the repository, the workspace on the platform, the app's own code — and recommends from it, then either builds a customer-facing AI agent (for WhatsApp, Instagram, a website widget or an app) and gets it to the
|
|
3
|
+
description: The first Vatio skill in a project. Looks at what is already there — a vatio.yml anywhere in the repository, the workspace on the platform, the app's own code — and recommends from it, then either builds a customer-facing AI agent (for WhatsApp, Instagram, a website widget or an app) and gets it to the Test page in the Vatio inbox, or gets a developer who joined a project that already has one up to speed. Use when asked to create, set up, start or ship a Vatio agent, a chatbot or a support/sales assistant on Vatio, to get started on or onboard onto a project that uses Vatio, or when the user pastes the prompt from vatio.ai.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# Start with Vatio in this project
|
|
@@ -45,8 +45,8 @@ you recommend, and ask them to confirm.
|
|
|
45
45
|
`vatio.yml` (and `tools/` for their APIs).
|
|
46
46
|
3. `vatio diff`, `vatio push`, then try it with `vatio chat`, including a
|
|
47
47
|
conversation that should hand off.
|
|
48
|
-
4. Give them the link `vatio push` prints after `Try it:` (the
|
|
49
|
-
Test
|
|
48
|
+
4. Give them the link `vatio push` prints after `Try it:` (the inbox's
|
|
49
|
+
Test page, with web chat, WhatsApp and Instagram) with what you
|
|
50
50
|
tried. Publish with `vatio publish` only when they ask.
|
|
51
51
|
- **A `vatio.yml`: the agent exists.** Never `vatio init` here: it writes a
|
|
52
52
|
starter agent, and pushing that replaces the real one. Work from the
|
|
@@ -59,7 +59,7 @@ you recommend, and ask them to confirm.
|
|
|
59
59
|
- open reports in `vatio flags`: work them with the `vatio-improve` skill;
|
|
60
60
|
- tool calls failing in `vatio tools`: the fix is in the backend they call;
|
|
61
61
|
- `workspace_forbidden`: they are not in the workspace yet, and the owner
|
|
62
|
-
invites them from **Team** in the
|
|
62
|
+
invites them from **Team** in the inbox.
|
|
63
63
|
- **A workspace slug but no `vatio.yml`.** Ask for the repository it lives
|
|
64
64
|
in: Vatio keeps what was deployed, not the files it came from. Do not
|
|
65
65
|
`vatio init` one instead.
|