@vatio-ai/skills 1.22.0 → 1.24.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.
|
@@ -12,7 +12,7 @@
|
|
|
12
12
|
"name": "vatio",
|
|
13
13
|
"source": "./",
|
|
14
14
|
"description": "Vatio skills for Claude Code, Cursor and Codex: add an AI agent to the app you're building with /vatio-init, put it in your web, iOS, Android or Flutter app with /vatio-add-to-app, then improve it daily with /vatio-improve and learn what people ask it with /vatio-analyze.",
|
|
15
|
-
"version": "1.
|
|
15
|
+
"version": "1.24.0",
|
|
16
16
|
"homepage": "https://vatio.ai/docs/integrations/claude-code",
|
|
17
17
|
"category": "development",
|
|
18
18
|
"keywords": [
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "vatio",
|
|
3
3
|
"description": "Vatio skills for Claude Code, Cursor and Codex: add an AI agent to the app you're building with /vatio-init, put it in your web, iOS, Android or Flutter app with /vatio-add-to-app, then improve it daily with /vatio-improve and learn what people ask it with /vatio-analyze.",
|
|
4
|
-
"version": "1.
|
|
4
|
+
"version": "1.24.0",
|
|
5
5
|
"author": {
|
|
6
6
|
"name": "Vatio",
|
|
7
7
|
"url": "https://vatio.ai"
|
package/README.md
CHANGED
|
@@ -59,6 +59,36 @@ name: `/vatio-init`, `/vatio-add-to-app`, `/vatio-improve`, `/vatio-analyze` and
|
|
|
59
59
|
`vatio init` also writes a pointer to `vatio flags` into the workspace's
|
|
60
60
|
`AGENTS.md`, which most coding agents read without installing anything.
|
|
61
61
|
|
|
62
|
+
## What it runs and sends
|
|
63
|
+
|
|
64
|
+
The skills are instructions for your coding agent, with no hooks, MCP servers
|
|
65
|
+
or anything that runs by itself. What they have your agent run is one
|
|
66
|
+
program, the [Vatio CLI](https://github.com/vatio-ai/cli)
|
|
67
|
+
(`npx @vatio-ai/cli`, downloaded from npm), and it talks to one service,
|
|
68
|
+
[vatio.ai](https://vatio.ai):
|
|
69
|
+
|
|
70
|
+
- **Sign-in.** The first `vatio push` (or `vatio login`) opens vatio.ai in your
|
|
71
|
+
browser; the token it gets back is saved in `~/.vatio/config.json`.
|
|
72
|
+
- **Your agent's files.** `vatio check` and `vatio push` send the directory
|
|
73
|
+
that holds `vatio.yml` (its tools and knowledge, never hidden files such as
|
|
74
|
+
`.env` or `.git/`) to vatio.ai, which runs the agent. `vatio secrets set`
|
|
75
|
+
sends a secret you name, stored encrypted.
|
|
76
|
+
- **Conversations.** `vatio chat` sends what you type to your agent.
|
|
77
|
+
`vatio flags`, `vatio chat show` and `vatio chat export` (redacted by Vatio
|
|
78
|
+
before it leaves) bring your workspace's conversations to your terminal.
|
|
79
|
+
`vatio docs` fetches the docs.
|
|
80
|
+
- **How each command ended.** The CLI tells Vatio which command ran, its exit
|
|
81
|
+
code and, on failure, what it printed; never arguments, file contents,
|
|
82
|
+
secrets or what a chat said. `VATIO_TELEMETRY=0` turns it off.
|
|
83
|
+
- **Feedback.** `vatio feedback "..."` sends the text your agent writes about
|
|
84
|
+
what got in its way.
|
|
85
|
+
- **Your coding session, only if you say yes.** `vatio-share-session` shows
|
|
86
|
+
you what would go (images left out, anything that looks like a secret
|
|
87
|
+
redacted) and sends it to the Vatio team only after you agree.
|
|
88
|
+
|
|
89
|
+
What Vatio keeps and for how long is in its
|
|
90
|
+
[privacy policy](https://vatio.ai/legal/privacy-policy).
|
|
91
|
+
|
|
62
92
|
## Docs
|
|
63
93
|
|
|
64
94
|
[Improve your agent from flags](https://vatio.ai/docs/improve) ·
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@vatio-ai/skills",
|
|
3
|
-
"version": "1.
|
|
3
|
+
"version": "1.24.0",
|
|
4
4
|
"description": "Vatio skills for Claude Code, Cursor and Codex: add an AI agent to the app you're building with /vatio-init, put it in your web, iOS, Android or Flutter app with /vatio-add-to-app, then improve it daily with /vatio-improve and learn what people ask it with /vatio-analyze.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"vatio",
|
|
@@ -33,6 +33,13 @@ In short:
|
|
|
33
33
|
developer's call: propose it (a report Vatio caused, one that asks for
|
|
34
34
|
something the agent must not do, one whose fix is in but the tests cannot
|
|
35
35
|
reproduce) and run it only when they say so.
|
|
36
|
+
A report can also say **What Vatio did**: when the cause was the agent's
|
|
37
|
+
instructions or a knowledge entry, Vatio already tried its own fix on
|
|
38
|
+
preview and tested it. One it kept is done: do not fix it again. One it
|
|
39
|
+
is still testing: leave what it changes alone until it settles. An
|
|
40
|
+
instructions fix is a change made outside the files, so before you edit
|
|
41
|
+
`vatio.yml` run `vatio pull` (commit your work first: it wants a clean git
|
|
42
|
+
tree) and check `git diff`.
|
|
36
43
|
2. Group the reports by cause, and fix each cause where it lives:
|
|
37
44
|
`vatio.yml`, a knowledge entry, a tool, or the developer's backend a tool
|
|
38
45
|
calls. `vatio tools --env live` shows each tool's error rate, timeouts and
|