frontier-ai-nextfrontier-ai-next/mgarlbot/skills/code_execution/SKILL.md

code_execution

Skill17 starsChanged 4 months agoMITView on GitHub

Run Python code, scripts, calculations, and data processing

1 other project uses a version of this.

Adopted by

Most recently taken up by

Shugar86/my-agenttheir own version, first seen May 28, 2026

Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
Shugar86/my-agent★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- app_controlSkill
- aws_opsSkill
- desktop_automationSkill
- docker_deploySkill
- file_operationsSkill
- gitlab_apiSkill
- gitlab_pages_ciSkill
- ops_dns_regruSkill
- ops_reverse_proxySkill
- ops_tmux_remote_deploySkill
- system_infoSkill
- vps_host_sshSkill

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Use the code interpreter (sandboxed Python).
line 11
Very specific:
Use code_interpreter for math and in-sandbox data work.
line 40
Very specific:
Use shell for filesystem operations on the host.
line 41
Very specific:
Always print() results; otherwise output may be empty.
line 43
Distinctive:
Prefer one coherent code block for multi-step logic.
line 44

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Code execution

Use the code interpreter (sandboxed Python).

Simple math

result = 2 ** 10
print(f"2^10 = {result}")

Data handling

import json
data = {"name": "test", "values": [1, 2, 3]}
print(json.dumps(data, indent=2))

Commonly allowed modules (safe mode)

math, statistics
json
re
datetime
collections
itertools, functools
random

Rules

Use code_interpreter for math and in-sandbox data work.
Use shell for filesystem operations on the host.
Imports are restricted — only allowed modules work.
Always print() results; otherwise output may be empty.
Prefer one coherent code block for multi-step logic.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free