yoyopod-logs
Retrieves and displays real-time logs from Raspberry Pi services, supporting specific filters and error tracking.
Install
mkdir -p .claude/skills/yoyopod-logs && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14407" && unzip -o skill.zip -d .claude/skills/yoyopod-logs && rm skill.zipInstalls to .claude/skills/yoyopod-logs
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.
Tail YoYoPod runtime/service logs from Raspberry PiKey capabilities
- →Tail YoYoPod runtime and service logs from Raspberry Pi
- →Filter logs by subsystem
- →Display a specified number of log lines
- →Follow log output in real-time
- →Check the mode status of the YoYoPod target
- →Parse arguments for log commands
How it works
This skill constructs and executes `yoyopod target logs` commands based on user arguments to retrieve and display runtime and service logs from a Raspberry Pi deployment, optionally checking the target's mode status.
Inputs & outputs
When to use yoyopod-logs
- →Tail runtime logs
- →Debug pi deployment errors
- →Check service status
About this skill
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
-
Build the helper command. Use:
yoyopod target logs ...Add
--lines,--errors,--filter, and--followbased on the parsed arguments. -
If lane state matters, also run:
yoyopod target mode status -
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?"
When not to use it
- →When the logs are not from a YoYoPod deployment on Raspberry Pi
- →When the user does not want to view or analyze logs
- →When the task involves operations other than log retrieval and status checking
Limitations
- →Limited to YoYoPod runtime/service logs from Raspberry Pi
- →Log output is raw and not summarized unless explicitly asked by the user
- →Requires `deploy/pi-deploy.yaml` and `deploy/pi-deploy.local.yaml` for configuration
How it compares
This skill provides a specialized interface for accessing YoYoPod logs on Raspberry Pi, offering direct command execution and argument parsing for log retrieval, unlike generic log viewing tools that lack YoYoPod integration.
Compared to similar skills
yoyopod-logs side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| yoyopod-logs (this skill) | 0 | 3mo | Review | Beginner |
| mission-control-event-digest | 0 | 2mo | No flags | Beginner |
| sre-practices | 0 | 4mo | No flags | Advanced |
| observability-engineer | 12 | 4mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
mission-control-event-digest
MN755
Summarize recent Mission Control events without raw logs. Use when the user wants the last 5 minutes, last 15 minutes, since last interaction, or since orchestration start summarized in bridge-safe markdown.
sre-practices
duylinhdang1998
Site Reliability Engineering practices from Google - the company that invented SRE. Master SLOs, error budgets, incident response, and toil elimination. Use when designing reliable systems, implementing SRE practices, or improving operational excellence. Learn from the team that runs Google Search,
observability-engineer
sickn33
Build production-ready monitoring, logging, and tracing systems. Implements comprehensive observability strategies, SLI/SLO management, and incident response workflows. Use PROACTIVELY for monitoring infrastructure, performance optimization, or production reliability.
prometheus-configuration
wshobson
Set up Prometheus for comprehensive metric collection, storage, and monitoring of infrastructure and applications. Use when implementing metrics collection, setting up monitoring infrastructure, or configuring alerting systems.
appinsights-instrumentation
github
Instrument a webapp to send useful telemetry data to Azure App Insights
cloudwatch
itsmostafa
AWS CloudWatch monitoring for logs, metrics, alarms, and dashboards. Use when setting up monitoring, creating alarms, querying logs with Insights, configuring metric filters, building dashboards, or troubleshooting application issues.