session-search/SKILL.md
This skill should be used when searching Claude Code session transcripts with semantic understanding. Triggers on queries like "find sessions about X", "when did I work on Y", "search previous conversations". Supports natural language queries with synonym matching.
npx skillsauth add glebis/claude-skills session-searchInstall 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.
Search Claude Code session transcripts by combining keyword pre-filtering with semantic evaluation. Finds previous sessions about specific topics, debugging conversations, research tasks, or any past work.
Execute scripts/search.py with the user's query:
python3 scripts/search.py "<query>" [max_results] [max_age_days]
query (required): Natural language search querymax_results (optional, default 10): Maximum results to returnmax_age_days (optional, default 90): How far back to searchThe script performs keyword pre-filtering across all sessions, then extracts meaningful excerpts from top candidates. Output contains a SESSIONS_DATA JSON block.
After receiving the script output, evaluate each session's relevance to the query. Consider:
Assign a relevance score (0-10) to each session based on excerpt content and query intent.
Display the top results (up to max_results) sorted by relevance, formatted as:
### [Relevance: N/10] Project — Date
Summary of what the session was about (1-2 sentences based on excerpts)
`claude --resume <session-id>`
If no relevant results are found, report that and suggest alternative queries.
Sessions are stored as JSONL files in ~/.claude/projects/. Each file contains events with user/assistant messages and tool calls. The search script handles file discovery and text extraction automatically.
To search older sessions or get more results:
/session-search "query" 20 180
(20 results, 180 days lookback)
documentation
Cut a software release and maintain a tiered compatibility policy. Use when the user wants to release, ship a version, bump the version, tag a release, write a changelog, or update COMPATIBILITY. Config-driven via release.config.json; bumps version files, runs a readiness gate, updates COMPATIBILITY.md tiers and deprecations, tags (→ release workflow), and reports closed issues. Teaches the underlying standards as it runs.
development
Sync and manage bilingual (EN/RU) library content for agency-docs. Use when adding, updating, or reviewing library articles. Handles translation, sync checks, and Russian stylistic review.
development
This skill should be used to watch a long-running background job (ffmpeg/media encode, qmd or other embedding/vector-DB run, batch agent/LLM pipeline, or a real-browser/agent-browser daemon) until it finishes or wedges, then deliver a verdict (done, needs-attention, or blocked) plus the exact next command, without burning dozens of manual poll commands. Triggers on "babysit this job", "watch this until it's done", "ping me when the encode/embed/batch finishes", "is this background process stuck", "monitor this ffmpeg/qmd run", or any request to wait on a long-running process and be told when it's complete or hung.
development
Use when the user wants Claude Code, Codex, or other AI coding/business agents to work together as peers. This skill should be used whenever the user mentions coordinating Claude Code and Codex, agent handoffs, multi-agent workflows, parity, respect, pushback between agents, deciding which agent should lead, or turning a business/code workflow into a two-agent operating model.