AGENT SKILL

synthetic-model

A model skill made up for the converter tests.

License 许可
MIT
所属仓库
eachlabs/plugin
最近更新
2026-10-29
Stars
★ 0
Forks
0

01 前言 Front Matter

name
synthetic-model
description
A model skill made up for the converter tests.

02 资源文件 1

03 SKILL.md 正文

Synthetic Model

Authentication is handled by the each::labs connector sign-in. The limit is 10 requests per organization.

Tools

This skill uses the each::labs connector. Sign-in happens through the connector; no API key is needed.

In an app that shows no cards, such as Claude Code or another terminal, do not call the tools that show or wait for a card (request_* and wait_for_*): ask in the chat instead, for a public URL of each file and for the values of any settings, range, crop, workflow inputs or choice.

Tool Arguments and result
get_model_schema slug; the model's input schema
run_model model, version ("0.0.1"), input, count; runs the model and waits for it. When the person asks for several variants of one prompt, make one call: set the model's own count parameter (num_images, num_outputs, n, number_of_images, batch_size, num_samples, whatever get_model_schema shows) when it has one, otherwise set count to the number asked for (up to 8). Never call run_model once per variant: each call shows its own result card, and the picker only appears when the variants arrive together
get_job prediction_id; the prediction with its status and output
request_file prompt saying what to upload, accept ("image", "video", "audio"), count (the number of files the person mentioned), max (the most files the model takes for that input: the array's maxItems in get_model_schema, or the video tool's input limit); shows an upload card in the conversation and returns a receipt_url. In an app that shows cards, call it as soon as the model needs a file the person has not given as a URL; do not ask for a URL first, and mention that a URL works too. Then call wait_for_upload with the receipt_url right away: it returns each file's name, kind and public_url once the upload is done, and the public_url is the input URL. If it answers waiting, call it again. When a model takes files with different roles (a person and a garment, a source face and a target), show one card per role so each URL is unambiguous; otherwise one card takes the whole set, for example all the images of a slideshow
wait_for_upload receipt_url from request_file; waits for the person's upload and returns the uploaded files with their public_url
request_parameters model, version, input (what you would pass to run_model), prompt; shows the model's settings as a card the person can adjust, and returns a receipt_url. Use it when the person asks to adjust or choose settings, or when the model has options the person did not mention (aspect ratio, duration, number of outputs) and the run costs more than a few cents; otherwise call run_model directly. Then call wait_for_parameters with the receipt_url right away and run the model with the input it returns. After the first run of a model in a conversation, end your reply with one markdown line of exactly this shape: **Adjust generation settings:** <two or three of this model's settings in plain words, such as aspect ratio, duration or number of images>. Just ask. Never use the words card, widget, tool or parameters in that line. Write it once per conversation, and skip it when the person has already adjusted settings
show_files urls (1 to 8 public URLs on each::labs storage), title; shows files the person already has as a result card: a picked variant, an earlier result, an uploaded input. No model runs
wait_for_parameters receipt_url from request_parameters; waits for the person to press Run and returns model, version and input for run_model
wait_for_choice receipt_url from a result that holds several outputs (choice_receipt_url in the result; the card offers a choice only when the person asked for several variants). Always call it right after showing the results: it returns once the person selects a variant and presses Use this variant, and you continue with that one. If it answers waiting, call it again; do not ask the person to type which one they want while the card is waiting
request_trim url (a video or audio file on each::labs storage), kind ("video" or "audio"), prompt; shows the file with a timeline and two handles for the start and the end, and returns a receipt_url. Use it when the person wants to cut, shorten, trim or keep part of a clip and has not given exact times; when they give the seconds, call trim directly. Then call wait_for_edit with the receipt_url right away and call trim with input_url set to the url and the start and duration it returns
request_crop url (a video or image on each::labs storage), prompt; shows the first frame with a rectangle the person moves and resizes, with aspect presets, and returns a receipt_url. Use it when the person wants to crop or reframe and has not given exact pixels; when they give the pixels, call crop directly. Then call wait_for_edit with the receipt_url right away and call crop with input_url set to the url and the x, y, width and height it returns
wait_for_edit receipt_url from request_trim or request_crop; waits for the person to press the button and returns the range (start, duration) or the rectangle (x, y, width, height) with the url. If it answers waiting, call it again
list_workflows When the task has more than one step, a fixed prompt reused across runs, or needs a fallback, call it first: the organization may have a workflow that does the whole thing in one call. Read a candidate with get_workflow and run it with trigger_workflow (the workflows skill has the details). If none matches, do the steps with the tools above

If the result says running, call get_job with the returned id and wait: true: the server waits for the job and returns the result, so do not sleep or poll between calls; if it still says running, call it again the same way. When the person asks to see a result again, or the variant they picked, call show_files with the URLs you already have: the result card shows a file only under a tool call. Never run a model or a video tool just to display a file that exists.

When a result is an edit of an image or video the person gave, the result card has a Compare toggle that shows the input and the result side by side; do not describe the difference in words unless asked.

Quick Start

  1. Check model — call get_model_schema with slug "flux-2-pro" and read its input schema.
  2. Check schema — call get_model_schema with slug set to the model slug
  3. Run — call run_model with the model and input.
  4. Wait — if run_model returned status running, call get_job with the prediction_id until it finishes.

Each image is run through run_model and read with get_job. Process several by calling run_model once for each image.

Run the model

Call run_model with these arguments:

{
  "model": "flux-2-pro",
  "version": "0.0.1",
  "input": {
    "prompt": "a cat",
    "image_url": "https://example.com/cat.png"
  }
}

Read the result

Call get_job with prediction_id set to the id returned by run_model.

Call get_model_schema with slug "flux-2-pro".

TODO(contract): no tool for POST https://api.eachlabs.ai/v1/unknown/route

TODO(contract): prediction body is not JSON: not json

TODO(contract): prediction body without model or input

TODO(contract): each::sense call POST https://eachsense-agent.core.eachlabs.run/v1/chat/completions has no tool in this version

TODO(contract): no tool for GET https://other.example.com/v1/thing

TODO(contract): cannot read the URL of a command: curl --help

TODO(contract): unexpected line in a command block: echo done

{"kept": "a block without curl stays as it is", "url": "https://example.com/song.mp3"}
{"video_url": "https://example.com/clip.mp4", "file": "https://example.com/no-extension"}

Code with a hash line

# not a heading
print("x")

Notes

The last section stays.

04 同仓库更多 Skills

eachlabs
eachlabs/plugin

gpt-image-v2

Generate and edit images using OpenAI's GPT Image v2 via EachLabs. Supports text-to-image (gpt-image-v2-text-to-image) and instruction-based editing (gpt-image-v2-edit). Use when the user specifically asks for GPT Image 2 / OpenAI image generation, or needs high-fidelity photorealism, precise text rendering, or reference-faithful edits. Use for any request to create or edit an image with GPT Image 2 on each::labs.

★ 0
eachlabs
eachlabs/plugin

eachlabs-workflows

Run and inspect multi-step AI workflows that chain multiple EachLabs models into one call. List the organization's workflows, read a workflow's versions and inputs, trigger a version and read the execution's outputs. Use when the user wants to run an existing workflow or check one that is running, and whenever a task chains several models, reuses a fixed prompt, needs a fallback model, runs steps in parallel, routes on a condition, or calls an HTTP API between model steps: check for a matching workflow before chaining models by hand. Building or editing workflows happens in the each::labs dashboard.

★ 0
eachlabs
eachlabs/plugin

eachlabs-voice-audio

Text-to-speech, speech-to-text, voice conversion, and audio processing using EachLabs AI models. Supports ElevenLabs TTS, Whisper transcription with diarization, and RVC voice conversion. Use when the user needs TTS, transcription, or voice conversion. Use for any request to create or change speech and voice audio: generate speech, transcribe it or convert a voice with each::labs.

★ 0
eachlabs
eachlabs/plugin

eachlabs-video-generation

Generate new videos from text prompts, images, or reference inputs using EachLabs AI models. Supports text-to-video, image-to-video, transitions, motion control, talking head, and avatar generation. Use when the user wants to create new video content. For editing existing videos, see eachlabs-video-edit. Use for any request to create a new video from text, an image or a reference: generate or animate it with each::labs.

★ 0
eachlabs
eachlabs/plugin

eachlabs-video-edit

Edit, transform, extend, upscale, and enhance videos using EachLabs AI models. Supports lip sync, video translation, subtitle generation, audio merging, style transfer, and video extension. Use when the user wants to edit or transform existing video content. Use for any request to change a video: edit, restyle, extend, upscale, lip-sync, translate, subtitle or add audio to it with each::labs.

★ 0
eachlabs
eachlabs/plugin

eachlabs-product-visuals

Generate professional e-commerce product photography and videos using EachLabs AI models. Product shots, background replacement, lifestyle scenes, and 360-degree views. Use when the user needs product images for e-commerce or marketing. Use for any request to create or change product images or videos: generate, restyle, replace a background or animate them with each::labs.

★ 0