imagegen-smarto 0.1.1 → 0.1.2
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 +9 -2
- package/imagegen-smarto/SKILL.md +22 -4
- package/imagegen-smarto/agents/openai.yaml +2 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -5,8 +5,15 @@ through a custom SmartO OpenAI-compatible VPS relay.
|
|
|
5
5
|
|
|
6
6
|
The skill does not call Codex's built-in `image_gen` tool. It places a private
|
|
7
7
|
routing marker in the Responses instructions; the relay adds its
|
|
8
|
-
`image_generation` tool
|
|
9
|
-
non-image requests
|
|
8
|
+
`image_generation` tool for requests that load this skill, merging it with
|
|
9
|
+
existing function, shell, file, or other tools. Ordinary non-image requests
|
|
10
|
+
remain unchanged.
|
|
11
|
+
|
|
12
|
+
When the SmartO profile is active, this skill can also replace only the image
|
|
13
|
+
provider inside workflows that normally use `$imagegen`, including the
|
|
14
|
+
official `hatch-pet` workflow. The workflow's prompts, references, QA, and
|
|
15
|
+
file handling remain unchanged; only image generation is routed through
|
|
16
|
+
SmartO.
|
|
10
17
|
|
|
11
18
|
## Install with npm
|
|
12
19
|
|
package/imagegen-smarto/SKILL.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: imagegen-smarto
|
|
3
|
-
description: Generate or edit raster images through the user's SmartO OpenAI-compatible VPS relay. Automatically use this skill for natural-language requests to create, draw, generate, or edit an image when the SmartO relay profile is active
|
|
3
|
+
description: Generate or edit raster images through the user's SmartO OpenAI-compatible VPS relay. Automatically use this skill for natural-language requests to create, draw, generate, or edit an image when the SmartO relay profile is active. It is also the drop-in image-generation provider for workflows that normally invoke `$imagegen`, including `hatch-pet`; preserve those workflows and replace only the image-generation execution layer. Do not use it for image analysis or coding tasks, official OpenAI/ChatGPT providers, or the built-in image_gen tool.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# SmartO relay image generation
|
|
@@ -10,6 +10,20 @@ SmartO relay profile is active. It is implicitly invokable, so the user should
|
|
|
10
10
|
be able to ask for an image in natural language without first writing
|
|
11
11
|
`$imagegen-smarto`.
|
|
12
12
|
|
|
13
|
+
When another active skill invokes `$imagegen` for a visual job (including the
|
|
14
|
+
official `hatch-pet` skill), treat this skill as the selected image-generation
|
|
15
|
+
provider when the SmartO relay profile is active. Keep the calling skill's
|
|
16
|
+
workflow, prompts, reference-image requirements, QA, and file handling
|
|
17
|
+
unchanged; replace only the provider-specific built-in image-generation call.
|
|
18
|
+
If that skill also loads the official `.system/imagegen/SKILL.md`, retain its
|
|
19
|
+
prompting and output-quality guidance but override only its provider-selection
|
|
20
|
+
rules: do not call the built-in `image_gen` tool and do not use its CLI/API
|
|
21
|
+
fallback. Use the normal Responses request through SmartO instead.
|
|
22
|
+
Every separate image-generation worker request must load this routing
|
|
23
|
+
instruction so the marker below is present in that request's Responses
|
|
24
|
+
`instructions` field. Do not ask the user to type the marker or add it to the
|
|
25
|
+
image prompt.
|
|
26
|
+
|
|
13
27
|
This skill is a routing signal, not a local image-generation tool:
|
|
14
28
|
|
|
15
29
|
- Never call the built-in `image_gen` tool or any other native image tool.
|
|
@@ -27,14 +41,18 @@ built-in image tool:
|
|
|
27
41
|
`__CODEX_VPS_IMAGEGEN__`
|
|
28
42
|
|
|
29
43
|
The relay-side rule should apply only to `/v1/responses` requests whose
|
|
30
|
-
`instructions` contain that marker. It
|
|
31
|
-
|
|
44
|
+
`instructions` contain that marker. It must merge the image tool into the
|
|
45
|
+
request's existing `tools` array, preserving every client-declared tool. If
|
|
46
|
+
the request has no `tools`, create the array. Do not skip injection merely
|
|
47
|
+
because the request already contains shell, file, function, or other tools:
|
|
32
48
|
|
|
33
49
|
```json
|
|
34
50
|
{"type":"image_generation","action":"auto"}
|
|
35
51
|
```
|
|
36
52
|
|
|
37
|
-
|
|
53
|
+
Do not add a duplicate if an equivalent `image_generation` tool is already
|
|
54
|
+
present. It may set `tool_choice` to `auto` only when the client did not
|
|
55
|
+
provide one.
|
|
38
56
|
Do not force image generation for every turn. The upstream model decides from
|
|
39
57
|
the natural-language request whether to generate a new image or edit an image
|
|
40
58
|
in context.
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
interface:
|
|
2
2
|
display_name: "SmartO VPS Image Generation"
|
|
3
|
-
short_description: "Generate images through
|
|
4
|
-
default_prompt: "Use
|
|
3
|
+
short_description: "Generate images through SmartO, including $imagegen workflows"
|
|
4
|
+
default_prompt: "Use SmartO as the image-generation provider for this workflow, including workflows that normally invoke $imagegen."
|
|
5
5
|
|
|
6
6
|
policy:
|
|
7
7
|
allow_implicit_invocation: true
|