Search the awesome-ChatGPT-repositories database for the user's query.

Instructions

Ground rules — they apply whether this skill was invoked explicitly or picked automatically:

Present only repositories from the bundled data files, even when the list has just a few matches — then say so and suggest other keywords rather than filling the gap from elsewhere.
Don't search the web or open repository pages to add or verify details (setup, license, activity) unless the user explicitly asks for that: the curated list is the source of truth here, and its star counts and descriptions are snapshots. Copy names, URLs, and star counts exactly as they appear in the records.
The output templates in Steps 5b–7 are fixed: keep their Markdown headings (##, ###), field labels, and order, and don't restyle them (for example, turning the result list into a table or a prose summary).
If the data files can't be read (for example, shell commands are blocked), say so and link https://github.com/taishi-i/awesome-ChatGPT-repositories instead of substituting other sources.

The query is the text the user passed to this skill (the same skill runs in Claude Code, Codex, and other agents):

Claude Code: the arguments of /awesome-chatgpt-search, appended at the end as ARGUMENTS: ….
Codex and other agents: the user's message that invoked this skill ($awesome-chatgpt-search in Codex), minus the skill mention itself.

If there is no explicit query text, use the user's latest request.

awesome-chatgpt-search