Skip to main content
A skill script is a skill that includes Python the agent can run in the code sandbox. Use it when a connector exists but its tools alone can’t handle the logic you need, such as branching, batching, or cleaning up results. You don’t need to write the script. Describe the outcome and let the agent draft the skill.

When this helps

  • Transform results before the next step (filter rows, reshape JSON)
  • Call the same connector many times with custom logic
  • Combine two connectors in one deterministic script
If you only need “send this Slack message,” add the Slack connector. Don’t wrap it in a skill.

How to get the agent to write one

  1. Add the connector on the agent first. See Give an agent a connector.
  2. Paste one of the prompts below.
  3. Review the skill. It should use the Gumloop SDK for the connector, not raw HTTP.
  4. Save it and attach it to this agent (and others, if you want).

Example prompts

Copy one of these, then swap in your mailbox, sheet, or channel. Filter unread email into a table
Batch Slack follow-ups
Sheets + Slack digest
Retry-safe CRM update

After it writes the skill

  • Keep the skill focused on one job.
  • Tell the agent which connector account to use if it has several to choose from.
  • If the script fails, paste the error back and ask it to fix the skill.
  • Every edit creates a new version. If a change breaks the skill, open the Edits tab on its detail page to see what changed and download an earlier version.

FAQ

No. Add the connector and ask the agent in chat. Use a skill script only when the connector’s tools alone can’t handle the logic you need, such as branching, batching, or cleaning up results.
Tell it: “Rewrite this to use the Gumloop SDK and the connector already on this agent. Do not call the API over HTTP.”
Yes, after you save it. Those agents still need the same connectors attached.

Code sandbox

Where skill scripts run

Agent skills

How to attach a skill