find

Locate prior coding agent sessions using partial user-provided clues.

6|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/GeekKingCloud/skills --skill find-geekkingcloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: find
Source: https://github.com/GeekKingCloud/skills/tree/main/find
Command: npx skills add https://github.com/GeekKingCloud/skills --skill find-geekkingcloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the common frustration of losing track of past coding agent conversations when you only remember vague details like a topic, error message, or date, eliminating the need to manually scroll through hours of chat history to find the right session.

Core Features & Use Cases

  • Multi-clue session search: Look up past conversations using topic, project, date range, file path, command, error text, person, PR, issue, or any remembered fragment.
  • Evidence-ranked results: Returns the most likely match first, with alternate candidates and confidence scores when the match is ambiguous, so you can quickly identify the correct session.
  • Use case: If you need to resume work on a payment integration bug you started 3 days ago but can't recall the exact session name, search for "payment integration error" or the specific error text you encountered to get the exact session ID and resume handle in seconds.

Quick Start

Use the find skill to locate the coding agent session where you fixed the user login redirect bug last Tuesday.

Frequently Asked Questions about find

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find a past coding agent session using only a partial error message?

You can find a past coding agent session by providing partial clues like error text, topic, or file path. The Skill searches this fragment against your history, returning ranked candidate sessions with verified metadata and confidence scores to identify the correct match.

What is the best way to locate an interrupted debugging conversation from last week?

The best way to locate an interrupted debugging conversation is searching by date range or topic. The Skill retrieves prior implementation context without manual history traversal, returning the exact session ID and resume handle instantly.

Can I search my coding agent history using a specific file path or command?

Yes, you can search your coding agent history using a specific file path or command. The Skill accepts multiple clue types including project names, issue references, and remembered fragments to disambiguate and locate exact past sessions.

How do I resume a coding agent session after finding the right conversation?

To resume a coding agent session, the Skill provides a verified resume handle alongside the session ID in the search results. This handle allows you to directly continue your previous development workflow from the exact interruption point.

Does the session search return results if I only remember a vague topic fragment?

Yes, session search works with vague topic fragments. The Skill uses evidence-ranked results, returning the most likely match first alongside alternate candidates and confidence scores to help you disambiguate uncertain matches and quickly identify the correct session.