Menu
Set up monitoring for API changes, changelogs, or documentation updates. Useful for tracking breaking changes in services you depend on.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Execute deep web research on any topic using Yutori's research agents. Use for competitive analysis, market research, finding documentation, or answering complex questions that require synthesizing information from multiple sources.
Automate browser tasks like form filling, data extraction, or multi-step web workflows. Use when the user needs to interact with websites that require clicking, typing, or navigation.
Log in to Yutori to connect your account
Set up continuous web monitoring with Yutori Scouts. Use when the user wants to track news, competitors, product updates, funding rounds, price changes, or any recurring web information.
Quickly set up monitoring for a competitor company. Tracks news, product updates, funding, and public announcements.
Based on SOC occupation classification
| name | yutori-api-monitor |
| description | Set up monitoring for API changes, changelogs, or documentation updates. Useful for tracking breaking changes in services you depend on. |
| argument-hint | [service or API name] |
| disable-model-invocation | true |
Set up monitoring for API or service changes.
Create a scout with this query structure:
**Context:** Monitoring API stability and changes for $ARGUMENTS to ensure our integration stays up-to-date.
## What to Monitor
- **Breaking Changes:** API version changes, deprecated endpoints, removed features
- **New Features:** New endpoints, parameters, capabilities
- **Rate Limits & Quotas:** Changes to limits, pricing tier updates
- **Deprecation Notices:** Sunset timelines, migration guides
- **Security Updates:** Authentication changes, security advisories
**Sources to check:** Official changelog, documentation, developer blog, GitHub releases, status page, developer Twitter/X account
**Exclusions:** Minor bug fixes, internal refactoring, documentation typos
## Deliverables
**Frequency:** Every 12 hours
**Output format:**
1. **URGENT** section for breaking changes (if any)
2. Table of changes: Date, Type (breaking/feature/deprecation), Description, Migration Required (yes/no), Source Link
3. Recommended actions for each change
Use create_scout with:
query: The above structured query with $ARGUMENTS replacedoutput_interval: 43200 (every 12 hours)After creation, explain:
Fetching API documentation or changelogs:
If you use a web fetch tool to look up the service's changelog, API reference, or developer docs while preparing the query, include the Accept: text/markdown header. Many developer documentation sites (Cloudflare-hosted) will return clean Markdown instead of HTML — fewer tokens, easier to parse.