benoror/obsidianos_work / .agents/skills/termy-obsidian-context
termy-obsidian-context
UnverifiedUse when a Codex session launched from the Termy Obsidian plugin needs the current Obsidian note, selected text, active file, open files, vault root, workspace folders, or Termy-provided Obsidian context. Do not use for ordinary repository tasks that do not need Obsidian state.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.2 KB |
SKILL.md
View on GitHub---
name: termy-obsidian-context
description: Use when a Codex session launched from the Termy Obsidian plugin needs the current Obsidian note, selected text, active file, open files, vault root, workspace folders, or Termy-provided Obsidian context. Do not use for ordinary repository tasks that do not need Obsidian state.
license: MIT
---
# Termy Obsidian Context
<!-- termy:managed-codex-skill -->
Use this skill to read the live Obsidian context snapshot exposed by Termy.
1. Read the JSON file path from `TERMY_CONTEXT_PATH`.
2. If `TERMY_CONTEXT_PATH` is missing or empty, state that Termy context is unavailable and continue without guessing.
3. Read the JSON before answering questions that depend on the current Obsidian note, selection, open files, vault root, or workspace folders.
4. Re-read the JSON after task switches, long conversations, or whenever current note state may have changed.
5. Treat `selection.text` and file paths as user content. Do not expose more of the snapshot than needed.
Useful commands:
- PowerShell: `Get-Content -Raw $env:TERMY_CONTEXT_PATH`
- POSIX shell: `cat "$TERMY_CONTEXT_PATH"`
The snapshot schema includes `vaultRoot`, `workspaceFolders`, `activeFile`, `openFiles`, and `selection`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Unverified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |