OS/Shell Scripting Troubleshooting Workflow Bundle

Overview

This public intake copy packages

plugins/antigravity-awesome-skills-claude/skills/os-scripting

https://github.com/sickn33/antigravity-awesome-skills

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

ORIGIN.md

OS/Shell Scripting Troubleshooting Workflow Bundle

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Quality Gates, Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• Debugging shell script errors
• Creating production-ready bash scripts
• Troubleshooting system issues
• Automating system administration tasks
• Managing processes and services
• Configuring system resources

Operating Table

metadata.json

ORIGIN.md

SKILL.md

SKILL.md

## Related Skills

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. bash-linux - Linux bash patterns
2. bash-pro - Professional bash scripting
3. bash-defensive-patterns - Defensive scripting
4. Identify operating system and version
5. Check available tools and commands
6. Verify permissions and access
7. Assess system resources

Imported Workflow Notes

Imported: Workflow Phases

Phase 1: Environment Assessment

Skills to Invoke

• bash-linux

  - Linux bash patterns

• bash-pro

  - Professional bash scripting

• bash-defensive-patterns

  - Defensive scripting

Actions

1. Identify operating system and version
2. Check available tools and commands
3. Verify permissions and access
4. Assess system resources
5. Review logs and error messages

Diagnostic Commands

# System information
uname -a
cat /etc/os-release
hostnamectl

# Resource usage
top
htop
df -h
free -m

# Process information
ps aux
pgrep -f pattern
lsof -i :port

# Network status
netstat -tulpn
ss -tulpn
ip addr show

Copy-Paste Prompts

Use @bash-linux to diagnose system performance issues

Phase 2: Script Analysis

Skills to Invoke

• bash-defensive-patterns

  - Defensive scripting

• shellcheck-configuration

  - ShellCheck linting

• bats-testing-patterns

  - Bats testing

Actions

1. Run ShellCheck for linting
2. Analyze script structure
3. Identify potential issues
4. Check error handling
5. Verify variable usage

ShellCheck Usage

# Install ShellCheck
sudo apt install shellcheck  # Debian/Ubuntu
brew install shellcheck      # macOS

# Run ShellCheck
shellcheck script.sh
shellcheck -f gcc script.sh

# Fix common issues
# - Use quotes around variables
# - Check exit codes
# - Handle errors properly

Copy-Paste Prompts

Use @shellcheck-configuration to lint and fix shell scripts

Phase 3: Debugging

Skills to Invoke

• systematic-debugging

  - Systematic debugging

• debugger

  - Debugging specialist

• error-detective

  - Error pattern detection

Actions

1. Enable debug mode
2. Add logging statements
3. Trace execution flow
4. Isolate failing sections
5. Test components individually

Debug Techniques

# Enable debug mode
set -x  # Print commands
set -e  # Exit on error
set -u  # Exit on undefined variable
set -o pipefail  # Pipeline failure detection

# Add logging
log() {
    echo "[$(date '+%Y-%m-%d %H:%M:%S')] $*" >> /var/log/script.log
}

# Trap errors
trap 'echo "Error on line $LINENO"' ERR

# Test sections
bash -n script.sh  # Syntax check
bash -x script.sh  # Trace execution

Copy-Paste Prompts

Use @systematic-debugging to trace and fix shell script errors

Phase 4: Script Development

Skills to Invoke

• bash-pro

  - Professional scripting

• bash-defensive-patterns

  - Defensive patterns

• linux-shell-scripting

  - Shell scripting

Actions

1. Design script structure
2. Implement functions
3. Add error handling
4. Include input validation
5. Add help documentation

Script Template

#!/usr/bin/env bash
set -euo pipefail

# Constants
readonly SCRIPT_NAME=$(basename "$0")
readonly SCRIPT_DIR=$(cd "$(dirname "$0")" && pwd)

# Logging
log() {
    local level="$1"
    shift
    echo "[$(date '+%Y-%m-%d %H:%M:%S')] [$level] $*" >&2
}

info() { log "INFO" "$@"; }
warn() { log "WARN" "$@"; }
error() { log "ERROR" "$@"; exit 1; }

# Usage
usage() {
    cat <<EOF
Usage: $SCRIPT_NAME [OPTIONS]

Options:
    -h, --help      Show this help message
    -v, --verbose   Enable verbose output
    -d, --debug     Enable debug mode

Examples:
    $SCRIPT_NAME --verbose
    $SCRIPT_NAME -d
EOF
}

# Main function
main() {
    local verbose=false
    local debug=false

    while [[ $# -gt 0 ]]; do
        case "$1" in
            -h|--help)
                usage
                exit 0
                ;;
            -v|--verbose)
                verbose=true
                shift
                ;;
            -d|--debug)
                debug=true
                set -x
                shift
                ;;
            *)
                error "Unknown option: $1"
                ;;
        esac
    done

    info "Script started"
    # Your code here
    info "Script completed"
}

main "$@"

Copy-Paste Prompts

Use @bash-pro to create a production-ready backup script

Use @linux-shell-scripting to automate system maintenance tasks

Phase 5: Testing

Skills to Invoke

• bats-testing-patterns

  - Bats testing framework

• test-automator

  - Test automation

Actions

1. Write Bats tests
2. Test edge cases
3. Test error conditions
4. Verify expected outputs
5. Run test suite

Bats Test Example

#!/usr/bin/env bats

@test "script returns success" {
    run ./script.sh
    [ "$status" -eq 0 ]
}

@test "script handles missing arguments" {
    run ./script.sh
    [ "$status" -ne 0 ]
    [ "$output" == *"Usage:"* ]
}

@test "script creates expected output" {
    run ./script.sh --output test.txt
    [ -f "test.txt" ]
}

Copy-Paste Prompts

Use @bats-testing-patterns to write tests for shell scripts

Phase 6: System Troubleshooting

Skills to Invoke

• devops-troubleshooter

  - DevOps troubleshooting

• incident-responder

  - Incident response

• server-management

  - Server management

Actions

1. Identify symptoms
2. Check system logs
3. Analyze resource usage
4. Test connectivity
5. Verify configurations
6. Implement fixes

Troubleshooting Commands

# Check logs
journalctl -xe
tail -f /var/log/syslog
dmesg | tail

# Network troubleshooting
ping host
traceroute host
curl -v http://host
dig domain
nslookup domain

# Process troubleshooting
strace -p PID
lsof -p PID
iotop

# Disk troubleshooting
du -sh /*
find / -type f -size +100M
lsof | grep deleted

Copy-Paste Prompts

Use @devops-troubleshooter to diagnose server connectivity issues

Use @incident-responder to investigate system outage

Phase 7: Automation

Skills to Invoke

• workflow-automation

  - Workflow automation

• cicd-automation-workflow-automate

  - CI/CD automation

• linux-shell-scripting

  - Shell scripting

Actions

1. Identify automation opportunities
2. Design automation workflows
3. Implement scripts
4. Schedule with cron/systemd
5. Monitor automation health

Cron Examples

# Edit crontab
crontab -e

# Backup every day at 2 AM
0 2 * * * /path/to/backup.sh

# Clean logs weekly
0 3 * * 0 /path/to/cleanup.sh

# Monitor disk space hourly
0 * * * * /path/to/monitor.sh

Systemd Timer Example

# /etc/systemd/system/backup.timer
[Unit]
Description=Daily backup timer

[Timer]
OnCalendar=daily
Persistent=true

[Install]
WantedBy=timers.target

Copy-Paste Prompts

Use @workflow-automation to create automated system maintenance workflow

Imported: Related Workflow Bundles

• development

  - Software development

• cloud-devops

  - Cloud and DevOps

• security-audit

  - Security testing

• database

  - Database operations

Imported: Overview

Comprehensive workflow for operating system troubleshooting, shell scripting, and system administration across Linux, macOS, and Windows. This bundle orchestrates skills for debugging system issues, creating robust scripts, and automating administrative tasks.

Imported: Quality Gates

Before completing workflow, verify:

• All scripts pass ShellCheck
• Tests pass with Bats
• Error handling implemented
• Logging configured
• Documentation complete
• Automation scheduled

Examples

Example 1: Ask for the upstream workflow directly

Use @os-scripting to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @os-scripting against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @os-scripting for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @os-scripting using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
• Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
• Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
• Treat generated examples as scaffolding; adapt them to the concrete task before execution.
• Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

plugins/antigravity-awesome-skills-claude/skills/os-scripting

metadata.json

ORIGIN.md

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Imported Troubleshooting Notes

Imported: Common Troubleshooting Scenarios

High CPU Usage

top -bn1 | head -20
ps aux --sort=-%cpu | head -10
pidstat 1 5

Memory Issues

free -h
vmstat 1 10
cat /proc/meminfo

Disk Space

df -h
du -sh /* 2>/dev/null | sort -h
find / -type f -size +500M 2>/dev/null

Network Issues

ip addr show
ip route show
ss -tulpn
curl -v http://target

Service Failures

systemctl status service-name
journalctl -u service-name -f
systemctl restart service-name

Related Skills

• @00-andruia-consultant-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @10-andruia-skill-smith-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @20-andruia-niche-intelligence-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @2d-games

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

references

references/n/a

examples

examples/n/a

scripts

scripts/n/a

agents

agents/n/a

assets

assets/n/a

Imported Reference Notes

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.