Before you run a prompt
Connect a supported client through MCP installation, then give it an API key from the environment or secret store that actually runs the client. Do not paste a key into the prompt. Start with one issuer and one prompt. A useful first result names the form, filing date, accession number, section or fact reference, source URL, and request ID when returned. These prompts assemble factual briefing material; they do not decide materiality or messaging. Keep source filings next to client-facing claims, separate verified facts from open questions, and stop on auth, validation, billing, quota, or capability errors.Working rules
filings.searchandsections.searchdo not apply an MCP date window. Filter returnedfilingDatevalues before you assemble the briefing.- Preserve the issuer’s terms. Do not turn a disclosed event, vote, or transaction into a motive, sentiment signal, or governance judgment.
- Keep verified facts, open questions, and proposed messaging in separate sections.
1. Vote-results client brief
Prompt id:pr-firm-voting-results-narrative
2. Material-event monitoring digest
Prompt id:pr-firm-8k-material-event-monitoring
3. Executive-transition briefing
Prompt id:pr-firm-executive-transition-detection
4. Peer event context
Prompt id:pr-firm-peer-comparison-context
5. Quiet-period transaction facts
Prompt id:pr-firm-quiet-period-trading-watch
6. Acquisition announcement context
Prompt id:pr-firm-acquisition-announcement-context
7. Release-to-filing cross-check
Prompt id:pr-firm-press-release-disclosure-cross-check
8. Earnings announcement source pack
Prompt id:pr-firm-results-announcement-prep
9. Shareholder-meeting narrative record
Prompt id:pr-firm-shareholder-meeting-narrative
10. Board-change watchlist
Prompt id:pr-firm-board-composition-change
11. Segment roadshow source note
Prompt id:pr-firm-segment-disclosure-narrative
12. Stakeholder-context briefing
Prompt id:pr-firm-stakeholder-sentiment-pulse

