workflows-optimize-credits
Skill from clay-run/agent-plugins
Install
npx skills add clay-run/agent-plugins --skill workflows-optimize-credits
Runs the open skills CLI and installs the skill for your agent (Claude Code, Codex, Cursor …). Alternatively copy the skill folder into .claude/skills/ or upload it in Claude.ai under Settings → Skills.
As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-official
/plugin install clay@clay-plugins
This skill is part of the plugin “clay”. In Claude Code the plugin installs it together with the plugin’s other skills, commands and hooks.
What does the workflows-optimize-credits skill do?
Description from the SKILL.md in the source repository.
Questions about workflows-optimize-credits
What does the workflows-optimize-credits skill do?
Clay workflows — reduce a workflow's credit and LLM cost via the CLI (`clay workflows` commands). Identifies expensive patterns and suggests cheaper alternatives.
How do I install workflows-optimize-credits?
In a terminal: npx skills add clay-run/agent-plugins --skill workflows-optimize-credits. The skills CLI asks which agents to install it for. In Claude.ai you can upload the skill folder as a ZIP under Settings → Skills.
Which agents can use workflows-optimize-credits?
Skills use the open SKILL.md format, which Claude Code, Claude.ai, the Claude API, OpenAI Codex, Cursor, Gemini CLI and other agents support.
Is workflows-optimize-credits safe to use?
Our automatic check found no risky patterns (piped shell scripts, hidden characters, secret access, prompt overrides). It is not a full audit – read the SKILL.md and any scripts before installing.
More skills from clay-run/agent-plugins
Clay tables — sweep a table for errored rows and report grouped by root cause (not a specific record).
Clay workflow alerts — use when the user wants to create, inspect, edit, enable, disable, or delete a workflow alert rule, or subscribe themselves to its email notifications.
Keep Clay up to date. Use when the user asks to update or upgrade Clay, the plugin, or the `clay` CLI; when `clay update` reports the CLI is pinned / managed by …
Clay tables — explain one cell by walking a column backward through its dependencies and run-gate to the origin or root cause.
Clay tables — locate a record by identifier and snapshot its state: which table(s) hold it and each cell's status.
Clay tables — check the row-capacity ceiling when imports stall, before assuming a run/config/enrichment problem.
Clay tables — analyze what a table does: reconstruct the column DAG, stage it, and narrate the workflow encoded in its columns.
Clay workflows — build enrichment steps and map their results back to Audiences in an existing audience enrichment workflow.
Related skills in Agents & Workflows
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in …
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
Teach the user a new skill or concept, within this workspace.
No description in the SKILL.md.
No description in the SKILL.md.
Ask which skill or flow fits your situation. A router over the skills in this repo.
No description in the SKILL.md.
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until …