PL

player-discovery-scan

Scans subnets for BrightSign media players and generates a local configuration file of discovered devices.

Install

mkdir -p .claude/skills/player-discovery-scan && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10304" && unzip -o skill.zip -d .claude/skills/player-discovery-scan && rm skill.zip

Installs to .claude/skills/player-discovery-scan

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Scan a local subnet to discover BrightSign players via DWS fingerprinting and update .brightsign/players.json. Use when asked to find players on a LAN or scan a CIDR range.
172 chars✓ has a “when” trigger
Beginner

Key capabilities

  • Scan local subnet
  • Discover BrightSign players
  • Update players.json
  • Report findings

How it works

It uses DWS fingerprinting to detect players and writes results to a JSON file.

Inputs & outputs

You give it
Network range
You get back
Updated players.json file

When to use player-discovery-scan

  • Scan local network for BrightSign players
  • Update player configuration file
  • Debug connectivity to specific players
  • Discover players on a non-local CIDR range

About this skill

Player Discovery Scan

Purpose

Discover BrightSign players on the local network via DWS fingerprinting and write results to .brightsign/players.json.

Safety and boundaries

  • Without --cidr, the tool auto-detects local private subnets (safe).
  • With --cidr, only the user-provided range is scanned.
  • .brightsign/players.json is gitignored — never commit it.
  • Prefer --host <ip> before scanning a full subnet when debugging.

Workflow

  1. If the user provides a CIDR, use it. Otherwise auto-detect.
  2. Run the discover command.
  3. Report the number of players found.
  4. Confirm .brightsign/players.json was updated.

Commands to run

Auto-detect and scan:

pnpm discover

Scan explicit subnet:

pnpm discover --cidr <CIDR>

Results are written to .brightsign/players.json (gitignored).

Output Format

  • Print a summary table: IP, model, serial, firmware, name
  • Confirm output path: .brightsign/players.json
  • Show number of players found

Troubleshooting guidance

If zero results:

  • Ask whether the developer is on the same VLAN/subnet as the players
  • Remind that Local DWS may be disabled or blocked by firewall rules
  • Suggest running pnpm discover --host <IP> --verbose for a known player first

When not to use it

  • Non-local networks
  • Projects without BrightSign hardware

Prerequisites

pnpm

Limitations

  • Requires local network access
  • Local DWS must be enabled

How it compares

It automates player discovery instead of manual IP scanning.

Compared to similar skills

player-discovery-scan side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
player-discovery-scan (this skill)04moReviewBeginner
applescript288moReviewAdvanced
bazel-build-optimization142moNo flagsAdvanced
home-assistant-manager98moReviewAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry