Install
$ agentstack add skill-hkuds-openspace-fallback-file-creation ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Fallback File Creation Workflow
Use this skill when execute_code_sandbox or shell_agent fails repeatedly for file creation tasks. This pattern provides a manual but reliable approach to create and verify files.
When to Use
- Code execution tools fail after multiple retries
- You need to create specific file formats (PDF, DOCX, etc.)
- Direct shell commands are more reliable than generated scripts
- You need explicit verification of file outputs
Step-by-Step Instructions
Step 1: Verify Working Directory
Before any file operations, confirm your current location:
pwd
ls -la
This ensures you're creating files in the correct workspace directory.
Step 2: Create Scripts via Heredoc
Use shell heredocs to create scripts with properly escaped syntax:
cat > /path/to/script.sh /workspace/create_pdf.sh /workspace/create_docx.sh << 'EOF'
#!/bin/bash
cd /workspace
pandoc -f markdown -t docx action_tracker.md -o action_tracker.docx
EOF
# Step 3: Execute
chmod +x /workspace/create_docx.sh
/workspace/create_docx.sh
# Step 4: Verify
ls -lh /workspace/action_tracker.docx
unzip -l /workspace/action_tracker.docx | head -20
Best Practices
- Always verify before and after - Check directory state before starting and after completion
- Use absolute or explicit paths - Avoid ambiguity in file locations
- Quote heredoc delimiters - Use
'EOF'to prevent unwanted variable expansion - Make scripts executable - Always
chmod +xbefore running - Inspect file metadata - Use format-specific tools (pdfinfo, unzip -l, file) to verify content
- Keep scripts simple - Each script should do one thing well
- Clean up temporary files - Remove intermediate files after successful completion
Troubleshooting
| Issue | Solution | |-------|----------| | Script not found | Use full path: /workspace/script.sh | | Permission denied | Run chmod +x script.sh | | File not created | Check script output, verify working directory in script | | Wrong file format | Verify conversion tool supports target format | | Corrupted output | Re-run with verbose mode, check intermediate files |
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: HKUDS
- Source: HKUDS/OpenSpace
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.