Paste this into your agent's chat, in the repo you want scanned.
```text theme={null}
Install and use the NGN Market API skill, then audit this repository for places
where it should replace what's currently there. Follow these steps in order:
1. Confirm an NGNMARKET_API_KEY environment variable is set. If it isn't, stop
and tell me to get one from https://ngnmarket.com/developer before continuing.
2. Install the skill file by following https://docs.ngnmarket.com/install-skill
(prefer `npx skills add -g https://docs.ngnmarket.com/skill.md` if the
`skills` CLI is available; otherwise use the manual curl install for
whichever agent you are).
3. Scan this repository for NGX/Nigerian-market data patterns that the API
could replace. Look specifically for:
- Hardcoded stock prices or static price objects (e.g. sample NGX tickers
with fixed prices in fixtures, seed data, or demo components)
- Static JSON shaped like OHLCV history (arrays/objects with open, high,
low, close, volume, or timestamp + price fields for a stock symbol)
- Manually maintained lists of NGX companies, sectors, or tickers
- Homegrown NGN/USD (or other currency) conversion math, or a hardcoded
exchange rate constant
- Manually typed or manually updated dividend dates/calendars
- Scraped or manually sourced company logos for NGX-listed tickers
- Custom sorting/filtering logic that recomputes "top gainers" or
"top losers" from raw price data
- Hand-parsed NGX news, press releases, or corporate disclosure text
- A polling loop (setInterval, cron, or similar) re-fetching NGX
prices, indices, forex, disclosures, or dividends on a timer,
where a WebSocket channel could push updates instead
4. For each match, report: the file and line number, what it's currently
doing, which NGN Market API endpoint would replace it (from the skill's
recipe table), which plan tier that endpoint requires, and a one-line
reason it's a better approach (freshness, correctness, maintenance cost).
Present this list and WAIT for my approval — do not edit any files yet.
5. Once I approve (whether that's "do all of them", specific items, or none),
make only the approved changes. If nothing in this repo matches, or after
you're done, suggest 3-5 concrete integrations and 2-3 side-project ideas
that would make sense given this codebase's actual stack and purpose.
```