← ClaudeAtlas

fieldylisted

Use when reading conversations, transcripts, summaries, or action items captured by a Fieldy AI wearable note taker, or when the user mentions Fieldy, their wearable, or wants the record of something said in person rather than on a video call. Covers API key setup, the time-window query model, pagination, and the async-processing and speaker-labelling gotchas that make naive reads report incomplete data.
TechNickAI/hermes-skills · ★ 0 · AI & Automation · score 76
Install: claude install-skill TechNickAI/hermes-skills
# Fieldy ## When to Use Use when the user mentions Fieldy, their wearable, or wants a real-world (non-video-call) conversation transcript, summary, or the action items the device captured. Also use when asked what was said in a specific in-person meeting, hallway conversation, or errand. Fieldy is a wearable AI note taker (pendant or wrist, Bluetooth to a phone) with a companion desktop app that captures Zoom/Teams/Slack calls. It transcribes conversations and generates summaries, keywords, quotes, speaker labels, and action items. This skill reads that data over Fieldy's Public REST API. If the user runs several capture devices (a meeting notetaker, a second pendant), coverage differs by device. A gap in Fieldy is not evidence the conversation never happened — check the other sources before concluding anything is missing. ## Setup 1. Open the **Fieldy mobile app** → **Settings** (gear icon) → **Developer Settings** → copy the API key. It starts with `sk-fieldy-` and is long-lived. The same screen exists in the desktop app. 2. Export it as `FIELDY_API_KEY`, or put it in a `0600` dotenv file and pass `--env-file /path/to/.env`. It is a bearer token for the user's entire personal conversation history — treat it like a password. 3. Verify: `python3 scripts/fieldy.py whoami` → returns `{"email": "..."}`. A wrong key returns HTTP 401 `{"code":"UNAUTHORIZED"}` with exit 1. The client reads **only** the environment variable and an explicitly-passed `--env-file`