jieli-findlisted

# Jieli Find ## When to Use Use this skill immediately when: - The user asks to find/search previous Jieli threads. - The user asks which thread mentioned something. - The user gives keywords, repo names, file paths, topics, labels, or vague clues instead of a known thread id. Do not use this skill when the user already supplied a specific Jieli thread id or URL. Use `jieli-read` for known thread ids/URLs. ## Inputs - Search keywords or clue text. - Optional explicit filters from the user, such as repo, label, page size, page, sort, or provider. - Jieli credentials from `JIELI_API_KEY` or `~/.config/jieli/settings.json`. - Jieli uses `https://jieli.app` by default; no base URL configuration is needed for hosted Jieli. ## Environment Use the `jieli-find-threads` command for thread search. It is installed from the plugin `bin/` directory and resolves the plugin scripts path itself. Do not duplicate raw `curl` calls unless you are diagnosing the helper. If the API key is missing, ask the user for a Jieli API key and write it to `~/.config/jieli/settings.json` with mode `600`. ## Search Procedure 1. Build the shortest useful search query from the user's clue. Keep file paths, repo names, branch names, error text, or topic words intact. 2. Search all providers by default: ```bash jieli-find-threads "<query>" --page-size 10 --sort updated ``` 3. Do not pass --provider based on the current agent. Do not set `--provider codex` merely because you are Codex, and do not set