Skill by ara.so — Daily 2026 Skills collection.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionwitr-process-inspectorExecute the skills CLI command in your project's root directory to begin installation:
Fetches witr-process-inspector from aradotso/trending-skills 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 witr-process-inspector. Access via /witr-process-inspector 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
22
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
22
stars
Skill by ara.so — Daily 2026 Skills collection.
witr is a Go CLI/TUI tool that answers "why is this running?" for any process, service, or port. Instead of leaving you to correlate ps, lsof, ss, systemctl, and docker ps manually, witr makes the causality chain explicit — showing where a running thing came from, how it was started, and what chain of supervisors/containers/shells is responsible.
curl -fsSL https://raw.githubusercontent.com/pranshuparmar/witr/main/install.sh | bash
irm https://raw.githubusercontent.com/pranshuparmar/witr/main/install.ps1 | iex
# Homebrew (macOS/Linux)
brew install witr
# Conda
conda install -c conda-forge witr
# Arch Linux (AUR)
yay -S witr-bin
# Windows winget
winget install -e --id PranshuParmar.witr
# Windows Scoop
scoop install main/witr
# Alpine / apk
sudo apk add --allow-untrusted ./witr-*.apk
# Go source install
go install github.com/pranshuparmar/witr/cmd/witr@latest
# Inspect a process by PID
witr <pid>
# Inspect by process name (substring match)
witr <name>
# Inspect what's bound to a port
witr --port <port>
witr -p <port>
# Launch interactive TUI dashboard
witr --interactive
witr -i
# Show all running processes with causality info
witr --all
witr -a
# Output as JSON (for scripting)
witr --json <pid>
# Follow/watch mode — refresh automatically
witr --watch <pid>
witr -w <pid>
# Verbose output — show full environment and metadata
witr --verbose <pid>
witr -v <pid>
# Filter processes by user
witr --user <username>
# Show version
witr --version
| Flag | Short | Description |
|---|---|---|
--port |
-p |
Inspect by port number |
--interactive |
-i |
Launch TUI dashboard |
--all |
-a |
Show all processes |
--json |
Output as JSON | |
--watch |
-w |
Auto-refresh/follow |
--verbose |
-v |
Full metadata output |
--user |
Filter by OS user | |
--version |
Print version |
Launch the full dashboard:
witr -i
# or
witr --interactive
TUI Keybindings:
| Key | Action |
|---|---|
↑ / ↓ |
Navigate process list |
Enter |
Expand process detail / causality chain |
f |
Filter/search processes |
s |
Sort by column |
r |
Refresh |
j |
Toggle JSON view |
q / Ctrl+C |
Quit |
witr 1234
PID: 1234
Name: node
Binary: /usr/local/bin/node
Started: 2026-03-18 09:12:44
User: ubuntu
Why is this running?
└─ Started by: npm (PID 1200)
└─ Started by: bash (PID 1180)
└─ Started by: sshd (PID 980)
└─ Started by: systemd (PID 1) [service: sshd.service]
witr --port 8080
Port: 8080 (TCP, LISTEN)
Process: python3 (PID 4512)
Binary: /usr/bin/python3
User: deploy
Why is this running?
└─ Started by: gunicorn (PID 4490)
└─ Started by: systemd (PID 1) [service: myapp.service]
Unit file: /etc/systemd/system/myapp.service
ExecStart: /usr/bin/gunicorn app:app --bind 0.0.0.0:8080
witr --json 4512
{
"pid": 4512,
"name": "python3",
"binary": "/usr/bin/python3",
"user": "deploy",
"started_at": "2026-03-18T09:00:00Z",
"causality_chain": [
{"pid": 4490, "name": "gunicorn", "type": "parent"},
{"pid": 1, "name": "systemd", "type": "supervisor", "service": "myapp.service"}
]
}
# Refresh every 2 seconds
witr --watch 4512
# Quick check: who owns port 5432 (Postgres)?
witr --port 5432
# Get machine-readable output for automation
witr --json --port 5432 | jq '.causality_chain[-1].service'
# List everything with causality, pipe to less
witr --all | less
# Export full audit to JSON
witr --all --json > audit.json
# witr understands container boundaries
witr <pid-of-containerized-process>
# Output will show: container → container runtime → systemd chain
#!/usr/bin/env bash
# Check if port 8080 is in use and why
if witr --json --port 8080 > /tmp/witr_out.json 2>/dev/null; then
SERVICE=$(jq -r '.causality_chain[-1].service // "unknown"' /tmp/witr_out.json)
echo "Port 8080 is owned by service: $SERVICE"
else
echo "Port 8080 is not in use"
fi
# Show only processes owned by www-data and why they're running
witr --all --user www-data
| Platform | Architectures | Notes |
|---|---|---|
| Linux | amd64, arm64 | Full support |
| macOS | amd64, arm64 (Apple Silicon) | Full support |
| Windows | amd64 | Full support |
| FreeBSD | amd64, arm64 | Full support |
If you want to use witr programmatically in a Go project:
go get github.com/pranshuparmar/witr
package main
import (
"fmt"
"github.com/pranshuparmar/witr/pkg/inspector"
)
func main() {
// Inspect a process by PID
result, err := inspector.InspectPID(1234)
if err != nil {
panic(err)
}
fmt.Printf("Process: %s\n", result.Name)
for _, link := range result.CausalityChain {
fmt.Printf(" └─ %s (PID %d)\n", link.Name, link.PID)
}
}
// Inspect by port
result, err := inspector.InspectPort(8080, "tcp")
if err != nil {
panic(err)
}
fmt.Printf("Port 8080 owned by PID %d (%s)\n", result.PID, result.Name)
# witr needs read access to /proc (Linux) or equivalent
# Run with sudo for system-level processes
sudo witr <pid>
sudo witr --port 80
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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
I recommend witr-process-inspector for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
witr-process-inspector fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added witr-process-inspector from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in witr-process-inspector — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
witr-process-inspector is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: witr-process-inspector is focused, and the summary matches what you get after install.
witr-process-inspector is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: witr-process-inspector is the kind of skill you can hand to a new teammate without a long onboarding doc.
witr-process-inspector has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in witr-process-inspector — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 25