Document Pi SSH access skill
This commit is contained in:
@@ -1,5 +1,6 @@
|
|||||||
# HEARTBEAT.md
|
# HEARTBEAT.md
|
||||||
|
|
||||||
# Keep this file empty (or with only comments) to skip heartbeat API calls.
|
Hourly checklist:
|
||||||
|
1. Himalaya: check reynafamilybot@gmail.com inbox.
|
||||||
# Add tasks below when you want the agent to check something periodically.
|
2. Parse new instructions at top of any email coming from aeroreyna@gmail.com or adolforeyna@emmint.com (ignore others).
|
||||||
|
3. If there’s a new action item, summarize it back to Adolfo (include original sender + quick action note). If nothing new, reply HEARTBEAT_OK.
|
||||||
|
|||||||
@@ -14,3 +14,6 @@
|
|||||||
- **Key Data:**
|
- **Key Data:**
|
||||||
- Personal Email: `aeroreyna@gmail.com`
|
- Personal Email: `aeroreyna@gmail.com`
|
||||||
- Church Email: `adolforeyna@emmint.com`
|
- Church Email: `adolforeyna@emmint.com`
|
||||||
|
|
||||||
|
## 2026-02-16: We can do anything
|
||||||
|
- **Reminder:** Adolfo affirmed “we can do anything,” reinforcing that we’ll approach tasks with a how-first mindset and keep pushing forward.
|
||||||
28
skills/pi-ssh-access/SKILL.md
Normal file
28
skills/pi-ssh-access/SKILL.md
Normal file
@@ -0,0 +1,28 @@
|
|||||||
|
---
|
||||||
|
name: pi-ssh-access
|
||||||
|
description: "Remembers and documents how to SSH into the Raspberry Pi (192.168.68.126) as adolforeyna with the current ed25519 key. Use when the user asks for the connection details so Bro can log in from another machine or confirm passwordless access setup."
|
||||||
|
---
|
||||||
|
|
||||||
|
# Raspberry Pi SSH Access
|
||||||
|
|
||||||
|
## Key facts Codex should keep handy
|
||||||
|
|
||||||
|
- **Host:** `192.168.68.126` (Pi on the local LAN)
|
||||||
|
- **Username:** `adolforeyna`
|
||||||
|
- **Default port:** `22` (standard SSH)
|
||||||
|
- **Public key path (local):** `~/.ssh/id_ed25519.pub`
|
||||||
|
- **Private key path (local):** `~/.ssh/id_ed25519`
|
||||||
|
- **SSH key comment:** `adolforeyna@Mac-mini-M4.local`
|
||||||
|
- **Known hosts entry:** Added via `ssh-keyscan -H 192.168.68.126`
|
||||||
|
|
||||||
|
## Steps for Bro to reconnect
|
||||||
|
|
||||||
|
1. Ensure the Pi is online and reachable at `192.168.68.126`.
|
||||||
|
2. Use the generated key automatically: `ssh adolforeyna@192.168.68.126` (no password required).
|
||||||
|
3. If a host key error resurfaces, rerun `ssh-keyscan -H 192.168.68.126 >> ~/.ssh/known_hosts` and reconnect.
|
||||||
|
4. When the user requests, copy the public key again with `ssh-copy-id -i ~/.ssh/id_ed25519.pub adolforeyna@192.168.68.126`.
|
||||||
|
|
||||||
|
## Reminder for maintenance
|
||||||
|
|
||||||
|
- If the key ever changes or is rotated, update this skill and regenerate both `id_ed25519` and `id_ed25519.pub` as needed.
|
||||||
|
- Keep this skill synced with `tools/ssh` notes if you ever keep a separate reference file.
|
||||||
Reference in New Issue
Block a user