claude-get-session-info
Shared utility script for getting Claude PID and Session ID. Source this in other scripts to access CLAUDE_PID and SESSION_ID variables.
npx skills add majiayu000/claude-skill-registry --skill claude-get-session-info --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Get Session Info Shared utility for session management - not directly invoked. **Usage (source in scripts):** ```bash source .claude/skills/claude-get-session-info/scripts/get-session-info.sh echo "Claude PID: $CLAUDE_PID" echo "Session ID: $SESSION_ID" ``` Exports `CLAUDE_PID` and `SESSION_ID` environment variables.
source .claude/skills/claude-get-session-info/scripts/get-session-info.sh echo "Claude PID: $CLAUDE_PID" echo "Session ID: $SESSION_ID"
What does the claude-get-session-info skill do?
Shared utility script for getting Claude PID and Session ID. Source this in other scripts to access CLAUDE_PID and SESSION_ID variables.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill claude-get-session-info --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
