Essential patterns for Bash on Linux/macOS.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionbash-linuxExecute the skills CLI command in your project's root directory to begin installation:
Fetches bash-linux from davila7/claude-code-templates and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate bash-linux. Access via /bash-linux in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
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
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
24.2K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
24.2K
stars
Essential patterns for Bash on Linux/macOS.
| 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" |
| 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 |
| 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 |
| 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 |
| 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" |
| 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 |
#!/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 "$@"
if command -v node &> /dev/null; then
echo "Node is installed"
fi
NAME=${1:-"default_value"}
while IFS= read -r line; do
echo "$line"
done < file.txt
for file in *.js; do
echo "Processing $file"
done
| 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 |
set -e # Exit on error
set -u # Exit on undefined variable
set -o pipefail # Exit on pipe failure
set -x # Debug: print commands
cleanup() {
echo "Cleaning up..."
rm -f /tmp/tempfile
}
trap cleanup EXIT
Remember: Bash is text-based. Use
&&for success chains,set -efor safety, and quote your variables!
Make data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
davila7/claude-code-templates
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
bash-linux has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added bash-linux from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for bash-linux matched our evaluation — installs cleanly and behaves as described in the markdown.
We added bash-linux from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
bash-linux fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added bash-linux from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
bash-linux reduced setup friction for our internal harness; good balance of opinion and flexibility.
bash-linux fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
bash-linux fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
bash-linux is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 48