code-execution
Runs local Python scripts to perform metadata analysis and batch transformations on files while minimizing token consumption.
Install
mkdir -p .claude/skills/code-execution && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5789" && unzip -o skill.zip -d .claude/skills/code-execution && rm skill.zipInstalls to .claude/skills/code-execution
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Execute Python code locally with marketplace API access for 90%+ token savings on bulk operations. Activates when user requests bulk operations (10+ files), complex multi-step workflows, iterative processing, or mentions efficiency/performance.Key capabilities
- →Perform bulk file operations
- →Analyze code metadata
- →Execute batch refactoring
- →Manage Git operations
- →Reduce token consumption
How it works
It executes Python code locally to perform transformations and analysis on files, returning only metadata or summaries to the agent to minimize token usage.
Inputs & outputs
When to use code-execution
- →Bulk refactoring across 10+ files
- →Complex multi-step code transformations
- →Automated code cleanup
About this skill
Code Execution
Execute Python locally with API access. 90-99% token savings for bulk operations.
When to Use
- Bulk operations (10+ files)
- Complex multi-step workflows
- Iterative processing across many files
- User mentions efficiency/performance
How to Use
Use direct Python imports in Claude Code:
from execution_runtime import fs, code, transform, git
# Code analysis (metadata only!)
functions = code.find_functions('app.py', pattern='handle_.*')
# File operations
code_block = fs.copy_lines('source.py', 10, 20)
fs.paste_code('target.py', 50, code_block)
# Bulk transformations
result = transform.rename_identifier('.', 'oldName', 'newName', '**/*.py')
# Git operations
git.git_add(['.'])
git.git_commit('feat: refactor code')
If not installed: Run ~/.claude/plugins/marketplaces/mhattingpete-claude-skills/execution-runtime/setup.sh
Available APIs
- Filesystem (
fs): copy_lines, paste_code, search_replace, batch_copy - Code Analysis (
code): find_functions, find_classes, analyze_dependencies - returns METADATA only! - Transformations (
transform): rename_identifier, remove_debug_statements, batch_refactor - Git (
git): git_status, git_add, git_commit, git_push
Pattern
- Analyze locally (metadata only, not source)
- Process locally (all operations in execution)
- Return summary (not data!)
Examples
Bulk refactor (50 files):
from execution_runtime import transform
result = transform.rename_identifier('.', 'oldName', 'newName', '**/*.py')
# Returns: {'files_modified': 50, 'total_replacements': 247}
Extract functions:
from execution_runtime import code, fs
functions = code.find_functions('app.py', pattern='.*_util$') # Metadata only!
for func in functions:
code_block = fs.copy_lines('app.py', func['start_line'], func['end_line'])
fs.paste_code('utils.py', -1, code_block)
result = {'functions_moved': len(functions)}
Code audit (100 files):
from execution_runtime import code
from pathlib import Path
files = list(Path('.').glob('**/*.py'))
issues = []
for file in files:
deps = code.analyze_dependencies(str(file)) # Metadata only!
if deps.get('complexity', 0) > 15:
issues.append({'file': str(file), 'complexity': deps['complexity']})
result = {'files_audited': len(files), 'high_complexity': len(issues)}
Best Practices
✅ Return summaries, not data ✅ Use code_analysis (returns metadata, not source) ✅ Batch operations ✅ Handle errors, return error count
❌ Don't return all code to context ❌ Don't read full source when you need metadata ❌ Don't process files one by one
Token Savings
| Files | Traditional | Execution | Savings |
|---|---|---|---|
| 10 | 5K tokens | 500 | 90% |
| 50 | 25K tokens | 600 | 97.6% |
| 100 | 150K tokens | 1K | 99.3% |
When not to use it
- →Small-scale operations where overhead exceeds benefits
Prerequisites
Limitations
- →Requires local runtime setup
- →Returns summaries rather than full data
How it compares
It processes files locally within a runtime environment rather than sending full source code to the LLM.
Compared to similar skills
code-execution side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| code-execution (this skill) | 1 | 9mo | No flags | Advanced |
| clojure-write | 16 | 2mo | No flags | Intermediate |
| add-uint-support | 18 | 9mo | No flags | Intermediate |
| python-patterns | 6 | 2mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by mhattingpete
View all by mhattingpete →You might also like
clojure-write
metabase
Guide Clojure and ClojureScript development using REPL-driven workflow, coding conventions, and best practices. Use when writing, developing, or refactoring Clojure/ClojureScript code.
add-uint-support
pytorch
Add unsigned integer (uint) type support to PyTorch operators by updating AT_DISPATCH macros. Use when adding support for uint16, uint32, uint64 types to operators, kernels, or when user mentions enabling unsigned types, barebones unsigned types, or uint support.
python-patterns
affaan-m
Pythonic 惯用法、PEP 8 标准、类型提示以及构建健壮、高效、可维护的 Python 应用程序的最佳实践。
modern-python
trailofbits
Configures Python projects with modern tooling (uv, ruff, ty). Use when creating projects, writing standalone scripts, or migrating from pip/Poetry/mypy/black.
massgen-develops-massgen
massgen
Guide for using MassGen to develop and improve itself. This skill should be used when agents need to run MassGen experiments programmatically (using automation mode) OR analyze terminal UI/UX quality (using visual evaluation tools). These are mutually exclusive workflows for different improvement goals.
migrate
alirezarezvani
Migrate from Cypress or Selenium to Playwright. Use when user mentions "cypress", "selenium", "migrate tests", "convert tests", "switch to playwright", "move from cypress", or "replace selenium".