Convert Bash commands with complex expansions into temporary script files.
npx skills add https://github.com/cowwoc/styler --skill bash-to-script
Please help me install this Agent Skill. Skill: bash-to-script Source: https://github.com/cowwoc/styler/tree/main/.claude/skills/bash-to-script Command: npx skills add https://github.com/cowwoc/styler --skill bash-to-script
The Bash tool can struggle with complex syntax like parameter expansion (${VAR##pattern}) or nested command substitutions, leading to cryptic parse errors. This Skill provides a reliable workaround by converting such commands into temporary script files, ensuring smooth execution.
jq pipelines, and multiple nested expansions.cat > /tmp/script.sh << 'EOF' ... EOF; bash /tmp/script.sh structure.set -euo pipefail and trap for robust execution.(eval):1: parse error near '(' when trying to extract an agent ID using a complex jq pipeline and parameter expansion, use this Skill to convert the command into a temporary script, allowing it to execute successfully without manual debugging.If a bash command fails with a parse error, use this skill: Skill: bash-to-script Command: | SESSION_ID="abc-123" AGENT_ID=$(jq -r 'select(.toolUseResult.agentId)' /path/${SESSION_ID}.jsonl | tail -1) echo "$AGENT_ID" > output.txt
High-intent search queries and answers about installing and using this skill.
Bash parse errors from parameter expansion like ${VAR##pattern} or nested command substitutions occur when the Bash tool struggles with complex syntax. Convert the problematic command into a temporary script file using heredoc syntax—this encapsulates the command safely and executes it via bash, eliminating parse failures.
Convert to script format when you encounter parse errors with parameter expansion, complex jq pipelines, multiple nested expansions, or unreliable execution in the Bash tool. Script encapsulation isolates syntax issues and ensures repeatable, robust execution without manual debugging.
Yes. The conversion supports error handling templates with set -euo pipefail and trap statements, enabling robust execution with graceful failure handling. These additions ensure scripts catch and respond to errors reliably.
Parameter removal patterns (${VAR##pattern}, ${VAR%%pattern}), complex jq command pipelines, and nested variable expansions frequently trigger parse errors in Bash tools. Converting these patterns into script files prevents tool-level syntax failures and enables reliable automation.
Automate by converting syntax-problematic bash commands into temporary script files with heredoc wrapping, then executing via bash. This approach standardizes execution, eliminates parse failures, and creates repeatable, debuggable automation workflows.
Direct Bash tool execution can fail on complex syntax; script conversion wraps the command in a temporary file and executes it, bypassing tool-level parsing constraints. This approach trades direct invocation for reliability, especially with parameter expansion and nested substitutions.
gekko68Execute Bash commands with validation, dry-run previews, and timeout protection.
theslashdojoExecute Bash commands and capture stdout/stderr with timeout and directory control.
ovachieverApply defensive Bash patterns with strict mode and error trapping.
JitsusamaFormat Git CLI commands with heredoc syntax and shell quoting rules for scripts.