[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75TTHW71NXKXW144682SPF1":3,"skill-same:01M75TTHW71NXKXW144682SPF1":156},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":20,"frontMatter":21,"refName":22,"commitSha":23,"skillDirectory":24,"forksCount":13,"repositoryHtmlUrl":25,"repositoryHomepageUrl":6,"ownerHtmlUrl":26,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":27,"install":28,"resources":41},"01M75TTHW71NXKXW144682SPF1","subsessions",null,"damien-robotsix\u002Frobotsix-chat","damien-robotsix","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F130368771?v=4","01M75TS5N09AA5MQAS3V6TPNM5","Damien SIX","01M75TS5NMBPJ3RRHERKBVA7DY",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Fskill.md",[],[],"2026-11-12 13:55:43",false,"# Subsessions — Background Agents\n\nThe subsession system runs background agents spawned from chat sessions. Every subsession is an\nindependent agent with its own model, instructions, and lifecycle — it runs concurrently while the\nparent conversation continues.\n\n## Subsession kinds\n\n| Kind             | Behaviour                                                                                            |\n| ---------------- | ---------------------------------------------------------------------------------------------------- |\n| `task`           | One-shot background job — runs to completion and reports a summary back.                             |\n| `periodic`       | Re-runs its instructions on a fixed interval until closed — for monitoring, polling, and CI-watch.   |\n| `wait_for_event` | Event-driven ticket monitor — wakes on mill push events (ticket state changes) instead of polling.   |\n| `user_chat`      | Side-chat with the operator — for discussions or decisions without blocking the parent conversation. |\n| `on_close`       | One-shot task that fires when the parent session is **closed** — for post-conversation work.         |\n\n## Agent tools — spawn and control from any session\n\nThese tools are available to the main chat agent (depth 0) and to any subsession agent whose\nchildren would still be within the configured `max_depth`.\n\n### `spawn_subsession`\n\nStart a background subsession and return its id immediately. Required: `kind`, `title`,\n`instructions`. Optional: `model_level`, `interval_seconds`, `anchor_time`, `max_runs`,\n`auto_stop_no_change_runs`, `include_previous_result`, `inherit_context`, `dedup_key`,\n`run_timeout_seconds`.\n\n- `model_level` picks capability 1 (cheap\u002Ffrequent) to 3 (frontier); 1 covers monitors and routine\n  checks, 2 is the workhorse for general work, 3 is frontier-only. Which provider serves a level is\n  automatic (flat-rate default with paid failover). For `periodic` and `wait_for_event` monitors,\n  levels above the server's `monitor_max_model_level` (default 1) are silently clamped down — use\n  level 1 for all routine monitoring. Hard tasks should use `kind=\"task\"` (uncapped) instead.\n- `interval_seconds` (minimum enforced), `max_runs`, and `auto_stop_no_change_runs` are for\n  `periodic` only.\n- `anchor_time` (`periodic` only, optional) pins recurrences to an absolute wall-clock time instead\n  of \"spawn time + interval\". Accepts `\"HH:MM\"` or `\"HH:MM:SS\"`, optionally followed by an IANA\n  timezone — e.g. `\"09:00\"`, `\"09:00:00 UTC\"`, or `\"09:00 Europe\u002FParis\"` (default timezone UTC).\n  With `interval_seconds=86400` and `anchor_time=\"09:00\"` the monitor fires every day at 09:00 UTC;\n  each next fire is the next occurrence of that time-of-day phase-aligned to `interval_seconds`, so\n  the schedule does not drift. The first run still fires at spawn; the anchor governs every\n  subsequent run. Omit it for the legacy relative-interval behaviour. DST: for whole-day intervals\n  the local time-of-day is held constant across daylight-saving transitions.\n- `auto_stop_no_change_runs` (must be an integer ≥ 1) overrides the global auto-stop threshold for\n  this monitor only. For a long-lived ticket monitor that progresses over days (waiting on human\n  review or CI), pass a higher value (e.g. 50) so it is not auto-stopped after the default 3\n  consecutive `NO_CHANGE` runs.\n- `dedup_key` prevents duplicate `user_chat`, `periodic`, and `wait_for_event` subsessions — use the\n  ticket id as the dedup key for monitors. Always check `list_subsessions` first.\n- `run_timeout_seconds` (seconds, optional) overrides the global per-run timeout (default 600 s) for\n  this subsession — declare a longer budget (e.g. 1800 for a 20-minute batch) for long search \u002F\n  tournament \u002F batch work. Bounded by `subsessions.max_run_timeout_seconds` (default 3600 s);\n  requests above the cap are clamped to it. A turn that exceeds its budget is failed fast and NOT\n  retried, so size it to the longest single step of the job.\n\n### `message_subsession`\n\nSend a steering message to a running subsession — it sees the message at its next turn boundary.\n\n### `close_subsession`\n\nClose a subsession from the outside. Prefer letting subsessions finish on their own.\n\n### `list_subsessions`\n\nList this conversation's subsessions: id, kind, status, model level, title, and scheduling info.\n\n### `check_monitor`\n\nCheck whether an active monitor (periodic or wait_for_event subsession) exists for a given ticket.\nReturns a JSON object with `active` (bool) and, when a monitor is found, its `subsession_id`,\n`kind`, `status`, and `title`. **Always call this tool before claiming a tracker is running** — do\nNOT assert \"tracking is active\" without verifying via `check_monitor`. Searches both\ncheckpoint-based matches and dedup-key matches.\n\n### Surface stop-and-escalate conditions in the user-facing summary\n\nWhen you spawn or arm a monitor that carries a **stop-and-escalate condition** — a rule that will\nhalt the monitor and alert the operator rather than keep looping (e.g. \"if the build fails again on\nthe same model-config error, stop and escalate as an infrastructure blocker\") — you MUST make that\ncondition visible in the user-facing summary. State plainly what triggers the stop and that the\nmonitor will alert the user, for example: \"If the build fails again, the monitor will stop and alert\nyou as an infrastructure blocker.\" Do not leave the stop rule implicit in the monitor's\ninstructions: the operator otherwise assumes the monitor will loop indefinitely, and is caught off\nguard when it halts and escalates. Surfacing the condition aligns the operator's expectations with\nthe monitor's actual escalation behaviour.\n\n## Tools available only inside a subsession\n\n### `complete_subsession`\n\nClose **this** subsession and report a summary to the parent. Call when work is finished, discussion\nconcluded, or the monitored condition has reached a terminal state. The summary is the only thing\nthe parent conversation is guaranteed to see — make it concise, self-contained, and user-facing\n(omit internal technical details: block IDs, event numbers, stack traces, raw API fragments).\n\n**Guard: periodic ticket monitors must observe at least one full tick before self-closing** — a\n`complete_subsession` call before the first run completes is rejected.\n\n**Guard: periodic ticket monitors must verify the most recent CI workflow run** before calling\n`complete_subsession`. Use `check_workflow_run` (or the GitHub Actions API) to fetch the latest run\nstatus, and include the verification result in the summary. A summary without CI evidence is\nrejected.\n\nWhen the verified run is a `startup_failure` (zero jobs, no logs), report the tool's deterministic\nclassification verbatim: a sibling workflow on the **same commit** that reached job execution means\n**per-workflow config issue** (not an account-level problem); zero siblings reaching job execution\nmeans **account\u002Frunner issue** (operator action, not a workflow-file edit). Never speculate a\nbilling diagnosis that contradicts the tool's classification — two monitors watching the same run\nmust reach the same conclusion.\n\n### `set_checkpoint`\n\nPersist arbitrary key\u002Fvalue data across restarts. Each call **replaces** the entire checkpoint, so\ninclude all fields you want to keep. Use it for: monitored ticket id, last-known ticket state,\ncompletion criteria, consecutive-failure counters. Two keys are system-owned and preserved\nautomatically even if omitted: `ticket_id` for `wait_for_event` monitors (so the monitor keeps its\ntarget ticket across restarts), and `auto_stop_no_change_runs` for `periodic` monitors (so a\nper-spawn no-change threshold override is not lost).\n\n### `self_update_subsession`\n\nUpdate THIS periodic subsession's own run configuration — the natural alternative to spawning a new\nperiodic child (which is not allowed from within a periodic context). Changes take effect on the\nnext scheduled tick.\n\nParameters (at least one required):\n\n- `instructions` (string, ≤ 8000 chars) — rewrite or extend the instruction text this subsession\n  executes each tick.\n- `interval_seconds` (number, ≥ configured minimum) — change the polling interval.\n- `max_runs` (integer, ≥ 0) — adjust the remaining max-run cap. Pass `null`\u002F`None` to remove the cap\n  entirely. The run counter is **never** reset — self-update cannot bypass max-run limits.\n\nOnly works from within a periodic subsession. Returns a confirmation string listing which fields\nwere changed.\n\n## Lifecycle\n\n| Status        | Meaning                                                    |\n| ------------- | ---------------------------------------------------------- |\n| `running`     | An agent turn is in flight.                                |\n| `waiting`     | Idle, waiting for an inbox message (user_chat).            |\n| `sleeping`    | Periodic, waiting for the next scheduled run.              |\n| `paused`      | Periodic, auto-paused by the idle-guard — retains worker.  |\n| `closed`      | Finished normally, summary delivered.                      |\n| `failed`      | Terminated with an error.                                  |\n| `interrupted` | Server restarted while work was live — resumes on restart. |\n\n## Operating rules (moved from the system prompt, 2026-09-08)\n\nThese rules complement the tool reference above. The spawning conversation keeps the short version\n(one subsession per subject, self-contained instructions, reporting contract, pre-spawn guard);\neverything about running INSIDE a subsession, monitor hygiene and user_chat decision etiquette is\nhere.\n\n### Monitors and periodic subsessions\n\n– Monitor existence check: NEVER claim a monitor is active, or that no monitor is needed because the\nwork already finished, without first checking live state. Before making any claim about a monitor's\nexistence or status, call check_monitor and list_subsessions (and, when a specific ticket is named,\ncomponent_request GET \u002Ftickets\u002F{id}) to verify what is actually spawned and what state it is in. If\ncheck_monitor returns terminal_report=true, a previous monitor already tracked the ticket to an end\nstate — spawn a new monitor only if GET \u002Ftickets\u002F{id} shows it active again (not DONE\u002FCLOSED), and\ndo NOT claim the work is unfinished. If no monitor was spawned and no terminal report exists, say so\ndirectly and offer to start one — do NOT invent a reason for why no monitor exists. Treat the work\nas unfinished (and the monitor as still needed) until the ticket is merged AND its endpoints are\nconfirmed live. – Inside a subsession, call complete_subsession(summary) as soon as your goal is\nreached — for periodic work, that means as soon as the monitored condition reaches a verified\nterminal state. Also call complete_subsession when user intervention is required (ticket blocked on\na decision, escalation needed). Do NOT call complete_subsession for intermediate progress — only the\nfinal summary reaches the parent. Reply exactly NO_CHANGE on a periodic run where nothing changed. –\nPeriodic subsessions poll directly on every cycle and cannot spawn child subsessions — they perform\nall monitoring, polling, and checking inline in their own replies. Being spawned as a periodic\nmonitor directly from a conversation (without going through a task subsession) is fully supported —\nit is the preferred way to launch a ticket monitor. – When monitoring a ticket that involves a code\nchange deployed to a component, periodic subsessions must track deploy status alongside board\nstatus. After the PR merges, the fix is not yet live — the monitor must verify the component is\nrunning the new image. Use get_lifecycle_service_status to confirm rollout completed, and\ncomponent_request GET \u002Fhealth to verify the component is healthy. A merged PR whose image is not yet\ndeployed is not a terminal state — keep the monitor open until deploy is confirmed. This prevents\nredundant fix proposals for issues already resolved in the running image. – If a periodic subsession\nattempts spawn_subsession and receives a 'periodic subsessions cannot spawn' error, do NOT present\noptions to the user or ask how to proceed. This is a hard code-level restriction, not a transient\nfailure — retry will hit the same gate. Fall back immediately: perform the monitoring, polling, or\nchecking inline in the current reply. If the work is too large for one cycle, spread it across\nmultiple cycles using NO_CHANGE replies to hold intermediate state — the periodic monitor's own\nreply loop is the correct vehicle for ongoing inline work. The user should never see the error or be\nasked to choose a recovery path. – Subsessions can spawn their own subsessions (nesting is\ndepth-limited) — split genuinely independent subtasks, do not chain for its own sake. – Spawn\nperiodic monitors directly — do NOT create a child task subsession whose only job is to call\nspawn_subsession(kind='periodic', ...). A task that exists solely to launch a monitor wastes a model\nround-trip and duplicates the spawning logic you already own. If you need a periodic monitor, spawn\nit from your own context. – When spawning a subsession to report a known global process error (e.g.\n'asyncio.run() cannot be called from a running event loop', or any error that affects multiple\ntickets\u002Fsubsessions at once), set dedup_key to the exact error message prefix (first 80 chars). When\nspawning a periodic monitor for a ticket, set dedup_key to the ticket id (e.g. '5f1c') — this\nprevents duplicate monitors for the same ticket. The system will suppress duplicate spawns for the\nsame key — only the first spawn creates a new subsession; subsequent spawns return the existing id.\nAlways pair this with list_subsessions to check what is already running.\n\n### Subsession pool budget\n\n– Subsession pool budget (check before spawning any monitor): the global subsession pool is finite —\nall active subsessions (monitors, tasks, side-chats) share one process-wide capacity cap\n(`subsessions.max_concurrent` in the server config). Spawning past the cap forces eviction of an\nexisting paused subsession, so an unplanned spawn can silently kill a monitor you still need. Treat\nevery spawn as consuming a scarce slot, and plan monitor count against the cap: • Count before\nspawning: call list_subsessions and count current active AND paused subsessions, then check headroom\nagainst the cap. If the pool is full, do not spawn — reuse an existing monitor (see below) or ask\nthe operator which monitor to pause. • Reuse slots: if an existing monitor already covers the same\nor a related ticket, resume or reuse it instead of spawning a duplicate. One monitor can watch a\nrelated set of tickets; duplicates waste a slot. • Skip draft tickets: do not spawn monitors for\ntickets still in `draft` status — they are unlikely to change state and the board-drain periodic\npicks those up instead. Monitor only tickets that have entered the active pipeline. • No\nevict-and-respawn thrash: do not pause\u002Fevict a low-priority monitor to free a slot and then forget\nto respawn it. If you must evict to make room, note the evicted monitor's ticket id and respawn it\nexplicitly once a slot frees — never leave it evicted silently.\n\n### user_chat decision subsessions\n\n– In a user_chat subsession, ask a pending question ONCE and wait for the user's reply; close with a\nsummary once the discussion reaches a conclusion. The user can also close it at any time. – CRITICAL\nfor user_chat decision subsessions: the operator sees ONLY the messages you write in the panel —\nthey do NOT see your instructions. Every time you reference an option label (Option A, Option B, …)\nyou MUST restate its full definition inline. For example, write \"Option B (phased: cleanup now,\nwarning-first gate, fail-closed only after auto-mail migrates)\" — never just \"Option B.\" This\napplies to every turn: the initial recommendation and any follow-up confirmation. When presenting a\ndecision, show ALL options with definitions so the operator can compare. – CRITICAL for user_chat\ndecision subsessions: present at most ONE decision per message. When multiple independent decisions\nare pending, present them SEQUENTIALLY — state the first decision with its options, wait for the\noperator's answer, confirm the choice (echo the selected option back and ask for explicit\nacknowledgement), then and only then present the next decision. Never batch multiple unrelated\ndecisions into a single message; a human operator cannot process a list of choices reliably and will\nmiss or misread options. If the operator raises a new question mid-sequence, answer it but return to\nthe pending decision queue afterward.\n",{},"main","c1d7c05ced8b81c2750ddc6e5e49a7803fc90940","src\u002Frobotsix_chat\u002Fsubsessions","https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat","https:\u002F\u002Fgithub.com\u002Fdamien-robotsix","2026-11-14 18:49:02",{"source":7,"skillName":5,"commands":29,"prompt":39,"zipAvailable":40},[30,33,36],{"tool":31,"command":32},"npx","npx skills add damien-robotsix\u002Frobotsix-chat --skill subsessions",{"tool":34,"command":35},"bunx","bunx skills add damien-robotsix\u002Frobotsix-chat --skill subsessions",{"tool":37,"command":38},"pnpm","pnpm dlx skills add damien-robotsix\u002Frobotsix-chat --skill subsessions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Fskill.md",true,[42,48,52,56,60,64,68,72,76,80,84,88,92,96,100,104,108,112,116,120,124,128,132,136,140,144,148,152],{"path":43,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":46,"sourceHtmlUrl":47},"__init__.py","SCRIPT","脚本",2597,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002F__init__.py",{"path":49,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":50,"sourceHtmlUrl":51},"continuation.py",2275,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Fcontinuation.py",{"path":53,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":54,"sourceHtmlUrl":55},"delivery.py",55497,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Fdelivery.py",{"path":57,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":58,"sourceHtmlUrl":59},"models.py",13392,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Fmodels.py",{"path":61,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":62,"sourceHtmlUrl":63},"prompt_context.py",3644,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Fprompt_context.py",{"path":65,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":66,"sourceHtmlUrl":67},"prompts.py",3070,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Fprompts.py",{"path":69,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":70,"sourceHtmlUrl":71},"registry_checkpoint.py",6922,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Fregistry_checkpoint.py",{"path":73,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":74,"sourceHtmlUrl":75},"registry_constants.py",2549,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Fregistry_constants.py",{"path":77,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":78,"sourceHtmlUrl":79},"registry_index.py",14523,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Fregistry_index.py",{"path":81,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":82,"sourceHtmlUrl":83},"registry_lifecycle.py",19445,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Fregistry_lifecycle.py",{"path":85,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":86,"sourceHtmlUrl":87},"registry_store.py",4419,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Fregistry_store.py",{"path":89,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":90,"sourceHtmlUrl":91},"registry_tickets.py",15014,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Fregistry_tickets.py",{"path":93,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":94,"sourceHtmlUrl":95},"registry.py",32882,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Fregistry.py",{"path":97,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":98,"sourceHtmlUrl":99},"resume.py",33206,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Fresume.py",{"path":101,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":102,"sourceHtmlUrl":103},"schedule.py",6645,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Fschedule.py",{"path":105,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":106,"sourceHtmlUrl":107},"slot_budget_wiring.py",3753,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Fslot_budget_wiring.py",{"path":109,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":110,"sourceHtmlUrl":111},"slot_budget.py",5068,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Fslot_budget.py",{"path":113,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":114,"sourceHtmlUrl":115},"subsession_types.py",2840,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Fsubsession_types.py",{"path":117,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":118,"sourceHtmlUrl":119},"subsession_waits.py",44540,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Fsubsession_waits.py",{"path":121,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":122,"sourceHtmlUrl":123},"tools.py",53351,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Ftools.py",{"path":125,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":126,"sourceHtmlUrl":127},"turn_errors.py",2374,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Fturn_errors.py",{"path":129,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":130,"sourceHtmlUrl":131},"turn_runner.py",12107,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Fturn_runner.py",{"path":133,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":134,"sourceHtmlUrl":135},"watcher.py",77370,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Fwatcher.py",{"path":137,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":138,"sourceHtmlUrl":139},"worker_errors.py",9128,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Fworker_errors.py",{"path":141,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":142,"sourceHtmlUrl":143},"worker_mill.py",30475,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Fworker_mill.py",{"path":145,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":146,"sourceHtmlUrl":147},"worker_periodic.py",50908,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Fworker_periodic.py",{"path":149,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":150,"sourceHtmlUrl":151},"worker_validation.py",2010,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Fworker_validation.py",{"path":153,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":154,"sourceHtmlUrl":155},"worker.py",55653,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Fworker.py",[157,163,169,175,181,187],{"skillNo":158,"name":159,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":18},"01M75TTQ70FE02S8DNAB423T5H","volume_tools","https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fvolume_tools\u002Fskill.md",[],[],{"skillNo":164,"name":165,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":18},"01M75TTNCPAPZBKHJTM4WFVAP1","ticket_poll","https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fticket_poll\u002Fskill.md",[],[],{"skillNo":170,"name":171,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":174,"publishedAt":18},"01M75TTGBAFPVH6759BNB3G3NR","security","https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Frepo\u002Fsecurity\u002Fskill.md",[],[],{"skillNo":176,"name":177,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":180,"publishedAt":18},"01M75TTCZN8GTQQ92GR7Z6E7Y2","direct","https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Frepo\u002Fdirect\u002Fskill.md",[],[],{"skillNo":182,"name":183,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":186,"publishedAt":18},"01M75TT98KF65BJQNPQ61GQFKV","actions","https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Frepo\u002Factions\u002Fskill.md",[],[],{"skillNo":188,"name":189,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":192,"publishedAt":18},"01M75TT6G40RCR0E5P4KFP7ZEN","render_url","https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Frender_url\u002Fskill.md",[],[]]