Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

session-search

Estrelas90

Forks2

Atualizado29 de junho de 2026 às 08:09

Find context from past Claude Code (CLI) and Claude Cowork (desktop) sessions on this Mac. Use when the user wants to recall something they did before but can't find it , phrasings like "where did I work on X", "find that session where I…", "when did I last do Y", "pull up the conversation about Z", "that time I built/tried/discussed …". Searches by kind (code/cowork), time range, title, working directory, or free-text content across all transcripts.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

techwolf-ai

techwolf-ai/ai-first-toolkit

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

Explorador de arquivos

5 arquivos

SKILL.md

readonly

Mais deste repositório

mesmo repositório

goal-prompt

techwolf-ai/ai-first-toolkit

Turn a task, plan, or feature request into a ready-to-paste Claude Code /goal command — a single completion condition with a measurable end state, a demonstrable proof, and the constraints that must not drift. Use when the user says "give me a goal", "goal prompt", "make this a /goal", "turn this into a goal", or wants an autonomous long-running objective for Claude Code.

2026-07-1090

build-plugin

techwolf-ai/ai-first-toolkit

Bundle skills, hooks, agents, or an MCP server into one installable Claude Code plugin and ship it. Use when asked to bundle tools into one plugin, package tools for a colleague, publish a plugin to a marketplace, share my tools with my team, or ship a plugin. Asks who it's for and where it's hosted, then walks analyze, assemble, ship, and maintain, tailored to that answer. Sibling to build-mcp.

2026-07-0790

handoff

techwolf-ai/ai-first-toolkit

Write a session handoff at the end of a session so the next session can start from where this one stopped without rereading the whole conversation. Use when user says "handoff", "wrap up", "write a handoff", "end of session", "park this session", "save where we are", or to RESUME with "/handoff read", "pick up the handoff", "read the handoff". Writes a tight resume note (HANDOFF.md) into the working directory, not a full transcript. Scope is the current project's resume note only: not searching or summarizing past sessions, and not any project-specific "resume" command the environment may have.

2026-06-2990

task-profile

techwolf-ai/ai-first-toolkit

Mine the user's Claude Code + Cowork session history into a structured task profile, what they do with AI, how often, how successfully where friction lives, then propose atomic skills that would reduce iteration. Use when the user asks to "analyse my Claude use", "build a task profile", "what tasks do I do with Claude", "where am I spending tokens", "what skills would help me", or mentions reviewing past sessions for patterns. Produces profile.csv (shareable), explorer.html (personal coaching view with AI-first principle comparison + token-spend chart), and skill-proposals.md.

2026-06-1290

token-doctor

techwolf-ai/ai-first-toolkit

Personal diagnosis of where your Claude Code + Cowork spend goes. Reads local transcripts, prints your conversation length distribution, marathon share, cache rebuild costs, and per-project diagnosis (good projects and problem projects) right in the terminal. Then offers a deeper dive that fans out parallel Haiku subagents over your most expensive (and most efficient) sessions and writes a tight Markdown report. Use when the user asks "why is my Claude spend so high", "where am I burning tokens", "diagnose my Claude habits", "audit my Claude usage", or asks for a personal token-cost diagnosis.

2026-06-1290

setup-content-studio

techwolf-ai/ai-first-toolkit

Set up a new content studio for a person. Copies the plugin template, adapts it to the person's voice, themes, and content types through interactive discovery. Use when asked to create a content studio for someone new.

2026-06-1090

name

session-search

description

session-search

Platforms: Claude Code / Cowork and Codex. find_sessions.py and show_session.py detect the host (via the platform stamp install.sh writes, or AI_FIRST_PLATFORM) and route to the right store: Claude Code (~/.claude/projects) + Cowork transcripts, or Codex rollouts (~/.codex/sessions/**/rollout-*.jsonl). Both support list, time/cwd/title filters, and full-text --grep. Antigravity is not supported: its IDE conversations are AEAD-encrypted at rest (~/.gemini/antigravity/conversations/*.pb) and its unencrypted CLI store carries no parseable turn content, so the skill prints a clear "not available" message and exits.

Two scripts in scripts/ locate past sessions and dump their content:

find_sessions.py , discover + filter sessions (metadata + optional full-text grep).
show_session.py , print a single session's conversation (user/assistant turns) in readable form.

Both read directly from disk , no API calls, no auth. They resolve paths from $HOME so they work for any macOS user:

Claude Code CLI: ~/.claude/projects/*/\*.jsonl
Claude Cowork: ~/Library/Application Support/Claude/local-agent-mode-sessions/*/*/local_*/audit.jsonl (sibling local_*.json holds title/metadata)

How to use

Start narrow, widen if needed. Prefer --grep for content recall; use metadata filters to scope.

Step 1 , find candidate sessions

scripts/find_sessions.py --grep "recruitee logo api"      # content search
scripts/find_sessions.py --title "rippling"              # title substring
scripts/find_sessions.py --cwd "Recruitee"               # Code sessions under matching cwd
scripts/find_sessions.py --since 2026-03-01 --until 2026-03-31
scripts/find_sessions.py --kind cowork -n 30             # 30 most recent Cowork

Combine freely. Output is a table by default; add --json for structured piping.

--grep PATTERN is a regex (case-insensitive). It searches message text inside every transcript and prints 1-2 matching snippets per session along with the session row. Use this when the user remembers a phrase or topic, not a title.

Step 2 , pull full context from a specific session

scripts/show_session.py <path-from-step-1>       # full conversation
scripts/show_session.py <path> --grep "logo"     # only turns mentioning "logo" (with ±1 surrounding turn)
scripts/show_session.py <path> --tail 20         # last 20 turns

The script strips tool calls/results and renders user + assistant text only. Output is markdown-ish; pipe to a pager if long.

Filter reference

find_sessions.py flags:

--kind {code,cowork,all} , default all
--since YYYY-MM-DD, --until YYYY-MM-DD , by last-activity mtime
--title TEXT , substring, case-insensitive (Cowork uses the stored title; Code uses the first user message)
--cwd TEXT , substring match against the working directory recorded in Code transcripts
--grep PATTERN , regex across transcript body
-n, --limit N , cap results (default 50, 0 = all)
--snippets N , how many matching lines to show per session under --grep (default 2)
--json , machine-readable output

Tips

If the user's description is vague, run --grep with 2–3 alternative phrasings in parallel before narrowing.
For Code sessions the "title" is a best-effort extraction of the first user message; for Cowork it comes from the .json sidecar written by the desktop app.
A session can have many transcripts (resumes, forks). find_sessions.py lists each transcript separately; that's usually what you want , the most recent one is the live thread.
Transcripts can be large (several MB). When dumping content to the user, prefer show_session.py --grep or --tail over the full file.