← The Fly Market IntelligenceCONTENT HISTORY

Update to The Fly Market Intelligence

Snapshot Sep 30, 2026 · 22:50 UTC · version 1.0.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "name": "the-fly-stock-screening",
  "description": "Rank stocks by market capitalization with The Fly Market Intelligence and optionally research selected results. Use for bounded market-cap ranking requests. Do not invent unsupported filters, alter portfolios, execute trades, or treat screening output as a recommendation.",
  "included_files": [],
  "skill_md_contents": "---\nname: the-fly-stock-screening\ndescription: Rank stocks by market capitalization with The Fly Market Intelligence and optionally research selected results. Use for bounded market-cap ranking requests. Do not invent unsupported filters, alter portfolios, execute trades, or treat screening output as a recommendation.\n---\n\n# The Fly stock screening\n\nUse `screen_stocks` to produce a bounded market-cap-ranked shortlist, then research only the names the user selects or the small number required by the request.\n\n## Procedure\n\n1. The submitted ChatGPT tool supports only `sortBy: \"market_cap\"`. If the user asks for sector, valuation, growth, or other filtering, explain that this v1 tool cannot apply that filter instead of inventing one.\n2. Always bound the request with `page` and `pageSize`; use a small page size for conversational use.\n3. Use the typed ChatGPT request shape. Example descending market-cap ordering:\n\n```json\n{\n  \"sortBy\": \"market_cap\",\n  \"direction\": \"desc\",\n  \"page\": 1,\n  \"pageSize\": 5\n}\n```\n\n4. Report the market-cap sort direction and page bounds alongside the shortlist.\n5. Use `research_company` only for the final selected names, not every row in a broad screen.\n\n## Interpretation rules\n\n- Treat screener values as point-in-time market data and retain relevant dates when available.\n- Highlight only fields actually returned by the tool; do not infer missing sector, valuation, growth, yield, return, or leverage filters.\n- Do not claim the screen is exhaustive when pagination or selection caps apply.\n- A screen is research output, not a recommendation or trade instruction.\n"
}

SHA-256: 7b124b3a65364a8d5996d8c18bc71714dea86103e9e9f598aa2af43cd76fbc76