@xpr-agents/openclaw 0.6.1 → 0.7.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.
- package/README.md +10 -2
- package/package.json +1 -1
- package/skills/blockart/SKILL.md +75 -0
- package/skills/blockart/dist/index.js +722 -0
- package/skills/blockart/skill.json +16 -0
- package/skills/blockart/src/index.ts +770 -0
- package/skills/blockart/tsconfig.json +14 -0
- package/skills/creative/SKILL.md +20 -0
- package/skills/creative/dist/index.js +66 -5
- package/skills/creative/src/index.ts +67 -5
- package/skills/xpr-agent-operator/SKILL.md +1 -0
- package/dist/cli-session 2.js +0 -89
- package/dist/cli-session.d 2.ts +0 -60
- package/dist/cli-session.d.ts 2.map +0 -1
- package/dist/cli-session.js 2.map +0 -1
- package/dist/index 2.js +0 -125
- package/dist/index.d 2.ts +0 -43
- package/dist/index.d.ts 2.map +0 -1
- package/dist/index.js 2.map +0 -1
- package/dist/proton-cli 2.js +0 -237
- package/dist/proton-cli.d 2.ts +0 -73
- package/dist/proton-cli.d.ts 2.map +0 -1
- package/dist/proton-cli.js 2.map +0 -1
- package/dist/session 2.js +0 -41
- package/dist/session.d 2.ts +0 -36
- package/dist/session.d.ts 2.map +0 -1
- package/dist/session.js 2.map +0 -1
- package/dist/skill-types 2.js +0 -9
- package/dist/skill-types.d 2.ts +0 -61
- package/dist/skill-types.d.ts 2.map +0 -1
- package/dist/skill-types.js 2.map +0 -1
- package/dist/types 2.js +0 -6
- package/dist/types.d 2.ts +0 -39
- package/dist/types.d.ts 2.map +0 -1
- package/dist/types.js 2.map +0 -1
package/README.md
CHANGED
|
@@ -211,8 +211,16 @@ proton chain:set proton # mainnet (use `proton-test` for testne
|
|
|
211
211
|
# - WebAuth mobile app → Backup Wallet → reveal private key
|
|
212
212
|
#
|
|
213
213
|
# Alternatively, if you already control a funded XPR account, use:
|
|
214
|
-
# proton account:create myagent
|
|
215
|
-
#
|
|
214
|
+
# proton account:create-funded myagent \
|
|
215
|
+
# --creator myfundedacct --owner myhumanacct --ram 8192
|
|
216
|
+
# --creator is required: that account signs the creation and pays the
|
|
217
|
+
# RAM. --owner adds a backup account to the new account's owner
|
|
218
|
+
# permission. --ram defaults to 3000 bytes (min 3000, ~6-7 XPR per
|
|
219
|
+
# 3000). With no --key the CLI generates the keypair, prints the
|
|
220
|
+
# public key, private key and a 12-word mnemonic, and adds the private
|
|
221
|
+
# key to the keychain for you — so you can skip step 4 below.
|
|
222
|
+
# (`proton account:create`, without -funded, is a different command:
|
|
223
|
+
# the email + 6-digit verification-code flow, no funding account.)
|
|
216
224
|
|
|
217
225
|
# 4. Load the key (interactive — pastes are hidden)
|
|
218
226
|
proton key:add # paste your PVT_K1_ key; stored encrypted
|
package/package.json
CHANGED
|
@@ -0,0 +1,75 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: blockart
|
|
3
|
+
description: Block Art fulfilment — the XPR atom emblem, every trait derived from the block the buyer paid in
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
## Block Art
|
|
7
|
+
|
|
8
|
+
Block Art is a fixed-price listing on the services market. A buyer pays, and gets
|
|
9
|
+
a 2048px render of the XPR Network atom emblem whose every visual trait is
|
|
10
|
+
derived from **the block their payment confirmed in**. Nothing about the piece is
|
|
11
|
+
chosen by you: the block chooses it, and `traits.json` ships alongside the image
|
|
12
|
+
so the buyer can check the derivation themselves.
|
|
13
|
+
|
|
14
|
+
A Block Art job arrives as a funded escrow job with `job_hash` `"svc:4"`.
|
|
15
|
+
|
|
16
|
+
### The two tools
|
|
17
|
+
|
|
18
|
+
- `blockart_plan` — `{ job_id }`. Reads the job, recovers the seed block, derives
|
|
19
|
+
the traits, reads the buyer's form answers and any revision notes, builds the
|
|
20
|
+
prompt, and persists the plan. Read-only, no spend, no signing.
|
|
21
|
+
- `blockart_render` — `{ job_id }`. Renders the planned piece, pins the image and
|
|
22
|
+
`traits.json` to IPFS under one CID, and returns a delivery manifest. It never
|
|
23
|
+
signs and never delivers.
|
|
24
|
+
|
|
25
|
+
### The flow
|
|
26
|
+
|
|
27
|
+
1. `blockart_plan` with the job id. **Read the `summary`.** It tells you the seed
|
|
28
|
+
block, the eight traits, and what the buyer asked for.
|
|
29
|
+
2. If the buyer's notes ask for something the listing does not offer — a
|
|
30
|
+
different subject, a different format, print or physical delivery, a logo or
|
|
31
|
+
any text in the image, a trait they want overridden — ask them **ONE** question
|
|
32
|
+
with `xpr_ask_client` and stop. Do not guess, and do not ask a second question
|
|
33
|
+
later.
|
|
34
|
+
3. Otherwise `blockart_render` with the same job id.
|
|
35
|
+
4. `xpr_deliver_job` with `evidence_uri` set to the manifest string the render
|
|
36
|
+
returned, **exactly as returned**. Do not rewrite it, do not wrap it, do not
|
|
37
|
+
substitute a bare gateway link.
|
|
38
|
+
|
|
39
|
+
### What the block fixes, and what it does not
|
|
40
|
+
|
|
41
|
+
The block fixes the material of the three orbits, the setting, the light, the
|
|
42
|
+
palette, the motion, the scale, the time of day, and (from the buyer's account
|
|
43
|
+
age) the patina. It says nothing about what else may share the scene, so a
|
|
44
|
+
buyer's theme is honoured **in the surroundings** — the environment, the sky, the
|
|
45
|
+
forms and shadows around the atom — while the atom itself stays the single clear
|
|
46
|
+
subject, unchanged in geometry. A buyer never gets to override a trait; if they
|
|
47
|
+
ask to, that is a question for them, not a decision for you.
|
|
48
|
+
|
|
49
|
+
### Revisions
|
|
50
|
+
|
|
51
|
+
If the client sends the job back with `revise`:
|
|
52
|
+
|
|
53
|
+
- Re-run `blockart_plan`. It **reuses the same seed block** — the traits cannot
|
|
54
|
+
change, or the piece stops matching the block the buyer was told it came from.
|
|
55
|
+
- The plan folds their revise note into the prompt's steer automatically. Read
|
|
56
|
+
the summary again to see it.
|
|
57
|
+
- Re-render, then deliver. **Never deliver identical evidence**: if the render
|
|
58
|
+
came back the same, say so and ask rather than re-sending the previous CID.
|
|
59
|
+
- If their note asks for a trait to change, that is not a re-render — ask with
|
|
60
|
+
`xpr_ask_client`.
|
|
61
|
+
|
|
62
|
+
### Environment
|
|
63
|
+
|
|
64
|
+
| Variable | Required for | Default |
|
|
65
|
+
|----------|--------------|---------|
|
|
66
|
+
| `REPLICATE_API_TOKEN` | `blockart_render` | — |
|
|
67
|
+
| `PINATA_JWT` | `blockart_render` | — |
|
|
68
|
+
| `PINATA_GATEWAY` | pinned URLs | `https://agent.mypinata.cloud` |
|
|
69
|
+
| `HYPERION_URL` | seed block + revise notes | a public XPR node |
|
|
70
|
+
| `XPR_RPC_ENDPOINT` | all chain reads | shared with the other skills |
|
|
71
|
+
| `BLOCKART_WORK_DIR` | plan + render storage | `./blockart-work` |
|
|
72
|
+
|
|
73
|
+
Both tools return `{ error: "..." }` rather than throwing. If the error names a
|
|
74
|
+
missing environment variable, say so plainly and stop — do not deliver a
|
|
75
|
+
description of the artwork in place of the artwork.
|