@vatio-ai/skills 1.14.0 → 1.14.1
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/.claude-plugin/marketplace.json +1 -1
- package/.claude-plugin/plugin.json +2 -2
- package/README.md +28 -18
- package/package.json +2 -2
- package/skills/vatio-init/SKILL.md +1 -1
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
{
|
|
6
6
|
"name": "vatio",
|
|
7
7
|
"source": "./",
|
|
8
|
-
"description": "
|
|
8
|
+
"description": "Vatio skills for Claude Code, Cursor and Codex: add an AI agent to the app you're building with /vatio-init, 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.14.
|
|
3
|
+
"description": "Vatio skills for Claude Code, Cursor and Codex: add an AI agent to the app you're building with /vatio-init, then improve it daily with /vatio-improve.",
|
|
4
|
+
"version": "1.14.1",
|
|
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,46 +1,56 @@
|
|
|
1
|
-
# Vatio:
|
|
1
|
+
# Vatio: an AI agent for the app you’re building
|
|
2
2
|
|
|
3
|
-
|
|
4
|
-
|
|
3
|
+
Building an app with Claude Code, Cursor or Codex? Give it an agent that knows
|
|
4
|
+
the app and its users. In your app’s project:
|
|
5
|
+
|
|
6
|
+
```bash
|
|
7
|
+
npx @vatio-ai/skills
|
|
8
|
+
```
|
|
9
|
+
|
|
10
|
+
Then, in Claude Code, run `/vatio-init` (in Cursor or Codex, ask it to use
|
|
11
|
+
vatio-init). It builds the agent from your project; [Vatio](https://vatio.ai)
|
|
5
12
|
runs it with an inbox, human handoff and evaluation checks. You try the preview
|
|
6
13
|
and approve publication.
|
|
7
14
|
|
|
8
|
-
After launch, report mistakes in the inbox and make `/vatio
|
|
9
|
-
daily routine.
|
|
10
|
-
approve the update. You do not need to write code yourself; you
|
|
11
|
-
your app’s project
|
|
15
|
+
After launch, report mistakes in the inbox and make `/vatio-improve` your
|
|
16
|
+
daily routine. Your coding agent prepares fixes, Vatio tests the reported
|
|
17
|
+
cases, and you approve the update. You do not need to write code yourself; you
|
|
18
|
+
need your app’s project on your computer and Node.js 20 or newer.
|
|
12
19
|
|
|
13
20
|
| Skill | What it does |
|
|
14
21
|
|---|---|
|
|
15
22
|
| `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 |
|
|
16
23
|
| `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 test` (on Vatio's servers, in the background) and publishes with `vatio publish` after your approval |
|
|
17
|
-
| `vatio-share-session` | Sends the
|
|
24
|
+
| `vatio-share-session` | Sends the coding 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 |
|
|
18
25
|
|
|
19
26
|
The skills are short on purpose. They tell your coding agent when to reach for
|
|
20
27
|
the Vatio CLI; the instructions themselves come from the platform when it runs
|
|
21
28
|
`vatio docs` or `vatio flags`, so they are never out of date.
|
|
22
29
|
|
|
23
|
-
## Install
|
|
30
|
+
## Install
|
|
31
|
+
|
|
32
|
+
`npx @vatio-ai/skills` copies the skills into `.claude/skills/`, where Claude
|
|
33
|
+
Code reads them, and `.agents/skills/`, where Codex, Cursor, Gemini CLI,
|
|
34
|
+
GitHub Copilot and most other coding agents do. Run it again to update them.
|
|
24
35
|
|
|
25
|
-
|
|
26
|
-
|
|
36
|
+
### As a Claude Code plugin
|
|
37
|
+
|
|
38
|
+
In Claude Code the same skills come as a plugin that can update itself. Run
|
|
39
|
+
these one at a time and follow the installation panel; the commands are then
|
|
40
|
+
`/vatio:vatio-init` and `/vatio:vatio-improve`:
|
|
27
41
|
|
|
28
42
|
```text
|
|
29
43
|
/plugin marketplace add vatio-ai/skills
|
|
30
44
|
/plugin install vatio@vatio
|
|
31
45
|
```
|
|
32
46
|
|
|
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
|
-
|
|
37
47
|
Claude Code does not update plugins from other people's marketplaces on its own:
|
|
38
48
|
turn it on once in `/plugin` → **Marketplaces** → **vatio** → **Enable
|
|
39
49
|
auto-update**, or run `claude plugin update vatio@vatio`.
|
|
40
50
|
|
|
41
|
-
Your agent then uses them on its own when you ask it to build, improve
|
|
42
|
-
a Vatio agent, or to send the session to Vatio, or you can call them by
|
|
43
|
-
`/vatio-init`, `/vatio-improve` and `/vatio-share-session`, or
|
|
51
|
+
Your coding agent then uses them on its own when you ask it to build, improve
|
|
52
|
+
or fix a Vatio agent, or to send the session to Vatio, or you can call them by
|
|
53
|
+
name: `/vatio-init`, `/vatio-improve` and `/vatio-share-session`, or
|
|
44
54
|
`/vatio:vatio-init` and so on from the plugin.
|
|
45
55
|
|
|
46
56
|
`vatio init` also writes a pointer to `vatio flags` into the workspace's
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@vatio-ai/skills",
|
|
3
|
-
"version": "1.14.
|
|
4
|
-
"description": "
|
|
3
|
+
"version": "1.14.1",
|
|
4
|
+
"description": "Vatio skills for Claude Code, Cursor and Codex: add an AI agent to the app you're building with /vatio-init, then improve it daily with /vatio-improve.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"vatio",
|
|
7
7
|
"agent-skills",
|
|
@@ -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 (
|
|
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 (in the app first, through its web widget or mobile SDK, and on WhatsApp or Instagram when asked) 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
|