[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DA2YXJ384EVWJX6RPHDZ9R":3,"skill-same:01M6DA2YXJ384EVWJX6RPHDZ9R":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M6DA2YXJ384EVWJX6RPHDZ9R","scion-conversation",null,"How to use the scion conversation command for managing conversations. Covers listing, creating, viewing, participant management, and message retrieval. Complements the scion-messaging skill.","GoogleCloudPlatform\u002Fscion","GoogleCloudPlatform","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2810941?v=4","01M6DA2FX07AS0KCQ4FBRS84A2","Google Cloud Platform","01M6DA2G1EA6A2E5MKG6THG0KK",2114,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FGoogleCloudPlatform\u002Fscion\u002Fblob\u002Fmain\u002Fresources\u002Fplatform_skills\u002Fscion-conversation\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31],"conversation","scion conversation","messaging","how","command","management","use","message","how to","retrieval","conversations","for","listing","2026-11-10 10:12:30",false,"---\nname: scion-conversation\ndescription: >-\n  How to use the scion conversation command for managing conversations.\n  Covers listing, creating, viewing, participant management, and message retrieval.\n  Complements the scion-messaging skill.\n---\n\n# Scion Conversation\n\n## Overview\n\nUse `scion conversation` to inspect and manage conversation metadata,\nparticipants, and message history. Conversation commands require Hub mode.\n\nThis command does not send messages. Use `scion message` to write to a\nconversation; see the `scion-messaging` skill for sending and reply-routing\nguidance.\n\n## When to Use\n\n- See which conversations you participate in.\n- Create a group conversation for multi-agent coordination.\n- Read message history or catch up on recent activity.\n- List or add participants, or leave a conversation.\n- Retrieve a specific message by ID.\n\n**When NOT to use:** Do not use `scion conversation` to send messages. Use\n`scion message` for writing into conversations. Avoid creating a conversation\nfor a one-off direct message; send it with `scion message @\u003Cagent-name>` instead.\n\n## Conversation References\n\nConversation subcommands accept three reference formats:\n\n- **`conv:\u003Cuuid>`**: Direct conversation ID. This is the most common form and\n  always works for a conversation you can access.\n- **`@\u003Cagent-name>`**: The direct-message conversation with an agent.\n- **`#\u003Cthread-name>`**: A named thread conversation.\n\nBare UUIDs are not accepted. Always include the `conv:` prefix when addressing\na conversation by ID.\n\n## Functional Capabilities\n\n**Reading:** `list`, `get`, `messages`, `catch-up`, and `get-message` let you\ndiscover accessible conversations, inspect their metadata, and read all,\nrecent, or individual messages. Prefer structured output when another command\nor agent will consume the result.\n\n**Administration:** `create`, `join`, `leave`, `participants`, and\n`set-default` create coordination spaces and manage their membership and\ndefault agent. A conversation name is the positional argument to `create`, not\na `--title` flag. `join` is not idempotent: adding an existing participant\nreturns HTTP 409, so check `participants` first when membership is uncertain.\n\nRun `scion conversation --help` for the full command reference and\n`scion conversation \u003Csubcommand> --help` for authoritative usage, arguments,\nand flags for an individual subcommand.\n\n## Common Patterns\n\n### Reply in the original conversation\n\nRead the inbound envelope's `conversation.id`, add the `conv:` prefix, and send\nthe reply with `scion message`:\n\n```bash\nscion message conv:a1b2c3d4-... \"Reply in the original conversation\"\n```\n\nDo not use `scion conversation` to send the reply. See the `scion-messaging`\nskill for the complete routing rules.\n\n### Create a coordination space\n\n```bash\nscion conversation create \"project-x coordination\" --json\n```\n\nCapture the returned ID and share it as `conv:\u003Cid>` with participants.\n\n### Catch up and manage membership\n\nUse `catch-up` to review recent activity without rereading the full history.\nBefore adding a participant whose membership is uncertain, inspect\n`participants`; call `join` only when they are absent.\n\n## Relationship to `scion message`\n\nThe commands are complementary:\n\n| Goal | Command |\n|---|---|\n| Send into a conversation | `scion message conv:\u003Cid> \"text\"` |\n| Read conversation history | `scion conversation messages conv:\u003Cid>` |\n| Read one message | `scion conversation get-message conv:\u003Cid> \u003Cmessage-id>` |\n| Inspect or administer a conversation | `scion conversation get`, `participants`, `join`, or `leave` |\n\nUse the `scion-messaging` skill for writing and reply routing, including the\nstructured-markdown format required for multi-sentence messages. Use this\nskill for reading and conversation administration.\n\n## Anti-Patterns\n\n- Passing a bare UUID instead of a `conv:\u003Cuuid>` reference; the command rejects\n  bare UUIDs.\n- Trying to send through `scion conversation`; use `scion message` instead.\n- Treating `scion conversation join` as idempotent; an existing participant\n  produces HTTP 409.\n- Creating a conversation for a one-off message; use `scion message @\u003Cagent>`\n  for a direct message.\n","# Scion Conversation\n\n## Overview\n\nUse `scion conversation` to inspect and manage conversation metadata,\nparticipants, and message history. Conversation commands require Hub mode.\n\nThis command does not send messages. Use `scion message` to write to a\nconversation; see the `scion-messaging` skill for sending and reply-routing\nguidance.\n\n## When to Use\n\n- See which conversations you participate in.\n- Create a group conversation for multi-agent coordination.\n- Read message history or catch up on recent activity.\n- List or add participants, or leave a conversation.\n- Retrieve a specific message by ID.\n\n**When NOT to use:** Do not use `scion conversation` to send messages. Use\n`scion message` for writing into conversations. Avoid creating a conversation\nfor a one-off direct message; send it with `scion message @\u003Cagent-name>` instead.\n\n## Conversation References\n\nConversation subcommands accept three reference formats:\n\n- **`conv:\u003Cuuid>`**: Direct conversation ID. This is the most common form and\n  always works for a conversation you can access.\n- **`@\u003Cagent-name>`**: The direct-message conversation with an agent.\n- **`#\u003Cthread-name>`**: A named thread conversation.\n\nBare UUIDs are not accepted. Always include the `conv:` prefix when addressing\na conversation by ID.\n\n## Functional Capabilities\n\n**Reading:** `list`, `get`, `messages`, `catch-up`, and `get-message` let you\ndiscover accessible conversations, inspect their metadata, and read all,\nrecent, or individual messages. Prefer structured output when another command\nor agent will consume the result.\n\n**Administration:** `create`, `join`, `leave`, `participants`, and\n`set-default` create coordination spaces and manage their membership and\ndefault agent. A conversation name is the positional argument to `create`, not\na `--title` flag. `join` is not idempotent: adding an existing participant\nreturns HTTP 409, so check `participants` first when membership is uncertain.\n\nRun `scion conversation --help` for the full command reference and\n`scion conversation \u003Csubcommand> --help` for authoritative usage, arguments,\nand flags for an individual subcommand.\n\n## Common Patterns\n\n### Reply in the original conversation\n\nRead the inbound envelope's `conversation.id`, add the `conv:` prefix, and send\nthe reply with `scion message`:\n\n```bash\nscion message conv:a1b2c3d4-... \"Reply in the original conversation\"\n```\n\nDo not use `scion conversation` to send the reply. See the `scion-messaging`\nskill for the complete routing rules.\n\n### Create a coordination space\n\n```bash\nscion conversation create \"project-x coordination\" --json\n```\n\nCapture the returned ID and share it as `conv:\u003Cid>` with participants.\n\n### Catch up and manage membership\n\nUse `catch-up` to review recent activity without rereading the full history.\nBefore adding a participant whose membership is uncertain, inspect\n`participants`; call `join` only when they are absent.\n\n## Relationship to `scion message`\n\nThe commands are complementary:\n\n| Goal | Command |\n|---|---|\n| Send into a conversation | `scion message conv:\u003Cid> \"text\"` |\n| Read conversation history | `scion conversation messages conv:\u003Cid>` |\n| Read one message | `scion conversation get-message conv:\u003Cid> \u003Cmessage-id>` |\n| Inspect or administer a conversation | `scion conversation get`, `participants`, `join`, or `leave` |\n\nUse the `scion-messaging` skill for writing and reply routing, including the\nstructured-markdown format required for multi-sentence messages. Use this\nskill for reading and conversation administration.\n\n## Anti-Patterns\n\n- Passing a bare UUID instead of a `conv:\u003Cuuid>` reference; the command rejects\n  bare UUIDs.\n- Trying to send through `scion conversation`; use `scion message` instead.\n- Treating `scion conversation join` as idempotent; an existing participant\n  produces HTTP 409.\n- Creating a conversation for a one-off message; use `scion message @\u003Cagent>`\n  for a direct message.\n",{"name":5,"description":7},"main","d2283cad8aa80efb245b118b91c4accb684e287e","resources\u002Fplatform_skills\u002Fscion-conversation",310,"https:\u002F\u002Fgithub.com\u002FGoogleCloudPlatform\u002Fscion","https:\u002F\u002Fgithub.com\u002FGoogleCloudPlatform","https:\u002F\u002Fcloud.google.com","2026-11-13 02:20:49",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add GoogleCloudPlatform\u002Fscion --skill scion-conversation",{"tool":51,"command":52},"bunx","bunx skills add GoogleCloudPlatform\u002Fscion --skill scion-conversation",{"tool":54,"command":55},"pnpm","pnpm dlx skills add GoogleCloudPlatform\u002Fscion --skill scion-conversation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGoogleCloudPlatform\u002Fscion\u002Fblob\u002Fmain\u002Fresources\u002Fplatform_skills\u002Fscion-conversation\u002FSKILL.md",true,[59],{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"agents\u002Fopenai.yaml","REFERENCE","参考文档",82,"https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcyber-securing-azure-with-microsoft-defender\u002Fagents\u002Fopenai.yaml",[66,103,134,156,171,188],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":77,"publishedAt":32},"01M6DA3C2RTK8R5TQ9YZVBYT1D","team-creation","Create or extend scion agent team templates from a high-level description of roles and workflow. Use when the user describes a multi-agent team, panel, crew, pipeline, or any scenario requiring coordinated LLM agents with distinct roles. Also use when adding new roles to an existing team, modifying workflows, or restructuring agent coordination. Produces ready-to-use template directories in .scion\u002Ftemplates\u002F by default, or in a custom path if specified.","https:\u002F\u002Fgithub.com\u002FGoogleCloudPlatform\u002Fscion\u002Fblob\u002Fmain\u002Fresources\u002Fplatform_skills\u002Fteam-creation\u002FSKILL.md",[72],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[78,79,80,81,82,83,25,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102],"creation","team","team creation","ready","pipeline","default","llm agents","workflows","workflow","coordination","roles","create","agent team","template","crew","templates","scenario","multi-agent","user","directories","agent coordination","new","when","path","extend",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":32},"01M6DA385P0S838W8ZXQ7SVDFM","scion-web-serving","How to serve a web page, app, API or other HTTP service from inside your agent so a person or program can reach it through the Hub's port proxy: scion expose and unexpose, the URL to hand over, what the proxy carries, and scion tunnel for full apps. The link serves web protocols only; for a non-HTTP port, point the person to scion tunnel. Use before running scion expose. For web pages and apps, also read references\u002Fweb-apps.md.","https:\u002F\u002Fgithub.com\u002FGoogleCloudPlatform\u002Fscion\u002Fblob\u002Fmain\u002Fresources\u002Fplatform_skills\u002Fscion-web-serving\u002FSKILL.md",[],[110,111,112,113,114,115,116,22,117,118,119,120,121,122,123,124,25,125,126,127,128,129,30,27,130,131,132,133],"scion web serving","web","serving","app","references","what the","protocols","proxy","page","hub","read","pages","tunnel","only","service","http","full","api","running","point","apps","URL","program","hand",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":32},"01M6DA35JGKREZP9ZM2ZYH0J7M","scion-scheduler","Schedule one-shot and recurring events for agents using the Scion CLI. Covers when to use scheduled events vs inline message delays, recurring cron schedules, lifecycle management, and the blocked-wait pairing rule.","https:\u002F\u002Fgithub.com\u002FGoogleCloudPlatform\u002Fscion\u002Fblob\u002Fmain\u002Fresources\u002Fplatform_skills\u002Fscion-scheduler\u002FSKILL.md",[],[141,142,143,26,144,145,25,24,146,147,30,148,149,100,150,151,152,153,154,155],"scheduler","scion scheduler","recurring","cli","lifecycle","schedule","cron","schedules","scheduled","inline","when to use","rule","wait","pairing","events",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":32},"01M6DA328HMWYY0R65MVVJJG3S","scion-messaging","Use when sending messages to users or agents with scion message, choosing conversations and mentions, or interpreting incoming messages. Covers user-facing formatting, agent delivery, and reading conversation history.","https:\u002F\u002Fgithub.com\u002FGoogleCloudPlatform\u002Fscion\u002Fblob\u002Fmain\u002Fresources\u002Fplatform_skills\u002Fscion-messaging\u002FSKILL.md",[],[21,163,25,26,19,164,165,29,166,167,168,169,170,96,100],"scion messaging","delivery","history","messages","users","with","reading","formatting",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":177,"publishedAt":32},"01M6DA2WCR1XJK9A3NSV2VGP56","scion-cli-operations","Operational constraints for Scion agents running in containerized sandboxes. Covers prohibited commands and hub-only API access. Complements the scion CLI reference and messaging skills.","https:\u002F\u002Fgithub.com\u002FGoogleCloudPlatform\u002Fscion\u002Fblob\u002Fmain\u002Fresources\u002Fplatform_skills\u002Fscion-cli-operations\u002FSKILL.md",[],[144,178,179,21,119,180,123,181,182,127,183,128,30,184,185,186,187],"operations","scion cli operations","commands","reference","access","constraints","cli reference","sandboxes","operational constraints","containerized",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":195,"publishedAt":32},"01M6DA2SNFM7QDR29R12HZGNQH","scion-agent-manage","Manage concurrent LLM-based code agents with scion - orchestrate parallel agents with isolated workspaces, troubleshoot and recover stuck agents","https:\u002F\u002Fgithub.com\u002FGoogleCloudPlatform\u002Fscion\u002Fblob\u002Fmain\u002Fresources\u002Fplatform_skills\u002Fscion-agent-manage\u002FSKILL.md",[194],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},[196,197,198,199,200,201,202,203,204,168],"manage","scion agent manage","parallel","orchestrate","workspaces","troubleshoot","parallel agents","code","code agents"]