ports

Data Community

Skill notes

Port Ranges

47100: Daemon API 47101-47199: Plugin instances 47200: Standalone plugin dev (npm run dt dev plugin <name>)

Output

Show a table of: Port number Process name PID What it likely is (daemon, plugin instance, standalone dev)

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Data
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@majiayu000 · MIT
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js
Detected file/system behavior
  • Read-only
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# Shella Port Check

Show what processes are using ports in the shella range.

## Port Ranges

- **47100**: Daemon API
- **47101-47199**: Plugin instances
- **47200**: Standalone plugin dev (`npm run dt dev plugin <name>`)

## Command

```bash
lsof -i :47100-47200 -P -n 2>/dev/null | grep LISTEN
```

## Output

Show a table of:
- Port number
- Process name
- PID
- What it likely is (daemon, plugin instance, standalone dev)

If nothing is listening, say so.

If there are unexpected processes (not node), flag them as potential conflicts.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.