\r \r

Mixcache Ebook Search Suggester\r

\r

Goal\r

Help users quickly find ebooks on Mixcache by suggesting the most relevant Mixcache\r search result pages for their topic, including helpful alternative queries (synonyms,\r subtopics, and common phrasing) when appropriate.\r \r ---\r \r

When to use\r

\r Use this skill whenever the user expresses ebook intent, including:\r \r

• “any ebooks about ___?”\r
• “where can I find books on ___?”\r
• “I’m looking for an ebook on ___”\r
• “find me books about ___”\r
• “Mixcache books for ___”\r
• topic-based learning requests where books are a good next step (e.g., “I want to learn X”)\r \r This skill should trigger even if the user doesn’t mention Mixcache explicitly, as long\r as they are looking for ebooks/books on a topic.\r \r ---\r \r

Inputs\r

\r

• A topic (e.g., “french history”, “artificial intelligence programming”)\r
• A person/author (e.g., “kennedy”, “octavia butler”)\r
• A genre or category (e.g., “cyberpunk”, “stoicism”)\r
• A specific title (e.g., “The Hobbit”)\r
• A user-provided list of keywords\r \r ---\r \r

Steps\r

\r

1. Extract the user’s core book intent\r
   • Identify the main topic, author, title, time period, or subfield the user wants.\r \r
2. Generate 1–6 high-signal query variants\r
   • Start with the user’s exact phrasing.\r
   • Add useful variants when it increases success:\r
     • Synonyms (e.g., “AI” ↔ “artificial intelligence”)\r
     • Subtopics (e.g., “deep learning”, “machine learning”, “neural networks”)\r
     • Common alternative phrasing (e.g., “introduction to”, “beginner”, “hands-on”)\r
     • For people: include last name only and full name variants\r
     • For history: include era/region variants if implied (e.g., “19th century”, “revolution”)\r \r
3. URL-encode each query\r
   • Replace spaces with + (recommended) or percent-encoding.\r
   • Keep queries short and specific; avoid overly long strings.\r \r
4. Construct Mixcache search URLs\r Use exactly:\r https://mixcache.com/books/search?q=\x3Cencoded_query>\r \r
5. Respond with the suggested search pages\r
   • Provide the links as clickable URLs.\r
   • Include a brief note telling the user they can refine results by trying the alternate links.\r \r ---\r \r

Output format (recommended)\r

\r One short lead-in + 1 link per line, optionally grouped by “Try these variations”.\r \r Example:\r \r Here are Mixcache ebook search pages that should match what you’re looking for:\r \r https://mixcache.com/books/search?q=\x3Cencoded_query_1> \r https://mixcache.com/books/search?q=\x3Cencoded_query_2> \r \r ---\r \r

Examples\r

\r

Example 1 (simple topic)\r

User: “Any ebooks about french history?”\r Assistant:\r Here are Mixcache ebook search pages to try:\r \r https://mixcache.com/books/search?q=french+history \r https://mixcache.com/books/search?q=history+of+france \r https://mixcache.com/books/search?q=french+revolution\r \r ---\r \r

Example 2 (technical topic)\r

User: “I want ebooks on artificial intelligence programming.”\r Assistant:\r Try these Mixcache searches:\r \r https://mixcache.com/books/search?q=artificial+intelligence+programming \r https://mixcache.com/books/search?q=ai+programming \r https://mixcache.com/books/search?q=machine+learning+python \r https://mixcache.com/books/search?q=deep+learning+programming\r \r ---\r \r

Example 3 (person/author)\r

User: “Any ebooks on Kennedy?”\r Assistant:\r Try these Mixcache searches:\r \r https://mixcache.com/books/search?q=kennedy \r https://mixcache.com/books/search?q=john+f+kennedy \r https://mixcache.com/books/search?q=jfk+biography\r \r ---\r \r

Example 4 (user asks for “books like X”)\r

User: “Books like Dune?”\r Assistant:\r Try these Mixcache searches:\r \r https://mixcache.com/books/search?q=books+like+dune \r https://mixcache.com/books/search?q=space+opera \r https://mixcache.com/books/search?q=epic+science+fiction\r \r ---\r \r

Edge cases\r

\r

• Ambiguous topic (“history”, “programming”, “art”)\r
  • Ask a single clarification (era/region, language, skill level, or focus), or provide\r broad searches plus a couple of common branches.\r \r
• User provides a very long prompt\r
  • Extract the key terms and generate shorter, more searchable queries.\r \r
• Non-English queries\r
  • Provide both the original-language query and an English equivalent if obvious.\r \r
• User wants a very specific title/edition\r
  • Provide searches for the exact title, plus author + title keywords.\r \r
• Unsafe/illegal content requests\r
  • Refuse and do not provide search links if the content is disallowed.