frytg/frytg-dotfiles

Fetch any public AT Protocol data as clean Markdown — resolve handles/DIDs, browse repos, read records from any collection on any PDS (Bluesky or third-party lexicons), resolve lexicon schemas by NSID, discover every repo using a lexicon, explore backlinks, and trace a did:plc identity's history via its PLC audit log. Use whenever the user shares an at:// URI, a handle/DID, or a lexicon NSID (e.g. app.bsky.feed.post, site.standard.document), or asks to inspect AT Protocol / atproto / Bluesky / Standard.site data, or wants to know when an account migrated PDS or changed its handle.

Triage a Better Stack (Better Uptime) incident webhook delivered by the skill harness. Parse the payload, enrich with monitor/availability/timeline data, classify severity + blast radius + suspected cause + confidence + summary, draft a comment for the incident, and persist the event plus open questions to MEMORIES.md and a per-incident record in INCIDENTS.md. Posting the comment is delegated to the host MCP; if the host's Betterstack MCP is read-only (current state), the skill stops at the draft. Use when the harness surfaces an incident webhook, when the user says "triage this Better Uptime alert" with an incident id, or when a Betterstack MCP read tool returns an active incident that should be assessed.

Generate decision-ready summaries in BLUF (Bottom Line Up Front) format. Use when the user asks for a summary, brief, status report, executive summary, recap, or "what does X say" where the reader needs the answer first and the supporting context second.

Bumps the project version based on conventional commits on the current branch, writes a new entry to CHANGELOG.md following Keep a Changelog 1.1.0, and updates package.json#version. Use when the user asks to cut a release, prepare a version bump, or refresh the changelog.

Promotes curated

Turn a conversation, plan, or sketch into a GitHub issue — optionally sliced into tracer-bullet child issues with blocking edges. Use when the user asks to create an issue, open a ticket, write a PRD/spec to GitHub, break work into tickets, or uses create-issue / to-spec / to-tickets phrasing.

Run shell commands in an ephemeral Daytona cloud sandbox via the daytona CLI. Use when a task needs an isolated Linux runtime — untrusted commands, package experiments, /tmp-style probes, network reachability checks, anything that shouldn't touch the host. Skip when the task needs the local repo (sandboxes don't auto-sync the working tree) or long-lived state across many turns. Requires daytona CLI installed and authenticated; if not, warn the user and stop.

Checks for outdated dependencies in a project using its configured package manager (bun, npm, nub, cargo, go, pip, bundler), plus GitHub Actions refs, Terraform provider pins, and container images in Kubernetes manifests; fetches upstream release notes to flag breaking changes. Use when the user asks to check for updates, look for outdated packages, audit dependencies, or review upgrade impact.

Save an article (markdown body) into the Obsidian vault under Dots/. Detects the active frontmatter style by inspecting the last few entries in Dots/<year>/qN/. Use when the user asks to save, archive, capture, or store an article, essay, post, or long-form read into their Obsidian Dots folder.

Refresh the Aktive Datenlieferanten table in ARD Eventhub docs/index.md from Datadog logs of swr-radiohub-ingest. Resolves institution URNs from the ARD Core feed (just feed → ard-core-livestreams.json), then counts live metadata for Eventhub TEST vs PROD. Use when updating active publishers, broadcasters, Datenlieferanten, or the TEST/PROD checklist on the Eventhub docs homepage.

Bumps the Eventhub ingest Docker tag (optional dev, test, prod). Use when deploying or updating that image. Confirms before the staging merge request, then again before staging into main.

Look up ARD Eventhub identifiers (publisher URNs, topic URNs, contribution CRIDs) for radio stations and individual contributions in Datadog logs of the SWR radiohub-ingest service. Maps human-readable inputs (station name, publisher Core ID, crid:// external id) to the hashed URNs the service actually logs, then queries structured Eventhub payloads. Use when the user asks about ingest activity for a specific station, contributor, or contribution in dev/stage/prod.

Walks Kubernetes manifests in a project, uses crane ls to find the latest tag for each pinned container image, presents proposed bumps with file path + current/new tag + bump type, asks the user to confirm each one, then updates the YAML on approval. Use when the user asks to check, bump, update, or upgrade container image versions in k8s/ArgoCD/Helm-rendered manifests. Nothing is applied to a cluster — the user reviews the diff and deploys manually.

Pull recent posts from the user's LinkedIn feed and write a one-page BLUF briefing in their voice. Tool-agnostic — works with any persistent browser automation (Osaurus, Playwright MCP, Browserbase, etc.) with a Firecrawl/Exa fallback for public-only summaries. Use when the user asks for a LinkedIn briefing, feed summary, "what's on my feed."

Lint and write Markdown that renders correctly across CommonMark, GFM, GitHub, Hugo, MkDocs, and most static-site generators. Use when editing any .md file or auditing documentation. Covers spacing around block elements, list and emphasis conventions, and final-newline requirements.

Turn raw transcripts, scattered notes, or a voice memo into a decision log, a task list, and a status log — not a transcript. Use when the user pastes a meeting transcript, says "summarize this meeting", "meeting notes", "what were the action items", "write up from this call", "debrief", "recap", "what did we decide", or hands over notes from a standup, 1:1, client call, planning session, retrospective, or all-hands.

Migrate a GitHub repository to Tangled and optionally mirror it back to GitHub via a Spindle workflow. Use when the user asks to move a repo to Tangled, mirror a GitHub repo to Tangled, set up a Tangled mirror that pushes back to GitHub, or replicate their workflow onto a federation-based git host.

Draft messages, posts, and notes in Dan's actual writing voice. Use whenever drafting anything on his behalf — DMs, posts, emails, notes. Never send or publish; always present the draft for his review first.

Work with an Obsidian vault using the agent's file tools and the official obsidian CLI. Use when the user asks to capture into their vault, find or update a note, set a frontmatter property, or run any Obsidian-side operation.

Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser through the orca CLI. Use when the user says "$orca-cli", "Orca worktree", "child worktree", "spawn codex/claude in a worktree", "read/wait/send Orca terminal", "handoff" / "handover" / "give this to another agent", "Orca browser", "orca artifacts", or "share skills". Prefer it over raw git worktree, ad hoc PTYs, or Computer Use when Orca state is involved. Use Computer Use only when a visible window needs GUI control that a CLI, filesystem, or API cannot do.

Drives the GUI of a visible local app window through orca computer: accessibility tree, clicks, typing, menus, dialogs, and screenshots in native apps and external browser windows (Chrome, Edge, Safari) or webviews. Prefer a programmatic path (shell, filesystem, git, HTTP, existing CLIs) whenever it can complete the task. Use only when a visible window needs GUI control those cannot reach. Do not use for Orca's embedded browser (orca-cli).

Coordinate supervised Orca workers: threaded messages, blocking ask/reply, task dispatch, worker_done/escalation waits, task DAGs, decision gates, coordinator loops, and decomposing work across agents. Use orca-cli for full ownership handoffs — "hand off", "handoff", "handover", "give this to another agent", "another worktree" — unless asked to supervise, monitor, or coordinate a DAG, and for terminal control, lightweight terminal prompts, shell commands, Orca worktree management, and reading or waiting on terminals.

Peer-level clarification of a plan, decision, or idea until shared understanding is explicit. Use when the user wants to pressure-test thinking before acting, unstick an ambiguous scope, or uses phrases like peer-clarify, clarify this, pressure-test, walk me through the decisions, or "don't implement yet — quiz me".

Resolve a podcast URL (Apple Podcasts episode/show page, or an already-direct audio link) to the direct audio file URL plus its normalized content type. Use when the user pastes a podcasts.apple.com link and the audio file is needed — e.g. before downloading, transcribing, or summarizing an episode (pairs with the podcast-bluf-summary skill).

Summarize a podcast episode as a BLUF brief by downloading the audio and sending it to Gemini Pro via OpenRouter. Use when the user pastes a podcast link (especially podcasts.apple.com) and asks for a summary, brief, or recap. Resolves the audio URL with the podcast-audio-url skill and formats output per the bluf skill.

Proofread a file or pasted text and return a bullet list of suggestions covering spelling, style, grammar, and punctuation (including commas). Each line starts with the source line number followed by the suggested fix; the changed word(s) or phrase(s) are wrapped in **bold**. Skips capitalization flags — see my-voice. Never edits the source.

Scan a codebase for module-deepening opportunities, write a visual Markdown architecture report, then peer-clarify the candidate you pick. Use when the user wants to improve architecture, find shallow modules, deepen seams, pressure-test structure for testability/AI-navigability, or asks for an architecture review / deepening pass.

Create RFC documents anywhere on disk. Asks clarifying questions one at a time, then writes a YYYY-MM-DD-topic.md file in BLUF + bullet-point style. Resolves the output directory from the user's explicit path, the working directory's rfc/ or docs/rfc/ folder, or asks if neither exists.

Surface setup-level changes worth making from the current conversation and the context files in the working directory. Read-only — suggestions only, never writes. Use when the user asks for a self-improvement check, setup review, "anything to improve?", "recurring patterns", "any setup changes worth making?", or after a long session.

Retrieve content from tangled.org, a federated git platform built on AT Protocol. Use when the user shares a tangled.org URL or asks to fetch/read/inspect content from any Tangled knot. All repos are public — files come over plain HTTP at /raw/{ref}/{path}; issues, PRs, comments, and repo metadata live as AT Protocol records on the owner's PDS (fetch via atproto.md or direct XRPC).