scout

Help the user set up a Yutori Scout for continuous web monitoring.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "scout" with this command: npx skills add yutori-ai/yutori-mcp/yutori-ai-yutori-mcp-scout

Scout Setup

Help the user set up a Yutori Scout for continuous web monitoring.

Process

Understand the monitoring context Ask about:

  • Who is monitoring and why? (e.g., "We're a fintech looking for recently funded startups")

  • What specific information matters? (funding events, product launches, pricing changes)

  • What geography or market segments?

  • How often should it run? (daily, twice daily)

  • Notification preference: email, webhook, or both?

Craft a comprehensive query

A well-structured scout query includes:

Context on the monitoring goal:

  • Who is doing the monitoring and what's the use case

  • What decisions this information supports

What to Monitor:

  • Specific events/triggers to track

  • Data sources to check (news sites, SEC filings, social media, etc.)

  • Geographic or segment focus

  • Exclusion criteria (what NOT to report)

Deliverables:

  • Frequency of reports

  • Output format (tables, narrative, both)

  • Required fields and citations

Example structure:

Context: [Who is monitoring and why]

What to Monitor

  • [Specific events to track]
  • [Sources to check]
  • [Exclusions]

Deliverables

  • [Output format]

  • [Required fields]

Create the scout Use the create_scout tool with:

  • query : The comprehensive monitoring query

  • output_interval : 86400 (daily), 43200 (twice daily), or 1800 (minimum, every 30 min)

  • webhook_url and webhook_format if they want webhook notifications

  • skip_email: true if they only want webhooks

  • output_fields : For structured data extraction (e.g., ["company", "amount", "round_type", "source_url"])

Provide next steps

  • Share the scout ID for future management

  • Explain how to pause/resume with edit_scout

  • Mention they can get updates with get_scout_updates

Query Quality Tips

Good queries:

  • Provide context on who is monitoring and why

  • Specify exact events/triggers (not just "news about X")

  • List data sources to check

  • Include exclusion criteria

  • Define output format expectations

  • Request citations and source links

Avoid:

  • Vague queries like "monitor competitor X"

  • Missing context about the monitoring goal

  • No output format specification

$ARGUMENTS

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

yutori competitor-watch

No summary provided by upstream source.

Repository SourceNeeds Review
General

yutori-scout

No summary provided by upstream source.

Repository SourceNeeds Review
General

yutori api-monitor

No summary provided by upstream source.

Repository SourceNeeds Review
General

yutori browse

No summary provided by upstream source.

Repository SourceNeeds Review