Awesome-omni-skill auxiliary-scripts
Auxiliary script management rules for Ralph agents
install
source · Clone the upstream repo
git clone https://github.com/diegosouzapw/awesome-omni-skill
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/cli-automation/auxiliary-scripts" ~/.claude/skills/diegosouzapw-awesome-omni-skill-auxiliary-scripts && rm -rf "$T"
manifest:
skills/cli-automation/auxiliary-scripts/SKILL.mdsource content
Auxiliary Script Management
"Auxiliary scripts in
help with automation and cleanup.".claude/session/
Script Classification
Scripts created in
.claude/session/ are automatically classified:
| Classification | Pattern | Retention |
|---|---|---|
| Temporary | , , , , | Auto-deleted after 1 hour |
| Reusable | Documented below | Persist across sessions |
| Unknown | Everything else | Manual cleanup required |
Temporary Scripts
Auto-cleaned after 1 hour:
- Agent runner scripts*-runner.ps1
- Message delivery filespending-messages-*.json
- Agent exit status files*.exit
- Restart signal filesrestart-flag-*.json
- Temporary files*.tmp
Do NOT rely on these persisting. They will be automatically deleted.
Creating Reusable Scripts
If you create a helper script that provides value across multiple sessions:
- Document it in the "Reusable Scripts" section of your AGENT.md
- Use descriptive naming:
{agent}-{purpose}.ps1 - Add to
inAuxiliaryScripts.Reusableralph-config.ps1 - Explain its purpose so future sessions understand its value
Reusable Scripts Template
# Script: {AGENT}-{PURPOSE}.ps1 # Purpose: {Brief description} # Created: {DATE} # Used by: {Which agents use this} param( [Parameter(Mandatory=$false)] [string]$SomeParameter ) # Script logic here
Adding to ralph-config.ps1
$Script:AuxiliaryScripts.Reusable = @{ "{AGENT}-{PURPOSE}.ps1" = @{ Purpose = "Brief description" Created = "2026-01-19" UsedBy = @("pm", "developer") } }
Documentation in AGENT.md
Maintain a "Reusable Scripts" section in your AGENT.md:
| Script | Purpose | Usage |
|---|---|---|
| (none yet) |
Update this table when creating new reusable scripts.
Cleanup Guidelines
When Deleting Scripts
- Check if active - ensure no agent is currently using it
- Check dependencies - ensure no other scripts depend on it
- Document removal - add note to progress file if significant
When Keeping Scripts
- Document purpose - add comment header explaining what it does
- Date stamp - include creation date
- Version - if modified, track version changes
Common Script Patterns
Message Delivery Script
# Used by watchdog to deliver messages to agents param([string]$TargetAgent, [string]$MessagePath) $message = Get-Content $MessagePath | ConvertFrom-Json $inbox = ".claude/session/messages/$TargetAgent/" Copy-Item $MessagePath "$inbox/$([Guid]::NewGuid()).json"
Health Check Script
# Used to check if agent is responsive param([string]$AgentName) $heartbeatFile = ".claude/session/coordinator-state.json" $state = Get-Content $heartbeatFile | ConvertFrom-Json $lastSeen = [DateTime]::Parse($state.agents.$AgentName.lastSeen) $age = (Get-Date) - $lastSeen if ($age.TotalSeconds -gt 60) { Write-Warning "Agent $AgentName unresponsive for $($age.TotalSeconds)s" return $false } return $true
Script Permissions
- All scripts in
should be executable by agents.claude/session/ - Never create scripts that modify source code without explicit task assignment
- Scripts should only update session files or state files
Reference
- file-permissions.md — What agents can write to
- context-management.md — Context reset procedures