bash-linux

sickn33/antigravity-awesome-skills · updated May 9, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill bash-linux
0 commentsdiscussion
summary

Essential Bash/Linux terminal patterns for command chaining, file operations, process management, and scripting.

  • Covers operator syntax ( ; , && , || , | ), file operations ( ls , find , grep , tail ), and process management ( ps , kill , lsof )
  • Includes text processing tools ( grep , sed , awk , cut , sort ) and network commands ( curl , nc , ifconfig )
  • Provides script templates with error handling ( set -e , set -u , set -o pipefail ) and cleanup patterns using trap
  • In
skill.md

Bash Linux Patterns

Essential patterns for Bash on Linux/macOS.


1. Operator Syntax

Chaining Commands

Operator Meaning Example
; Run sequentially cmd1; cmd2
&& Run if previous succeeded npm install && npm run dev
|| Run if previous failed npm test || echo "Tests failed"
| Pipe output ls | grep ".js"

2. File Operations

Essential Commands

Task Command
List all ls -la
Find files find . -name "*.js" -type f
File content cat file.txt
First N lines head -n 20 file.txt
Last N lines tail -n 20 file.txt
Follow log tail -f log.txt
Search in files grep -r "pattern" --include="*.js"
File size du -sh *
Disk usage df -h

3. Process Management

Task Command
List processes ps aux
Find by name ps aux | grep node
Kill by PID kill -9 <PID>
Find port user lsof -i :3000
Kill port kill -9 $(lsof -t -i :3000)
Background npm run dev &
Jobs jobs -l
Bring to front fg %1

4. Text Processing

Core Tools

Tool Purpose Example
grep Search grep -rn "TODO" src/
sed Replace sed -i 's/old/new/g' file.txt
awk Extract columns awk '{print $1}' file.txt
cut Cut fields cut -d',' -f1 data.csv
sort Sort lines sort -u file.txt
uniq Unique lines sort file.txt | uniq -c
wc Count wc -l file.txt

5. Environment Variables

Task Command
View all env or printenv
View one echo $PATH
Set temporary export VAR="value"
Set in script VAR="value" command
Add to PATH export PATH="$PATH:/new/path"

6. Network

Task Command
Download curl -O https://example.com/file
API request curl -X GET https://api.example.com
POST JSON curl -X POST -H "Content-Type: application/json" -d '{"key":"value"}' URL
Check port nc -zv localhost 3000
Network info ifconfig or ip addr

7. Script Template

#!/bin/bash
set -euo pipefail  # Exit on error, undefined var, pipe fail

# Colors (optional)
RED='\033[0;31m'
GREEN='\033[0;32m'
NC='\033[0m'

# Script directory
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"

# Functions
log_info() { echo -e "${GREEN}[INFO]${NC} $1"; }
log_error() { echo -e "${RED}[ERROR]${NC} $1" >&2; }

# Main
main() {
    log_info "Starting..."
    # Your logic here
    log_info "Done!"
}

main "$@"

8. Common Patterns

Check if command exists

if command -v node &> /dev/null; then
    echo "Node is installed"
fi

Default variable value

NAME=${1:-"default_value"}

Read file line by line

while IFS= read -r line; do
    echo "$line"
done < file.txt

Loop over files

for file in *.js; do
    echo "Processing $file"
done

9. Differences from PowerShell

Task PowerShell Bash
List files Get-ChildItem ls -la
Find files Get-ChildItem -Recurse find . -type f
Environment $env:VAR $VAR
String concat "$a$b" "$a$b" (same)
Null check if ($x) if [ -n "$x" ]
Pipeline Object-based Text-based

10. Error Handling

Set options

set -e          # Exit on error
set -u          # Exit on undefined variable
set -o pipefail # Exit on pipe failure
set -x          # Debug: print commands

Trap for cleanup

cleanup() {
    echo "Cleaning up..."
    rm -f /tmp/tempfile
}
trap cleanup EXIT

Remember: Bash is text-based. Use && for success chains, set -e for safety, and quote your variables!

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

how to use bash-linux

How to use bash-linux on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add bash-linux
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill bash-linux

The skills CLI fetches bash-linux from GitHub repository sickn33/antigravity-awesome-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/bash-linux

Reload or restart Cursor to activate bash-linux. Access the skill through slash commands (e.g., /bash-linux) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.543 reviews
  • Advait Anderson· Dec 24, 2024

    Useful defaults in bash-linux — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Sophia Abebe· Dec 20, 2024

    Solid pick for teams standardizing on skills: bash-linux is focused, and the summary matches what you get after install.

  • Ganesh Mohane· Dec 16, 2024

    I recommend bash-linux for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Xiao Sethi· Nov 15, 2024

    bash-linux is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Sophia Yang· Nov 11, 2024

    bash-linux has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Rahul Santra· Nov 7, 2024

    bash-linux fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Pratham Ware· Oct 26, 2024

    bash-linux has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Aditi Torres· Oct 6, 2024

    bash-linux reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Sophia Martin· Oct 2, 2024

    bash-linux fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Hana Reddy· Sep 25, 2024

    Solid pick for teams standardizing on skills: bash-linux is focused, and the summary matches what you get after install.

showing 1-10 of 43

1 / 5