Terminal
Terminal/Skill
Generates alt text, title, caption and description for a local image as JSON, or object labels for it, using the Transloadit CLI.
By Transloadit
Works with
npx skills add transloadit/skills --skill transform-describe-image-with-transloadit.json output path; default is the same path with .jsonResolve credentials in this order:
.env only~/.transloadit/credentialsIf your .env lives in a parent directory, export the variables into the shell first.
Use the official Transloadit Node CLI directly.
Labels / object-style description:
npx -y @transloadit/node image describe \
--input ./input.jpg \
--fields labels \
--output ./labels.json
WordPress-ready fields:
npx -y @transloadit/node image describe \
--input ./input.jpg \
--for wordpress \
--output ./fields.json
Custom field selection:
npx -y @transloadit/node image describe \
--input ./input.jpg \
--fields altText,title,caption,description \
--output ./fields.json
If you omit --output, the CLI writes the JSON file next to the input image using the same base
name. After the command finishes, confirm the JSON file exists at the expected output path.
--fields labels returns a JSON array of labels.
--for wordpress and authored --fields ... return a JSON object with requested string fields, for example:
{
"altText": "...",
"title": "...",
"caption": "...",
"description": "..."
}
--for wordpress when you want publishable CMS fields.--fields labels when you want recognizer-style tags instead of authored copy.--model only matters for authored fields, not for labels.~/.transloadit/credentials as the default fallback when you want a reusable user-level setup..env still takes precedence, so avoid it when deterministic account selection matters..env, run the command from that directory or export the variables first.npx -y @transloadit/node assemblies get <assemblyIdOrUrl> -j