Agent skill

Pifinder Remote

by brickbots in brickbots/PiFinder

Run the PiFinder app headlessly and drive it like a user — launch it with no pygame window or physical display, send keypad presses to navigate menus, capture the screen as a PNG, read live state…

GPL-3.0Auto-check passed

Install Pifinder Remote

skills CLI
$ npx skills add brickbots/PiFinder --skill pifinder-remote -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install brickbots/PiFinder pifinder-remote --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/brickbots/PiFinder.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/pifinder-remote .claude/skills/pifinder-remote && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
pifinder-remote
GitHub stars
250
Token cost
~2.5k tokens
SKILL.md length
1,159 words
Files
2 (incl. scripts)
Skills in repo
3
Repo updated
First seen
Licence
GPL-3.0

At a glance

Run the PiFinder app headlessly and drive it like a user — launch it with no pygame window or physical display, send keypad presses to navigate menus, capture the screen as a PNG, read live state…

  • Works in 2 steps: Hipparcos catalog —… → tetra3 submodule —…
  • Verify UI-affecting changes by running the app and looking at the screen
  • SKILL.md covers The loop, Commands, Keypad buttons and How it works (and why stop is…, plus 3 more sections
  • Runs Python scripts from its folder; calls python3 and git; reaches github.com

What it does

Pifinder Remote is an agent skill from brickbots/PiFinder. Run the PiFinder app headlessly and drive it like a user — launch it with no pygame window or physical display, send keypad presses to navigate menus, capture the screen as a PNG, read live state (plate solve, location, IMU, SQM), and stop it cleanly. Use this whenever you need to actually operate or observe the running PiFinder UI rather than just read its code: "launch/start/run PiFinder", "navigate to <menu/screen", "take a screenshot of PiFinder", "press UP/DOWN/SQUARE", "what's on the PiFinder screen", "what…

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/pf_remote.py`).

It works with Python. The repository describes itself as: A plate solving telescope finder based around a Raspberry PI and RPI HQ Camera. The licence is GPL-3.0.

When your agent uses it

  • Verify UI-affecting changes by running the app and looking at the screen

Example prompts

  • “launch/start/run PiFinder”
  • “navigate to <menu/screen”
  • “take a screenshot of PiFinder”
  • “/pifinder-remote”

Requirements

  • Python 3

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. Hipparcos catalog — astro_data/hip_main.dat (~53 MB) is git-ignored
  2. tetra3 submodule — python/PiFinder/tetra3/ is a git submodule

What it can do on your machine

Read from SKILL.md and the folder at commit 3775008. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Pifinder Remote loads about 2.5k tokens when it runs. Until then it costs about 194 tokens; SKILL.md has 1,159 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~194
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from brickbots/PiFinder at commit 3775008, republished under its GPL-3.0 licence (© brickbots). 1,159 words, ~2,508 tokens.

Download SKILL.mdSave it as .claude/skills/pifinder-remote/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
pifinder-remote
description
Run the PiFinder app headlessly and drive it like a user — launch it with no pygame window or physical display, send keypad presses to navigate menus, capture the screen as a PNG, read live state (plate solve, location, IMU, SQM), and stop it cleanly. Use this whenever you need to actually operate or observe the running PiFinder UI rather than just read its code: "launch/start/run PiFinder", "navigate to <menu/screen>", "take a screenshot of PiFinder", "press UP/DOWN/SQUARE", "what's on the PiFinder screen", "what is it solving / where is it pointing", "check the UI shows X", "reproduce this UI bug", "drive the PiFinder interface", or "stop/shut down PiFinder". Also use it to verify UI-affecting changes by running the app and looking at the screen.

Driving PiFinder headlessly

PiFinder normally renders to a physical OLED/LCD (or a pygame emulator window) and is driven by a hardware keypad. This skill runs it in a headless mode — no pygame, no SDL window, no hardware — while still rendering every frame, and drives it entirely over PiFinder's HTTP API. That lets you launch the app, navigate its menus, see exactly what's on screen, read its live state, and shut it down, all from the command line.

Everything goes through one helper: scripts/pf_remote.py (Python standard library only — runs under any python3; it finds and uses the PiFinder venv itself when launching). Run python3 <skill>/scripts/pf_remote.py -h for the full command list.

The loop

bash
S=.claude/skills/pifinder-remote/scripts/pf_remote.py   # adjust path as needed

python3 $S launch            # start cedar + headless PiFinder (rev4, 176x176), wait for API
python3 $S launch -fb        # ...with the rev4 battery icon + a simulated discharge
python3 $S launch --display headless   # the 128x128 v3/v2.5 panel instead
python3 $S screen -o /tmp/pf.png   # capture the current screen as PNG
python3 $S key DOWN DOWN RIGHT     # send keypad presses, in order
python3 $S status            # aggregated live state as JSON
python3 $S stop              # graceful shutdown, then guaranteed teardown

After launch succeeds, the other commands find the running instance (URL + PIDs) from a small state file in the temp dir — you don't need to pass the URL. Read the PNG that screen writes (use the Read tool on the path it prints) to see the UI; that is how you "look at" PiFinder.

Commands

CommandWhat it does
launchStarts cedar-detect-server then PiFinder headless (-fh --camera debug --keyboard none --display headless_176 -x), in its own process group, and waits until /api/status answers. Records state for the other commands. --display {headless_176,headless,headless_320} picks the panel — default headless_176, rev4's 176×176; headless is the 128×128 panel on v3/v2.5. -fb/--fakebattery adds the rev4 battery monitor: the title-bar battery icon plus a full simulated discharge (low-battery warnings, blind-floor shutdown).
screen [-o PATH]Saves GET /api/screen (the live display) as a PNG and prints the path. 176×176 by default, 128×128 under --display headless.
key BTN [BTN ...]POSTs each button to /api/key in order (default 0.4s apart, --delay to change).
status / solution / locationPretty-prints GET /api/status / /api/solution / /api/location.
get PATHGETs any other endpoint, e.g. get /api/imu, get /api/sqm.
stopBest-effort graceful /api/stop, then escalates to SIGTERM/SIGKILL on the process group so nothing is orphaned.
killSkips the graceful step; force-kills the recorded process groups (recovery).
logs [-n N]Tails the captured PiFinder and cedar startup logs (first place to look if launch fails).
readyPolls until the API answers; useful after a manual launch.

Keypad buttons

PiFinder has a small keypad. Pass these names to key (case-sensitive), or a raw integer keycode:

  • Directions / actions: UP DOWN LEFT RIGHT PLUS MINUS SQUARE
  • Long press (held): LNG_LEFT LNG_UP LNG_DOWN LNG_RIGHT LNG_SQUARE
  • Alt (function) variants: ALT_UP ALT_DOWN ALT_LEFT ALT_RIGHT ALT_PLUS ALT_MINUS ALT_SQUARE ALT_0
  • Number keys: pass the digit as an integer, e.g. key 1 2 3

Navigation model: RIGHT (or SQUARE) generally drills into the highlighted item, LEFT goes back, UP/DOWN move the selection, LNG_LEFT returns to the top menu. After any input, take a fresh screen to confirm what happened — the screen is the ground truth, menu order changes between versions.

How it works (and why stop is built this way)

  • Headless rendering. The launch passes --display headless_176, which selects the in-memory DisplayHeadless176 driver (python/PiFinder/displays.py, backed by luma.core.device.dummy). It renders at 176×176 with rev4's Layout176 font and spacing profile, so what you capture matches the real rev4 panel rather than merely being scaled up. --display headless gives the 128×128 DisplayHeadless used by v3/v2.5. The UI render loop already calls shared_state.set_screen() beside every hardware draw, so the current frame is always available at GET /api/screen regardless of display driver. No pygame/SDL/X is needed.
  • Input. --keyboard none runs a no-op keyboard process; POST /api/key injects into the same keyboard_queue the main loop reads, so menu navigation behaves exactly as with the real keypad.
  • Solving works headless. With --camera debug, PiFinder cycles through sample frames and cedar-detect-server + the solver produce real plate solves, so status/solution return live RA/Dec/constellation.
  • Stopping is deliberately two-stage. PiFinder is multi-process; its workers run bare while True loops, aren't daemonized, and don't watch a stop flag. Clean shutdown depends on SIGINT reaching the whole process group at once (what a terminal Ctrl-C does). POST /api/stop does that from inside the app, which reliably stops the worker processes — but the main process can still hang in its teardown (a multiprocessing-manager shutdown race). So launch starts PiFinder in its own session/process group, isolated from the launcher, and stop escalates with SIGTERM→SIGKILL on that group after a short grace period. stop returns as soon as the process is actually gone. This guarantees no orphaned processes even when the graceful path stalls.
Show full SKILL.md (446 more words)Show less

Running in a git worktree

A fresh worktree (one created via git worktree add or EnterWorktree) is missing two things PiFinder needs to start, because git worktrees only check out tracked files and don't share git-ignored files or submodule contents with the main checkout. Copy them in from the main checkout before the first launch:

  1. Hipparcos catalog — astro_data/hip_main.dat (~53 MB) is git-ignored (see python/.gitignore) but required by UIChart / UIAlign. The chart screen will crash on construction if it's missing.
  2. tetra3 submodule — python/PiFinder/tetra3/ is a git submodule (https://github.com/smroid/cedar-solve). git submodule update --init inside a worktree typically fails ("Unable to find current revision in submodule path") because the submodule's git metadata isn't replicated to the worktree. Copying the populated directory in from the main checkout is the reliable path.

Both copies are one-time per worktree. Run from the worktree root:

bash
# Adjust MAIN to point at the main checkout (typically three dirs up from a
# .claude/worktrees/<name>/ worktree).
MAIN=../../..

cp "$MAIN/astro_data/hip_main.dat" astro_data/
cp -R "$MAIN/python/PiFinder/tetra3/." python/PiFinder/tetra3/

Venv: the worktree has no venv of its own and pf_remote.py launch only auto-discovers a venv inside the repo it was invoked from (python/venv, python/.venv, .venv, venv) — it does not cross into the main checkout to find one. So activate the main checkout's venv in your shell before launching, so pf_remote inherits it via sys.executable:

bash
source "$MAIN/python/venv/bin/activate"   # or python/.venv if that's where yours is

Alternatively, point pf_remote.py at the main checkout with --repo "$MAIN" so it finds the venv there — but then it also runs PiFinder from that checkout, not your worktree, which defeats the purpose.

When startup fails

launch waits up to --timeout seconds (default 90) for the API. The first launch in a fresh checkout rebuilds the catalog cache (~90s, one time); later launches come up in a few seconds. If it times out:

  1. python3 $S logs — read the PiFinder/cedar startup logs.
  2. Confirm the venv exists (python/venv or python/.venv) and the object DB is present (astro_data/pifinder_objects.db).
  3. If you're in a git worktree, confirm astro_data/hip_main.dat and python/PiFinder/tetra3/ are populated — see "Running in a git worktree".
  4. The API binds port 80 when it can, else 8080; launch probes both and records the winner. Pass --base-url http://host:port to override.
  5. If a previous run left something behind, python3 $S kill clears it.

Notes

  • Repo location is auto-detected (this skill lives under the repo). Override with --repo /path/to/PiFinder or the PIFINDER_REPO env var.
  • This skill requires two small pieces of in-repo support that ship with it: the headless display driver and the POST /api/stop endpoint (python/PiFinder/api_extensions.py). They're already in this branch.
  • The screen is 176×176 (rev4's panel, the default) or 128×128 under --display headless, and is rendered mostly in the red channel (PiFinder's night-vision palette); that's expected, not a rendering bug.
  • Plain -fh emulates rev3: no battery process and no title-bar battery icon. Add -fb when the shot or check involves the battery.

© brickbots, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (scripts) in .claude/skills/pifinder-remote of brickbots/PiFinder.

  • SKILL.md
  • scripts/pf_remote.py

Open the folder on GitHubat commit 3775008

Compare with similar skills

Pifinder Remote next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Pifinder Remote compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Pifinder Remote this skillbrickbots/PiFinder250—~2.5kAutomated safety check: PassGPL-3.0
MCP Server Builderanthropics/skills180k64 repos~2.3kAutomated safety check: PassApache-2.0
PDF Processinganthropics/skills180k48 repos~2kAutomated safety check: PassProprietary
NotebookLM Research AssistantPleasePrompto/notebooklm-skill7.8k14 repos~2.4kAutomated safety check: NotesMIT
Manim Video Productionbrowser-use/video-use28k6 repos~3kAutomated safety check: PassMIT
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 64 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • PDF Processing

    anthropics/skills

    Official

    Handles everyday PDF jobs in Python and on the command line: extract text and tables, merge, split, rotate, watermark, fill forms, encrypt and OCR.

    180k GitHub starsUsed in 48 repos~2k tokens
    Documents & OfficeAuto-check passed
  • NotebookLM Research Assistant

    PleasePrompto/notebooklm-skill

    Lets Claude Code ask questions of your Google NotebookLM notebooks through browser automation and return answers grounded in your uploaded sources.

    7.8k GitHub starsUsed in 14 repos~2.4k tokens
    Knowledge ManagementAuto-check: notes
  • Manim Video Production

    browser-use/video-use

    Produces math and technical explainer videos with Manim Community Edition: concept animations, equation derivations, algorithm walkthroughs and data stories.

    28k GitHub starsUsed in 6 repos~3k tokens
    Media & CreativeAuto-check passed
  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed
  • PPT Master

    hugohe3/ppt-master

    Generates editable PowerPoint decks, rebuilds slides from images, fills .pptx templates and polishes existing presentations through routed workflows.

    58k GitHub starsUsed in 1 repo~2.5k tokens
    Documents & OfficeAuto-check passed

More from brickbots/PiFinder

  • Docs

    brickbots/PiFinder

    Author and edit PiFinder's user-facing documentation in the project's house style.

    250 GitHub stars~6.2k tokensUpdated today
    Auto-check passed
  • I18n

    brickbots/PiFinder

    PiFinder's internationalization (i18n) workflow — marking strings for translation, running the Babel extract/update/compile pipeline, adding or updating language translations, and filling in missing…

    250 GitHub stars~2.8k tokensUpdated today
    Auto-check passed

Works with

Questions about Pifinder Remote

What does Pifinder Remote do?

Run the PiFinder app headlessly and drive it like a user — launch it with no pygame window or physical display, send keypad presses to navigate menus, capture the screen as a PNG, read live state…. Pifinder Remote is an agent skill from brickbots/PiFinder. Run the PiFinder app headlessly and drive it like a user — launch it with no pygame window or physical display, send keypad presses to navigate menus, capture the screen as a PNG, read live state (plate solve, location, IMU, SQM), and stop it cleanly.

When should I use Pifinder Remote?

Pifinder Remote fits situations like: verify UI-affecting changes by running the app and looking at the screen.

How do I install Pifinder Remote in Claude Code?

Run `npx skills add brickbots/PiFinder --skill pifinder-remote -a claude-code`. Or copy the skill folder (.claude/skills/pifinder-remote in brickbots/PiFinder) into .claude/skills/pifinder-remote in your project. Claude Code loads it when a task matches its description.

How do I install Pifinder Remote in Codex?

Run `npx skills add brickbots/PiFinder --skill pifinder-remote -a codex`. Or copy the skill folder (.claude/skills/pifinder-remote in brickbots/PiFinder) into .agents/skills/pifinder-remote in your project. Codex loads it when a task matches its description.

Can I use Pifinder Remote in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brickbots/PiFinder --skill pifinder-remote -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pifinder-remote, .gemini/skills/pifinder-remote, .github/skills/pifinder-remote and .opencode/skills/pifinder-remote in your project.

What does Pifinder Remote need to run?

Going by SKILL.md and its folder, Pifinder Remote needs Python for the scripts in its folder and the command-line tools its instructions call (python3 and git). Our summary lists: Python 3.

Does Pifinder Remote access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Pifinder Remote safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Pifinder Remote use?

Pifinder Remote is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Pifinder Remote use?

About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Pifinder Remote?

Skills that share tags, products or a category with Pifinder Remote: MCP Server Builder (anthropics/skills, 180k stars), PDF Processing (anthropics/skills, 180k stars), NotebookLM Research Assistant (PleasePrompto/notebooklm-skill, 7.8k stars) and Manim Video Production (browser-use/video-use, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pifinder Remote?

brickbots (a GitHub user) maintains it in brickbots/PiFinder, which has 250 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 7, 2026.

Source: brickbots/PiFinder on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.