Who it is forA new self-publisher who wants to earn from Kindle books but does not know which niche or format to start with.
The problemChoosing a niche, format and budget without research or a clear test is slow and often leads to guesswork.
The outcomeA goal summary, five researched niche choices, one selected book idea, a reader promise and a costed first experiment.
What you need first
- A supported AI assistant host, such as ChatGPT Work, Codex, Claude Cowork, Kimi Work, OpenClaw or Hermes Agent
- The Beyondwords skill installed through the route in docs/INSTALL.md
- An Amazon KDP account for publishing your own books
- Authorized Amazon Sponsored Products API access only if you want connected advertising
- A stated goal, budget, available time and country
Steps
- Open docs/INSTALL.md and follow the route for your assistant host, then keep the complete skill folder.
- Start a conversation and state your goal, timeframe, budget, available time, country, language and any existing skills.
- Ask for five researched niches with an idea for each, or five ideas inside a niche you choose.
- Review the gaps and contrary evidence for each option, then choose one niche and book idea.
- Agree the reader promise, format, budget and workload for the first experiment before any production starts.
Prompt for your agent
Use the Beyondwords skill from the repo beyondtahir/beyondwords. My target is <monthly profit goal>, budget <budget>, and I have <hours per week> hours per week. Return the goal summary, five researched niches with one book idea each, and a costed first experiment. Verify that the experiment states its budget and workload and does not promise earnings.
Caveat. The README says earnings depend on the books, readers, costs and execution and are never guaranteed, so the plan is only a researched starting point.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page