skills/omnisess-active/SKILL.md
Show currently active AI coding sessions (Claude Code, Cursor, Codex, GitHub Copilot CLI, Gemini). A session is active if the underlying process is alive and the session file was modified within the last 2 minutes. Use this skill when asked about active sessions, running sessions, what is currently open, or which AI tools are in use right now. Trigger phrases: "active sessions", "running sessions", "what's open", "current sessions", "is claude running", "what sessions are active", "show active".
npx skillsauth add psacc/omnisess activeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Show currently active AI coding sessions.
omnisess active
omnisess binary is available:if ! command -v omnisess &>/dev/null; then
echo "omnisess not found. Install it with:"
echo " go install github.com/psacc/omnisess@latest"
exit 1
fi
omnisess active "$@"
A session is considered active when:
claude:5c3f2742 ~/prj/myapp (process alive, modified 47s ago)
tools
Print AI coding sessions for a calendar day as Obsidian-compatible markdown with the full Q&A content of every session. Intended for daily-note workflows: paste the output into a daily journal to preserve a searchable record of what was discussed with which AI tool. Use this skill when asked to dump today's sessions as markdown, prepare a daily-note entry, archive Q&A for Obsidian, or export a calendar-day's coding conversations. Trigger phrases: "digest today's sessions", "dump sessions as markdown", "obsidian daily note", "archive my coding chats", "export today's Q&A", "session log for daily note".
development
Classify agent skills by usage tier (Keep / Borderline / Archive / Unknown) using Claude Code session JSONL transcripts as the signal source. Read-only — never modifies skills, sessions, or any file on disk. Use this skill when asked to audit skills, find unused skills, classify skills, check which skills get used, produce a skill usage report, or prune skills. Trigger phrases: "audit skills", "find unused skills", "classify skills", "which skills do I use", "skill usage report", "prune skills", "what skills are unused", "skills I can remove", "trim my skill list". Output is a recommendation (Keep / Borderline / Archive) — acting on it is always a manual step.
testing
Test skill eta
testing
Test skill epsilon