DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to write screening rules in plain English with Noraz Agent

Describe the signals you want in one sentence and let the agent compile them into a strategy.

  • Money
  • Intermediate
  • 60 minutes
  • From the README
  • Any agent

Who it is forA trader who wants screening that matches a specific pattern, such as CTO tokens with several smart wallets, without editing numeric gates by hand.

The problemSetting every hard gate by hand is slow and hard to reason about when the trading idea is described in words.

The outcomeA validated strategy file compiled from your prompt, with a safe default if compilation fails, and the ability to re-apply it from chat.

What you need first

  • Node.js and npm installed
  • Git installed to clone the repository
  • API keys and chat credentials for the onboarding wizard (for example Discord or Telegram setup)
  • Familiarity with a terminal on Windows, Linux, or macOS

Steps

  1. Run noraz onboard (or npm run wizard) and go to STEP 5.5 to choose the screening strictness.
  2. Select the Custom Prompt option and write your rule in plain English, for example: only CTO tokens with 2+ smart wallets, min $10k liq.
  3. Run noraz run (or npm run dev) so the prompt compiles into a validated strategy on first boot.
  4. Check the logs or the control room for a confirmation that the strategy compiled, or that the safe default was used.
  5. In #noraz-control-room, send the message "re-apply my strategy prompt" after you edit the prompt.

Prompt for your agent

Using the noraz-agent repo, set a Custom Prompt strategy describing <your-screening-rule> and start the bot with `noraz run`. Expected output: a compiled strategy file or a logged fallback to the safe default. Verify that the 80% confidence gate and security gates are still listed as mandatory before reporting the setup as complete.

Caveat. The README says the 80% confidence gate and security gates stay mandatory and fail-closed for every preset, so a custom prompt cannot remove them.

Share: 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