Update to You.com

{
  "description": "Route research tasks between a cost-conscious agentic search workflow, You.com Research API scripts, and managed or payment-aware MCP fallback.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 680
    },
    {
      "relative_path": "references/agent-led-deep-search.md",
      "size_in_bytes": 3677
    }
  ],
  "name": "you-research",
  "skill_md_contents": "---\nname: you-research\ndescription: Route research tasks between a cost-conscious agentic search workflow, You.com Research API scripts, and managed or payment-aware MCP fallback.\ncompatibility: Requires network access and either You.com MCP tools with `YDC_API_KEY`, OAuth, or payment support, or the You.com Research API with `YDC_API_KEY` or an MPP/x402-capable client.\nlicense: MIT\n---\n\n# You.com Research Routing\n\nUse this skill to choose the right You.com research path for the user's goal: agent-led search, Research API scripts, or managed MCP fallback.\n\n## Prerequisites\n\nFor API scripts:\n\n- Use `YDC_API_KEY` when available, or an MPP/x402-capable HTTP client for keyless paid Research API calls.\n- With `YDC_API_KEY`, use these API request headers: `X-API-Key: ${YDC_API_KEY}` and `User-Agent: SKILL/(@youdotcom-oss/agent-skills you-research)`.\n- With MPP/x402, expect Research API pricing by `research_effort` and at least a 1 cent charge; confirm the user expects a paid managed research request before sending it.\n\nFor the agent-led workflow, use the `you-research-base` MCP profile with `you-search` and `you-contents` when available. Those tools and their REST endpoints should use x402 for keyless paid retries, not MPP. See the [agent-led deep-search workflow](references/agent-led-deep-search.md) for setup and workflow details.\n\nMPP/x402-aware MCP or HTTP clients may receive HTTP `402` payment challenges from You.com tools and endpoints, then retry with payment headers. Use MPP/x402 for managed Research API calls where appropriate. Let the host client handle external payment and retry; do not add wallet signing logic to this skill.\n\n## Research API scripts\n\nWhen the user wants You.com managed research APIs, write a small script or direct HTTP request instead of calling `you-research` through MCP, especially for `deep`, `exhaustive`, or `frontier` work.\n\nBefore coding or updating a script, query the You.com Docs MCP server, usually through `searchDocs`, for current API details. Use targeted queries such as:\n\n- `Research API v1 research background source_control output_schema research_effort`\n- `Research task status v1 research task`\n- `Research task stream SSE v1 research task stream`\n\nIf Docs MCP is unavailable, use the canonical pages:\n\n- https://you.com/docs/api-reference/research/v1-research\n- https://you.com/docs/api-reference/research/v1-research-task\n- https://you.com/docs/api-reference/research/v1-research-task-stream\n\nKeep the script aligned with the docs returned at runtime and include the auth or payment headers listed above. If the user wants keyless MPP/x402 direct HTTP usage for Research API, verify current payment guidance in Docs MCP first, then handle `402 payment-required` as a challenge and retry only through a payment-capable client or library. Do not apply MPP guidance to plain search or contents REST calls; those should use x402 only.\n\n## Decision Tree\n\n- User is cost-conscious or wants to develop/fine-tune a research skill -> follow the [agent-led deep-search workflow](references/agent-led-deep-search.md).\n- User asks for You.com managed API output, structured output, source controls, background tasks, or `deep`/`exhaustive`/`frontier` research -> write a script against the Research API.\n- User needs OAuth or MPP/x402 payment handling and direct API scripts are not practical -> use MCP only if the MCP client supports the expected response time and payment flow.\n- Simple lookup -> use `you-research-base` `you-search` once, answer directly.\n- URL provided -> use `you-research-base` `you-contents` on those URLs.\n- Everything else -> use the base agent-led workflow.\n\n## Agent-led workflow reference\n\nWhen choosing the cost-conscious skill-building path, open and follow the [agent-led deep-search workflow](references/agent-led-deep-search.md). Adapt its tool budget, source policy, and output format to the user's agent environment. Preserve its core requirements: read sources before relying on exact claims, cross-check key facts, cite real URLs, and finish with the best supported answer even when evidence is incomplete.\n"
}