31 lines
2.1 KiB
Markdown
31 lines
2.1 KiB
Markdown
---
|
|
name: didiosphere
|
|
description: Look up information about a location (OS instance) or device (physical machine) in the user's didiosphere repo at ~/Code/didiosphere. Use when the user invokes /didiosphere <name> or asks about a specific location/device by its Greek-named identifier (e.g. "delphi", "papyros").
|
|
---
|
|
|
|
# Didiosphere lookup
|
|
|
|
The user has a repository at `/Users/didericis/Code/didiosphere` that documents their personal network topology. Entities live in two directories:
|
|
|
|
- `locations/<name>/` — an OS instance (often tied to a specific device). Named after ancient Greek islands/cities.
|
|
- `devices/<name>/` — a physical computer. Named after ancient Greek nouns.
|
|
|
|
The argument to this skill is a single name (e.g. `delphi`, `papyros`). It may match a location, a device, or — rarely — both.
|
|
|
|
## What to do
|
|
|
|
1. Take the name from the skill argument. Lowercase it for matching.
|
|
2. Check both `/Users/didericis/Code/didiosphere/locations/<name>/` and `/Users/didericis/Code/didiosphere/devices/<name>/`. Report which (if either) exists.
|
|
3. For each match, Read every non-binary file in that directory tree (typically `README.md`, `JOURNAL.md`, and similar). Summarize what the entity is, its purpose, and any noteworthy state from the journal.
|
|
4. If the name doesn't match any directory, list the available locations and devices so the user can pick.
|
|
|
|
## Hard rules (from the repo's CLAUDE.md)
|
|
|
|
- **Never** read, cat, grep, or otherwise inspect any file ending in `.pem` or `.pub` under `locations/*/ssh/`. Treat them as opaque.
|
|
- Filenames in those `ssh/` directories are fine to list and discuss (filenames encode routing metadata) — only file _contents_ are off-limits.
|
|
- If a permission error fires on a `.pem`/`.pub` path, that is the repo's settings working as intended. Do not ask the user to override it.
|
|
|
|
## Output
|
|
|
|
Lead with one sentence identifying the entity (location vs device, what it's for). Then a tight summary of what the docs say. If a `JOURNAL.md` exists, note the most recent entry. Keep it short — the user knows their own repo; they want a refresher, not a recitation.
|