verified-script-execution
Fallback workflow for reliable file creation and verification when automated code execution fails
- License 许可
- MIT
- 所属仓库
- HKUDS/AgentPilot
- 最近更新
- 2026-11-12
- Stars
- ★ 8.0k
- Forks
- 944
01 前言 Front Matter
- name
- verified-script-execution
- description
- Fallback workflow for reliable file creation and verification when automated code execution fails
02 资源文件 1
- 其他.skill_id39 B
03 SKILL.md 正文
Verified Script Execution Workflow
When execute_code_sandbox or shell_agent fails repeatedly, use this manual fallback pattern to reliably create and verify files through explicit shell commands.
When to Activate This Pattern
- After 3+ consecutive failures with
execute_code_sandbox - When
shell_agentproduces repeated errors without progress - For critical deliverables (PDFs, Word docs, reports) that must be created reliably
- When working directory confusion causes file creation failures
Step 1: Verify Working Directory
Always confirm your current location before creating any files:
pwd
ls -la
This ensures you're writing to the correct workspace directory and reveals any existing files that might conflict.
Step 2: Create Scripts via Heredoc
Use shell heredoc syntax to create scripts with proper escaping. Choose the heredoc delimiter style based on your needs:
For literal content (no variable expansion):
cat > script_name.sh << 'EOF'
#!/bin/bash
# Your script content here
# Variables like $VAR will NOT be expanded
echo "Literal text with $symbols"
EOF
For content requiring variable expansion:
cat > script_name.sh << EOF
#!/bin/bash
OUTPUT_DIR="$PWD/output"
# Variables WILL be expanded
echo "Working in $OUTPUT_DIR"
EOF
Key escaping rules:
- Use
<< 'EOF'(quoted delimiter) to prevent variable expansion and command substitution - Use
<< EOF(unquoted delimiter) when you need shell variables expanded - Escape single quotes inside quoted heredoc as
'\'' - For nested heredocs, use different delimiters (e.g.,
EOFandINNER)
Step 3: Make Executable and Run with Explicit Path
chmod +x script_name.sh
./script_name.sh
Or use the explicit full path for certainty:
bash /full/path/to/script_name.sh
Step 4: Verify Output
Always verify file creation and inspect content:
# Check file exists and see size
ls -lh expected_output.pdf
ls -lh expected_output.docx
# For PDFs, verify structure and page count
pdfinfo expected_output.pdf
# For Word docs, inspect internal structure
unzip -l expected_output.docx | head -20
Complete Example: PDF and Word Document Generation
# Step 1: Verify directory
pwd
ls -la
# Step 2: Create document generation script
cat > generate_deliverables.sh << 'EOF'
#!/bin/bash
set -e
# Create PDF checklist
cat > checklist_content.txt << 'CONTENT'
Safety Checklist
================
Page 1: Overview
Page 2: Requirements
Page 3: Verification Steps
Page 4: Sign-off
CONTENT
# Create Word action tracker
cat > tracker_content.txt << 'CONTENT'
Action Tracker
==============
Item,Owner,Due,Status
Task 1,Team A,2024-01-15,Pending
Task 2,Team B,2024-01-20,In Progress
CONTENT
# Convert to target formats (adapt to available tools)
echo "Files created in: $(pwd)"
ls -lh *.txt
EOF
# Step 3: Execute with explicit path
chmod +x generate_deliverables.sh
./generate_deliverables.sh
# Step 4: Verify all outputs
ls -lh checklist_content.txt tracker_content.txt
# For PDFs: pdfinfo output.pdf
# For DOCX: unzip -l output.docx | head -20
Efficiency Tips
- Combine related operations in a single script to reduce iteration count
- Verify incrementally - check each file before proceeding to the next step
- Use explicit paths throughout to avoid directory confusion
- Test heredoc syntax in isolation before building complex nested scripts
- Document expected outputs (filenames, sizes, page counts) before running
- Use
set -ein scripts to fail fast on errors
Common Pitfalls to Avoid
- Unquoted heredoc delimiters when you need literal
$symbols - Missing
chmod +xbefore script execution - Not verifying output before assuming success
- Nested heredocs with same delimiter causing premature termination
- Assuming current directory without explicit
pwdverification
Migration Back to Automated Tools
Once files are created successfully with this pattern:
- Study what worked in the manual script
- Translate the working approach back to
execute_code_sandboxformat - Test incrementally with smaller code blocks
- Revert to automated tools for subsequent iterations
This pattern prioritizes reliability over iteration efficiency, ensuring deliverables are created correctly even when automated tools struggle.
04 同仓库更多 Skills
agentpilot
Set up AgentPilot and use its single entry to prepare missing inputs and run configured RSI experiments. Use when the user requests AgentPilot installation or work with AgentPilot.
remember
Review auto-memory entries and propose promotions to OPENSPACE.md, OPENSPACE.local.md, or retained auto-memory topics; detect duplicates, stale facts, conflicts, and ambiguous entries before making changes.
skill-discovery
Search reusable OpenSpace skills locally, and browse cloud packages step by step when a cloud skill may help. Reusing proven skills saves tokens, improves reliability, and extends your capabilities beyond built-in tools.
delegate-task
Delegate tasks to OpenSpace — a full-stack autonomous worker for coding, DevOps, web research, and desktop automation, backed by an extensive MCP tool and skill library. Skills auto-improve through use, reducing token consumption over time. A cloud community lets agents share and collectively evolve reusable skills.
write-special-chars-ts-check
Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, plus a reliable TypeScript type-checking step that filters output to only the newly-written files to avoid being misled by pre-existing errors.
write-special-chars-readback
Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, with mandatory post-write verification via read_file and cleanup of /tmp helper scripts.