agentleFS
Sign inStart free
QuixiAIQuixiAI/Hexis/skills/installed/code-execution/SKILL.md

code-execution

Skill623 starsChanged 10 months agoMITView on GitHub

Run programs, shell commands, and scripts — compile and execute code, test programs in installed languages, work with files in the workspace

6 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use code-transfer, timeline-creator and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • nek1987Skill

    code-transfer

    Transfer code between files with line-based precision. Use when users request copying code from one location to another, moving functions or classes between files, extracting code blocks, or inserting code at specific line numbers.

    Also in 3 projects that use this

  • nek1987Skill

    timeline-creator

    Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.

    Also in 3 projects that use this

  • coffeefuelbumpSkill

    csv-data-summarizer

    Analyzes CSV files, generates summary stats, and plots quick visualizations using Python and pandas.

    Also in 3 projects that use this

  • ArogyaReddySkill

    changelog-generator

    Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

    Also in 4 projects that use this

  • LangChainSkill

    file-organizer

    Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.

    Also in 3 projects that use this

  • GoogleSkill

    algorithmic-art

    Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.

    Also in 4 projects that use this

  • +1 more from nek1987

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    All four tools use the operator-selected execution profile.

    line 14
  2. Distinctive:

    Use this skill to actually run things: compile a program, execute a script, test code someone shares with you, check what a command …

    line 22
  3. Very specific:

    When a language or binary is missing from PATH, say so plainly and name what you checked (which <name>).

    line 46

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “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

All four tools use the operator-selected execution profile. Do not ask for or invent a backend argument—the public tool schemas stay stable. If a result says the selected SSH or remote-Docker profile is unavailable, report its exact recovery step; never retry by assuming local placement. run_script requires the same workspace-relative file to exist on the remote target. Remote execute_code persists picklable session variables, reports unpicklable names, and cannot call the local tool_use bridge; call that tool directly instead.

Use this skill to actually run things: compile a program, execute a script, test code someone shares with you, check what a command outputs, or work with files. Running code is how claims about code become knowledge — a program that compiles and passes its tests teaches you more than any amount of reading it.

Choosing the tool

  1. safe_shell — one shell command with guarded defaults. The right first reach for compiling, running installed binaries, checking versions, and inspecting the environment (which, ls, language toolchains on PATH).
  2. execute_code — run a code snippet directly in a supported runtime without touching the filesystem.
  3. run_script — a saved multi-step script when the work has real structure.
  4. write_file + safe_shell — the classic loop for languages the runtime doesn't embed: write the source file, invoke its compiler or interpreter from the shell, read the output.

Practice

  • State what you ran and show the real output — including failures. A compile error is a finding, not an embarrassment.
  • Working files belong in the workspace directory; clean up what has no lasting value.
  • When a language or binary is missing from PATH, say so plainly and name what you checked (which <name>). Absence of a toolchain is a fact about the environment, never something to paper over with imagined output.
  • Long or destructive operations deserve a sentence of intent before you run them.

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