Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Safely write or update large files over 5000 bytes by reading, incrementally editing small sections, verifying each change, and using fallback recovery methods.
Safely write or update large files over 5000 bytes by reading, incrementally editing small sections, verifying each change, and using fallback recovery methods.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Safe file writing strategy for large files to avoid truncation issues.
Writing files larger than 5000 bytes Updating existing files with significant changes Modifying specific sections of large files Previous write operations were truncated Need to ensure file integrity
Large file writes can fail due to: Tool limitations - write tool may have byte limits per operation Network limits - Large file transfers may be truncated during transmission System limits - OpenClaw may have size limits on single operations
OperationSafe SizeRisk Levelwrite new file< 2000 bytesโ Safewrite new file2000-5000 bytesโ ๏ธ Moderatewrite new file> 5000 bytesโ High riskedit modification< 500 bytesโ Safeedit modification500-1000 bytesโ ๏ธ Moderateedit modification> 1000 bytesโ High risk
Before making changes, read the current file state: # Read the file to understand current structure read /path/to/file.md # For large files, read specific sections read /path/to/file.md --offset 100 --limit 50 Purpose: Understand file structure Identify exact text to replace `- Determine modification points
After each modification, verify the result: # Check file line count wc -l /path/to/file.md # Read modified section read /path/to/file.md --offset <start> --limit <lines> # Verify file ends correctly read /path/to/file.md --offset -10 Success Criteria: File size increased as expected Modified section contains new content File ends correctly (not truncated) No syntax errors (for code files)
For large multi-section updates: Modify one section at a time Verify each modification Proceed to next section Repeat until all changes complete
If write tool fails for large content: Split content into chunks: 1. Write first chunk (header + section 1) 2. Verify and append section 2 3. Verify and append section 3 4. Continue until complete
For complex modifications, use unique markers: In source file: <!-- SECTION_START: configuration --> [existing content] <!-- SECTION_END: configuration --> Edit operation: oldText: "<!-- SECTION_START: configuration -->\n[existing content]\n<!-- SECTION_END: configuration -->" newText: "<!-- SECTION_START: configuration -->\n[new content]\n<!-- SECTION_END: configuration -->"
For creating new large files: 1. Create file with basic structure 2. Add sections one by one using edit 3. Verify after each addition 4. Final verification
For critical file modifications: # Create backup before modification cp /path/to/file.md /path/to/file.md.backup # Attempt modification # ... (write or edit operation) # If modification fails, restore cp /path/to/file.md.backup /path/to/file.md
Symptom: "Could not find exact text in file" Causes: oldText doesn't match exactly Whitespace differences (spaces vs tabs) File already modified Text doesn't exist in file Solutions: Re-read the file to get exact content Use unique markers for large sections Match whitespace exactly (copy from file read) Use smaller oldText for more precise matching
Symptom: File ends abruptly or is incomplete Solutions: Use edit tool instead of write Split content into smaller chunks Write incrementally (section by section) Verify file size after each operation
Symptom: File has syntax errors or invalid content Solutions: Restore from backup Re-read and re-verify Use incremental build strategy Validate syntax after each modification
Step 1: Read file to find insertion point read /path/to/large-file.md --offset 50 --limit 10 Step 2: Use edit to add new section edit: file_path: /path/to/large-file.md oldText: "## Existing Section\n\nContent here" newText: "## Existing Section\n\nContent here\n\n## New Section\n\nNew content" Step 3: Verify read /path/to/large-file.md --offset 50 --limit 20
Step 1: Create basic structure write: file_path: /path/to/new-file.md content: "# Title\n\n## Section 1\n\nContent 1" Step 2: Add sections incrementally edit: file_path: /path/to/new-file.md oldText: "Content 1" newText: "Content 1\n\n## Section 2\n\nContent 2" Step 3: Verify wc -l /path/to/new-file.md
Step 1: Read file to find exact text read /path/to/file.md Step 2: Use unique markers edit: file_path: /path/to/file.md oldText: "<!-- START: old-section -->\n[old content]\n<!-- END: old-section -->" newText: "<!-- START: old-section -->\n[new content]\n<!-- END: old-section -->" Step 3: Verify read /path/to/file.md | grep "new content"
Always read before editing - Understand current state Use edit for modifications - More precise than write Keep changes small - Under 500 bytes per edit Verify after each operation - Don't batch operations Use unique markers - For complex modifications Create backups - For critical files Handle errors gracefully - Provide recovery strategies Test incrementally - Verify each step
Need to write/update file? โโ New file? โ โโ < 2000 bytes? โ โ โโ Use write tool โ โโ > 2000 bytes? โ โโ Use incremental build strategy โโ Existing file? โโ Small change (< 500 bytes)? โ โโ Use edit tool โโ Medium change (500-1000 bytes)? โ โโ Use edit with unique markers โโ Large change (> 1000 bytes)? โโ Use incremental edit strategy
TaskToolStrategyCreate small filewriteDirect writeCreate large filewrite + editIncremental buildSmall modificationeditDirect editMedium modificationeditEdit with markersLarge modificationeditIncremental editReplace sectioneditUnique markersAppend contenteditEdit end of file
Writing, remixing, publishing, visual generation, and marketing content production.
Largest current source with strong distribution and engagement signals.