Skills Guide

Tail YoYoPod logs on Raspberry Pi

VerifiedCaution

Tail runtime/service logs from a YoYoPod deployment on a Raspberry Pi. Supports filtering, error-only mode, and follow mode.

Download and use
Sby Skills Guide Bot
DevOpsIntermediate
7/22/2026
Claude Code
#logging#raspberry-pi#deployment#troubleshooting#cli

Recommended for

Backend developerClaude CodeDevOps engineerGit automationDebugging

Automated summary

Tails YoYoPod runtime and service logs from a Raspberry Pi through the `yoyopod target logs` command, with filtering, error-only mode, and live follow.

Strengths

  • Parses arguments (line count, --errors, --filter, --follow) and forwards each one to the underlying command
  • Relies on the shared deploy contract `deploy/pi-deploy.yaml` plus a local override to target the right host
  • Can check lane state with `yoyopod target mode status` when deployment context matters
  • Returns raw log lines instead of summarizing, so no error detail gets lost

Limitations

  • Tightly coupled to the YoYoPod project: requires the `yoyopod` CLI, the repo, and SSH access to the Pi
  • Performs no automatic summarization or log analysis, leaving diagnosis entirely to the user
  • Model invocation is disabled, so it must be triggered explicitly by the user
When to use it

When you need to inspect YoYoPod service logs on the Pi quickly, for instance after a failure or to watch behavior live.

When not to use it

When you are outside the YoYoPod repository, lack a configured `yoyopod` CLI, or have no SSH access to the target.

Security analysis

Caution
Quality score74/100

No destructive, exfiltration, or obfuscated behavior: it shells out to a single project CLI (`yoyopod target`) to read Pi logs, and Read is used for a config file. Risk is moderate rather than low because user-supplied arguments are passed into a shell command without quoting guidance and because `config edit` is an interactive, file-writing path — reasonable to ship with a caveat rather than block.

Findings
  • •Free-form user arguments (notably --filter <value>) are interpolated into a shell command with no instruction to quote or escape them; a crafted value could append extra shell commands. The Bash(yoyopod target:*) prefix restriction may not block this because the injected payload would ride inside an allowed command string.
  • •`yoyopod target config edit` opens an interactive editor and creates/modifies deploy/pi-deploy.local.yaml, which is state-changing rather than read-only; the skill does not bound where the editor may be pointed.
  • •`--follow` produces a long-running foreground process; nothing in the skill says to bound it or how to stop it, which can hang an agent session.
  • •The skill trusts a project-local YAML deploy contract for host/SSH/branch values, so the actual remote targets are outside the skill's control.
How this analysis is made

Examples

Recent errors
/yoyopod-logs 200 --errors
Follow a subsystem live
/yoyopod-logs 50 --filter media --follow
Diagnose a dropped call
/yoyopod-logs 300 --filter call --errors then explain why the call dropped

name: yoyopod-logs description: Tail YoYoPod runtime/service logs from Raspberry Pi disable-model-invocation: true allowed-tools:

  • Read
  • Bash(yoyopod target:*) argument-hint: "[line_count] [--errors] [--filter <subsystem>] [--follow]"

Config

Use deploy/pi-deploy.yaml as the shared deploy contract and deploy/pi-deploy.local.yaml for machine-specific overrides such as host, SSH user, dev lane checkout, and branch. The tracked dev default is /opt/yoyopod-dev/checkout; prod slots live under /opt/yoyopod-prod. yoyopod target merges the files directly, and yoyopod target config edit is the preferred way to create or update the local override.

If the file does not exist yet, run yoyopod target config edit first. That command creates deploy/pi-deploy.local.yaml automatically before opening it.

Argument Parsing

Parse the arguments string provided after /yoyopod-logs:

  • Line count: If a bare number is present (for example /yoyopod-logs 100), map it to --lines <count>. Default: 100.
  • --errors flag: Pass through to yoyopod target logs --errors.
  • --filter value: Pass through to yoyopod target logs --filter <value>.
  • --follow flag: Pass through to yoyopod target logs --follow.

Multiple flags can be combined.

Steps

  1. Build the helper command. Use:

    yoyopod target logs ...

    Add --lines, --errors, --filter, and --follow based on the parsed arguments.

  2. If lane state matters, also run:

    yoyopod target mode status

  3. Present the log output. Return the raw log lines directly. Do not summarize or truncate unless the user explicitly asks.

After presenting the logs, remind the user they can ask follow-up questions about the log content, such as "why did the call drop?" or "what errors happened in the last minute?"

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/tail-yoyopod-logs-on-raspberry-pi-mrwakb3r/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/tail-yoyopod-logs-on-raspberry-pi-mrwakb3r' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/tail-yoyopod-logs-on-raspberry-pi-mrwakb3r/download' --output '.skill-downloads/tail-yoyopod-logs-on-raspberry-pi-mrwakb3r/SKILL.md.part' && mv '.skill-downloads/tail-yoyopod-logs-on-raspberry-pi-mrwakb3r/SKILL.md.part' '.skill-downloads/tail-yoyopod-logs-on-raspberry-pi-mrwakb3r/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/tail-yoyopod-logs-on-raspberry-pi-mrwakb3r/SKILL.md' && test -s '.skill-downloads/tail-yoyopod-logs-on-raspberry-pi-mrwakb3r/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/yoyopod-logs' && cp -R '.skill-downloads/tail-yoyopod-logs-on-raspberry-pi-mrwakb3r' '.claude/skills/yoyopod-logs'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/tail-yoyopod-logs-on-raspberry-pi-mrwakb3r'

openskills read 'tail-yoyopod-logs-on-raspberry-pi-mrwakb3r'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/tail-yoyopod-logs-on-raspberry-pi-mrwakb3r/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

Configure a Chat Channel with SecretRefs

DevOps

Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.

Claude CodeCodexintermediateSafe 387,940
Skills Guide Bot

Investigate ClickHouse CI Failures

DevOps

Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.

Claude CodeadvancedSafe 49,516
Skills Guide Bot

Ansible PR Review

DevOps

Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.

Claude CodeintermediateSafe 70,491
Skills Guide Bot