Update to A-Z Links: Easily view sources

{
  "description": "Prepare an audience-specific Links resource handoff when the user wants to brief a teammate, onboard someone, or share project resources with a clear starting point. Select essentials, explain their relevance, and draft a short introduction. Use for preparing the handoff, not sending messages, publishing a shared collection, or building a learning curriculum.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 261
    }
  ],
  "name": "prepare-resource-handoff",
  "skill_md_contents": "---\nname: prepare-resource-handoff\ndescription: \"Prepare an audience-specific Links resource handoff when the user wants to brief a teammate, onboard someone, or share project resources with a clear starting point. Select essentials, explain their relevance, and draft a short introduction. Use for preparing the handoff, not sending messages, publishing a shared collection, or building a learning curriculum.\"\n---\n\n# Prepare Resource Handoff\n\nMake a resource collection understandable and actionable for its intended\nrecipient.\n\n## Inputs\n\n- Obtain the recipient's role or audience, the handoff purpose, and what the\n  recipient needs to do with the resources.\n- Use supplied links or the latest model-visible `modelContent.links`. If\n  referenced widget edits are unavailable, request the current links.\n- Use the user's project context and resource summaries. Ask for missing\n  audience or purpose information only when it affects the selection.\n\n## Workflow\n\n1. Define the recipient's first useful action and the context they need to take\n   it. Use a stated assumption for minor gaps instead of a long questionnaire.\n2. Select essential resources for that action. Preserve resources the user\n   marks mandatory and distinguish optional background. Explain meaningful\n   exclusions in the companion note.\n3. Arrange resources so the starting point comes first, followed by working\n   materials and supporting references. Use the supplied context to explain\n   the order; do not claim to know hidden pin state or the recipient's progress.\n4. Preserve useful titles and rewrite descriptions to answer why the recipient\n   needs each resource, what to look for, and what to do next. Keep ownership,\n   access requirements, and deadlines only when supplied or verified.\n5. Inspect destination content through available browsing tools when the\n   handoff depends on unseen details. Otherwise use cautious labels and flag\n   missing context. Do not claim that the recipient can access a private page\n   or that a link has been tested merely because its syntax is valid.\n6. Draft a short introduction stating the purpose, the starting resource, and\n   the requested next action. Choose Markdown for a document or knowledge base,\n   plain text for a simple message, or bookmark HTML for a browser collection,\n   according to the user's destination.\n7. Deliver the recipient-oriented collection, the introduction, and any\n   material access or context gaps. Keep the introduction outside the tool\n   arguments because Links has no collection-level title or message field.\n\n## Publish with Links\n\nCall `links` once with the selected ordered HTTP(S) entries, each containing\nstring `url`, `title`, and `description` fields, and an optional brief `reason`.\nTreat `{ links }` as an echo, not confirmation of delivery or page access.\n\nExplain that this creates a new collection. Guide the user to review the saved\ncards and choose the desired format from Share. Do not send an email or chat\nmessage, control the clipboard, generate a shared collection URL, or claim\nthat another person received the handoff.\n\nRespect requests for text only or no tools by returning the prepared handoff\nin text. If no usable resources are available, request them rather than\npublishing an empty collection or inventing project links.\n"
}