[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6R5K5MFAESZPXCG9NS2K9JR":3,"skill-same:01M6R5K5MFAESZPXCG9NS2K9JR":132},{"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":42,"ownerHtmlUrl":43,"ownerBlogUrl":42,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M6R5K5MFAESZPXCG9NS2K9JR","google-calendar",null,"Read a selected Google Calendar's bounded events or free\u002Fbusy window through a governed connection, preserving coverage and time semantics for downstream planning.","runxhq\u002Frunx","runxhq","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F278566904?v=4","01M6R54JKTWZNT4VQZ0K0DZ7V2","runx","01M6R54JRGDE4MDVDDR0E9MN0K",103,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Frunxhq\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-calendar\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31],"google calendar","calendar","google","coverage","planning","for","time","free","window","read","connection","events","bounded","2026-11-10 10:12:30",false,"---\nname: google-calendar\ndescription: Read a selected Google Calendar's bounded events or free\u002Fbusy window through a governed connection, preserving coverage and time semantics for downstream planning.\n---\n# Google Calendar\n\nUse this skill when a decision needs current events or busy intervals from a Google calendar the operator has explicitly selected. The default `events` method reads expanded event instances; `freebusy` reads only busy intervals. Both are read-only `google-calendar` connector operations with an exact calendar target and a positive, explicitly bounded time window. They cannot create, edit, delete, RSVP to, or invite anyone to events.\n\nThe portable skill owns Calendar evidence semantics, not credentials or connector selection. A local, self-hosted, third-party, or Runx-hosted connector is compatible when it implements the declared operations and scopes. Keep connection identifiers, credentials, tenant details and private calendar choices in the operator's binding and inputs, never in this package.\n\n## Choose a bounded read\n\nAuthorize the intended Google account for `events.read` and\u002For `freebusy.read`. The hosted Google binding requests `calendar.events.readonly` for event details and `calendar.events.freebusy` for busy-only reads; Analytics or Search Console access does not grant Calendar access. Supply the exact calendar ID plus start and end instants with explicit UTC offsets. `primary` selects the connected account's primary calendar. For multiple calendars, run the selected IDs separately and preserve each result's coverage.\n\nThe `events` method expands recurrence and reads one result page. `calendar_id` defaults to `primary`; select another exact ID when needed. Choose `page_size` for the bounded operation (100 by default, up to Google’s 2,500-event page maximum), and use its returned cursor to read any remaining events in the same window. This is a per-call work budget, not a limit on the number of events or the duration you can inspect. Use `freebusy` when only availability is relevant, so event titles are not collected. A live method returns provider readback; `normalize-supplied` only normalizes already collected bytes and says `supplied_result`\u002F`not_called`. Keep the prior receipt with that packet if it is to be treated as prior provider evidence.\n\n## Interpret the evidence\n\nThe returned `calendar_context` binds calendar ID, window, observation time, recurrence and cancellation identity, all-day dates with exclusive end, transparency, self-response and busy intervals. Private event titles are removed. An inaccessible calendar, provider error, stale result or incomplete event page means unknown coverage, never a free slot. Event absence establishes nothing unless every selected calendar window is complete and fresh. An all-day event covers local dates through the day before its exclusive end; do not turn it into a guessed UTC meeting time. A cancelled recurring instance is not a live commitment.\n\nThe assistant may use complete current evidence for meeting preparation and attention timing. The `assistant-brief` method takes an exact scheduled goal occurrence, selected calendar and the calling host's actual `observed_at` instant with an explicit UTC offset, reads an upcoming bounded window, and returns the common operator work result. The window starts at the later of the occurrence due time and `observed_at`, so a wake after sleep reads the upcoming period. The host supplies this execution time; the deterministic worker never infers it from its own clock. Partial coverage holds that occurrence; it never means the calendar is free. A separate owning scheduling or conversation skill may propose times only from complete fresh coverage and private working-hour\u002Fbuffer policy. This skill neither offers slots nor sends messages. Event mutations belong to a separately governed future capability.\n\n## Recover and compose\n\nIf an event page is partial, pass its exact `next_page_token` as `page_token`, with the same calendar, time bounds and page size. Do not repeat the first page. The final resumed page has `page_complete: true` but still has partial window coverage: it does not contain earlier pages. Feed the ordered `calendar_context` values to `combine-pages` to recover whole-window coverage. That phase makes no provider call; it checks the cursor chain and window identity, deduplicates identical instances, and holds gaps, cycles or conflicting revisions. Keep the prior read receipts with these contexts. Google pagination does not provide an atomic snapshot; if instances change while paging, refresh rather than choosing a revision silently. The combined observation starts at the oldest page, so combining cannot make old evidence fresh. If a provider error or expired grant caused the gap, repair the binding and refresh the affected window. Do not add a mirrored event database, sync-token store, webhook loop or assistant-owned case for routine polling.\n\nFor example, read `primary` from `2026-10-04T00:00:00+11:00` through `2026-10-11T00:00:00+11:00`, then pass the context and receipt to the assistant. If `next_page_token` is present, continue the same query until the tail is complete, then combine the pages before concluding there are no other commitments. You may also choose separate narrower windows when that better fits the task, accounting for event overlap at their boundaries.\n\n`normalize-supplied` accepts a prior provider result and the exact requested `page_token` for that result. It reuses the evidence without calling Google, labels it `supplied_result`\u002F`not_called`, preserves every admitted event and busy interval, and validates event timing. Partial or malformed free\u002Fbusy evidence cannot establish availability. Supplied-result reuse and page combination do not independently verify the source provider; carry the original receipts when the next workflow needs that assurance.\n\nEvent reads cover overlapping events: an event must end after `time_min` and start before `time_max`. Events already underway are included. These bounds are not a filter on event start alone.\n","# Google Calendar\n\nUse this skill when a decision needs current events or busy intervals from a Google calendar the operator has explicitly selected. The default `events` method reads expanded event instances; `freebusy` reads only busy intervals. Both are read-only `google-calendar` connector operations with an exact calendar target and a positive, explicitly bounded time window. They cannot create, edit, delete, RSVP to, or invite anyone to events.\n\nThe portable skill owns Calendar evidence semantics, not credentials or connector selection. A local, self-hosted, third-party, or Runx-hosted connector is compatible when it implements the declared operations and scopes. Keep connection identifiers, credentials, tenant details and private calendar choices in the operator's binding and inputs, never in this package.\n\n## Choose a bounded read\n\nAuthorize the intended Google account for `events.read` and\u002For `freebusy.read`. The hosted Google binding requests `calendar.events.readonly` for event details and `calendar.events.freebusy` for busy-only reads; Analytics or Search Console access does not grant Calendar access. Supply the exact calendar ID plus start and end instants with explicit UTC offsets. `primary` selects the connected account's primary calendar. For multiple calendars, run the selected IDs separately and preserve each result's coverage.\n\nThe `events` method expands recurrence and reads one result page. `calendar_id` defaults to `primary`; select another exact ID when needed. Choose `page_size` for the bounded operation (100 by default, up to Google’s 2,500-event page maximum), and use its returned cursor to read any remaining events in the same window. This is a per-call work budget, not a limit on the number of events or the duration you can inspect. Use `freebusy` when only availability is relevant, so event titles are not collected. A live method returns provider readback; `normalize-supplied` only normalizes already collected bytes and says `supplied_result`\u002F`not_called`. Keep the prior receipt with that packet if it is to be treated as prior provider evidence.\n\n## Interpret the evidence\n\nThe returned `calendar_context` binds calendar ID, window, observation time, recurrence and cancellation identity, all-day dates with exclusive end, transparency, self-response and busy intervals. Private event titles are removed. An inaccessible calendar, provider error, stale result or incomplete event page means unknown coverage, never a free slot. Event absence establishes nothing unless every selected calendar window is complete and fresh. An all-day event covers local dates through the day before its exclusive end; do not turn it into a guessed UTC meeting time. A cancelled recurring instance is not a live commitment.\n\nThe assistant may use complete current evidence for meeting preparation and attention timing. The `assistant-brief` method takes an exact scheduled goal occurrence, selected calendar and the calling host's actual `observed_at` instant with an explicit UTC offset, reads an upcoming bounded window, and returns the common operator work result. The window starts at the later of the occurrence due time and `observed_at`, so a wake after sleep reads the upcoming period. The host supplies this execution time; the deterministic worker never infers it from its own clock. Partial coverage holds that occurrence; it never means the calendar is free. A separate owning scheduling or conversation skill may propose times only from complete fresh coverage and private working-hour\u002Fbuffer policy. This skill neither offers slots nor sends messages. Event mutations belong to a separately governed future capability.\n\n## Recover and compose\n\nIf an event page is partial, pass its exact `next_page_token` as `page_token`, with the same calendar, time bounds and page size. Do not repeat the first page. The final resumed page has `page_complete: true` but still has partial window coverage: it does not contain earlier pages. Feed the ordered `calendar_context` values to `combine-pages` to recover whole-window coverage. That phase makes no provider call; it checks the cursor chain and window identity, deduplicates identical instances, and holds gaps, cycles or conflicting revisions. Keep the prior read receipts with these contexts. Google pagination does not provide an atomic snapshot; if instances change while paging, refresh rather than choosing a revision silently. The combined observation starts at the oldest page, so combining cannot make old evidence fresh. If a provider error or expired grant caused the gap, repair the binding and refresh the affected window. Do not add a mirrored event database, sync-token store, webhook loop or assistant-owned case for routine polling.\n\nFor example, read `primary` from `2026-10-04T00:00:00+11:00` through `2026-10-11T00:00:00+11:00`, then pass the context and receipt to the assistant. If `next_page_token` is present, continue the same query until the tail is complete, then combine the pages before concluding there are no other commitments. You may also choose separate narrower windows when that better fits the task, accounting for event overlap at their boundaries.\n\n`normalize-supplied` accepts a prior provider result and the exact requested `page_token` for that result. It reuses the evidence without calling Google, labels it `supplied_result`\u002F`not_called`, preserves every admitted event and busy interval, and validates event timing. Partial or malformed free\u002Fbusy evidence cannot establish availability. Supplied-result reuse and page combination do not independently verify the source provider; carry the original receipts when the next workflow needs that assurance.\n\nEvent reads cover overlapping events: an event must end after `time_min` and start before `time_max`. Events already underway are included. These bounds are not a filter on event start alone.\n",{"name":5,"description":7},"main","14cf84bcc80d7abf0008335efac4d92aacfa682e","skills\u002Fgoogle-calendar",108,"https:\u002F\u002Fgithub.com\u002Frunxhq\u002Frunx","https:\u002F\u002Frunx.ai","https:\u002F\u002Fgithub.com\u002Frunxhq","the governed runtime for agent skills","2026-11-14 13:45:54",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add runxhq\u002Frunx --skill google-calendar",{"tool":52,"command":53},"bunx","bunx skills add runxhq\u002Frunx --skill google-calendar",{"tool":55,"command":56},"pnpm","pnpm dlx skills add runxhq\u002Frunx --skill google-calendar","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frunxhq\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-calendar\u002FSKILL.md",true,[60,66,70,74,78,84,88,92,96,100,104,108,112,116,120,124,128],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"eval_queries.json","REFERENCE","参考文档",2172,"https:\u002F\u002Fgithub.com\u002Frunxhq\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-calendar\u002Feval_queries.json",{"path":67,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":68,"sourceHtmlUrl":69},"evals\u002Fevals.json",1927,"https:\u002F\u002Fgithub.com\u002Frunxhq\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-calendar\u002Fevals\u002Fevals.json",{"path":71,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":72,"sourceHtmlUrl":73},"evals\u002Ffiles\u002Foctober-4-calendar-read.json",839,"https:\u002F\u002Fgithub.com\u002Frunxhq\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-calendar\u002Fevals\u002Ffiles\u002Foctober-4-calendar-read.json",{"path":75,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":76,"sourceHtmlUrl":77},"evals\u002Ffiles\u002Fquarter-calendar-pages.json",2306,"https:\u002F\u002Fgithub.com\u002Frunxhq\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-calendar\u002Fevals\u002Ffiles\u002Fquarter-calendar-pages.json",{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"google-calendar.mjs","SCRIPT","脚本",12575,"https:\u002F\u002Fgithub.com\u002Frunxhq\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-calendar\u002Fgoogle-calendar.mjs",{"path":85,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":86,"sourceHtmlUrl":87},"google-calendar.test.mjs",5630,"https:\u002F\u002Fgithub.com\u002Frunxhq\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-calendar\u002Fgoogle-calendar.test.mjs",{"path":89,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fcatalog.md",127,"https:\u002F\u002Fgithub.com\u002Frunxhq\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-calendar\u002Freferences\u002Fcatalog.md",{"path":93,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":94,"sourceHtmlUrl":95},"run.yaml",7204,"https:\u002F\u002Fgithub.com\u002Frunxhq\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-calendar\u002Frun.yaml",{"path":97,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":98,"sourceHtmlUrl":99},"tests\u002Fassistant-brief-after-sleep.yaml",1136,"https:\u002F\u002Fgithub.com\u002Frunxhq\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-calendar\u002Ftests\u002Fassistant-brief-after-sleep.yaml",{"path":101,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":102,"sourceHtmlUrl":103},"tests\u002Fassistant-brief-future-occurrence.yaml",1142,"https:\u002F\u002Fgithub.com\u002Frunxhq\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-calendar\u002Ftests\u002Fassistant-brief-future-occurrence.yaml",{"path":105,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":106,"sourceHtmlUrl":107},"tests\u002Fassistant-brief-requires-observation.yaml",330,"https:\u002F\u002Fgithub.com\u002Frunxhq\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-calendar\u002Ftests\u002Fassistant-brief-requires-observation.yaml",{"path":109,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":110,"sourceHtmlUrl":111},"tests\u002Fcomposes-in-workflow.yaml",497,"https:\u002F\u002Fgithub.com\u002Frunxhq\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-calendar\u002Ftests\u002Fcomposes-in-workflow.yaml",{"path":113,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":114,"sourceHtmlUrl":115},"tests\u002Fcontinues-exact-window.yaml",1355,"https:\u002F\u002Fgithub.com\u002Frunxhq\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-calendar\u002Ftests\u002Fcontinues-exact-window.yaml",{"path":117,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":118,"sourceHtmlUrl":119},"tests\u002Fdefault-requires-binding.yaml",180,"https:\u002F\u002Fgithub.com\u002Frunxhq\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-calendar\u002Ftests\u002Fdefault-requires-binding.yaml",{"path":121,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":122,"sourceHtmlUrl":123},"tests\u002Fdefault-runs-events.yaml",1328,"https:\u002F\u002Fgithub.com\u002Frunxhq\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-calendar\u002Ftests\u002Fdefault-runs-events.yaml",{"path":125,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":126,"sourceHtmlUrl":127},"tests\u002Fnormalizes-complete-private-and-cancelled-events.yaml",1069,"https:\u002F\u002Fgithub.com\u002Frunxhq\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-calendar\u002Ftests\u002Fnormalizes-complete-private-and-cancelled-events.yaml",{"path":129,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":130,"sourceHtmlUrl":131},"tests\u002Fpartial-freebusy-stays-unknown.yaml",653,"https:\u002F\u002Fgithub.com\u002Frunxhq\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-calendar\u002Ftests\u002Fpartial-freebusy-stays-unknown.yaml",[133,163,185,201,219,236],{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":144,"publishedAt":32},"01M6R60D2HHP5C47QZ7ZBYBHSM","webhook-handoff","Validate a runx execution context and deliver a governed payload once to an n8n Cloud workflow webhook or a Zapier Catch Hook, with exact approval and the receiver's acknowledgement receipted.","https:\u002F\u002Fgithub.com\u002Frunxhq\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fwebhook-handoff\u002FSKILL.md",[139],{"categoryNo":140,"categoryName":141,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[145,146,147,148,149,150,12,151,152,153,154,155,156,157,158,159,160,161,162],"webhook","handoff","webhook handoff","approval","zapier","context","hook","cloud","payload","n8n","validate","catch","with","workflow","execution","acknowledgement","deliver","receiver",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":32},"01M6R609BT4F4MFVK9M2YZPQTV","web-search","Discover a bounded set of fresh web source candidates from one explicit search query, preserve provider evidence and reported cost, and prepare source selection for fetching and research.","https:\u002F\u002Fgithub.com\u002Frunxhq\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fweb-search\u002FSKILL.md",[],[170,171,172,173,174,175,176,177,24,178,179,180,181,31,182,183,184],"web","search","web search","fresh","preserve","query","selection","provider","discover","evidence","SET","cost","prepare","source","research",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":191,"publishedAt":32},"01M6R5ZV4Z3FK8AHATF7AARXYD","web-fetch","Fetch and extract one public web source, optionally restrict its hosts, and return the content by digest with full provenance.","https:\u002F\u002Fgithub.com\u002Frunxhq\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fweb-fetch\u002FSKILL.md",[],[192,193,170,194,195,196,197,198,199,157,200,183],"fetch","web fetch","full","content","extract","public","digest","hosts","provenance",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":208,"publishedAt":32},"01M6R5ZPRJQZ1Y8CBPT3WHSWCB","vuln-triage","Prioritize actual exact-coordinate vulnerability findings, preserve unknown exposure and partial coverage, and return practical remediation or an unsent advisory draft.","https:\u002F\u002Fgithub.com\u002Frunxhq\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fvuln-triage\u002FSKILL.md",[207],{"categoryNo":140,"categoryName":141,"taxonomyType":142,"taxonomyTypeDesc":143},[209,210,174,211,212,213,214,215,216,217,218,22],"triage","vuln triage","prioritize","remediation","draft","advisory","vulnerability","unknown","coordinate","practical",{"skillNo":220,"name":221,"nameZh":6,"description":222,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":223,"categories":224,"keywords":226,"publishedAt":32},"01M6R5Z9RR7V456TAW4J5AJG0R","twitter","Govern X (Twitter) account work through three lanes: evidence reads, typed act plans for posting and account hygiene, and gated execution with per-act provider evidence. Nothing reaches a live timeline or mutates an account without an explicit approval recorded in the receipt.","https:\u002F\u002Fgithub.com\u002Frunxhq\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Ftwitter\u002FSKILL.md",[225],{"categoryNo":140,"categoryName":141,"taxonomyType":142,"taxonomyTypeDesc":143},[221,179,227,228,157,229,159,177,24,230,231,232,148,233,234,235],"gated","work","plans","three","posting","hygiene","timeline","live","act",{"skillNo":237,"name":238,"nameZh":6,"description":239,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":240,"categories":241,"keywords":243,"publishedAt":32},"01M6R5Z3XRVR0V5XTES05XJRV8","team-delegate","Divide bounded work across an operator-selected team and return exact member assignments with source context, scope ceilings and acceptance checks.","https:\u002F\u002Fgithub.com\u002Frunxhq\u002Frunx\u002Fblob\u002Fmain\u002Fskills\u002Fteam-delegate\u002FSKILL.md",[242],{"categoryNo":140,"categoryName":141,"taxonomyType":142,"taxonomyTypeDesc":143},[244,245,246,31,150,183,247,228,157,248,249,250],"team","team delegate","delegate","operator","across","acceptance","scope"]