[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75TTNCPAPZBKHJTM4WFVAP1":3,"skill-same:01M75TTNCPAPZBKHJTM4WFVAP1":76},{"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},"01M75TTNCPAPZBKHJTM4WFVAP1","ticket_poll",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\u002Fticket_poll\u002Fskill.md",[],[],"2026-11-12 13:55:43",false,"# Ticket Poll — ticket-state lookup, PR merging, and ticket filing via the component roster\n\nYou have `ticket_poll`, `ticket_poll_batch`, `merge_pull_request`, `mark_ticket_done`,\n`file_ticket`, `find_ticket_by_pr`, `prioritize_all_open_tickets`, and `list_stale_ready_tickets`\ntools that interact with the mill board API. These tools route through `component_request`\n(roster-based connectivity) when available, falling back to the direct board API when the roster is\nunavailable — they are reliable as the primary path for checking ticket state, merging approved PRs,\nand filing new tickets.\n\n## When to use it\n\n- **Primary ticket-state check** — `ticket_poll` is your go-to tool for checking a ticket's current\n  state. It uses the same roster-based connectivity as `component_request` and is always preferred\n  for single-ticket lookups.\n\n- **Independent verification** — use `ticket_poll` as a second source (alongside\n  `component_request`) to satisfy the terminal-state double-check requirement.\n\n- **Periodic monitoring** — every monitor tick, call `ticket_poll` (or `component_request`) to\n  live-GET the ticket state before reporting any change.\n\n- **Bulk triage** — use `ticket_poll_batch` to fetch full details (state, history, events, comments)\n  for many tickets in one call, then classify them by failure signature.\n\n- **Merge approved PRs** — use `merge_pull_request` when a ticket is in `waiting_auto_merge` or\n  `human_mr_approval` state and its associated PR has been approved. This directly calls the mill\n  board's merge-now endpoint, bypassing the need for auto-merge to be enabled on the target\n  repository.\n\n- **Find ticket by PR** — use `find_ticket_by_pr` when you know a PR URL (e.g.\n  `https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo\u002Fpull\u002F656`) but not the associated ticket ID. This is a direct\n  lookup — one API round-trip instead of enumerating all tickets and filtering client-side.\n\n- **File a new ticket** — use `file_ticket` to create a new ticket on the mill board. Use this when\n  you identify a deferred improvement, follow-up task, or actionable item during a session —\n  especially when the user has granted autonomy and the improvement would prevent recurring manual\n  decisions. Always mention the filed ticket in your final summary so the user is aware.\n\n- **Route to an external repo** — when a user request belongs in a different repository (e.g. a\n  model-routing or provider change belongs in `robotsix-llmio`, not `robotsix-chat`), use\n  `file_ticket` with the appropriate `repo_id` to dispatch the ticket to that repo's board. This is\n  the primary mechanism for routing out-of-scope requests to the correct team — do not tell the user\n  \"I can't do that because it's in a different repo\" when you can file the ticket for them. Known\n  external repo ids include `robotsix-llmio`, `robotsix-mill`, `robotsix-standards`, and\n  `robotsix-central-deploy`.\n\n- **Resolve a repo id to GitHub** — use `resolve_repo(repo_id)` before calling any GitHub tool\n  (`list_open_prs`, `fetch_repo_for_study`, PR inspection) with a repository you only know by its\n  mill `repo_id` (e.g. `robotsix-central-deploy`). It reads the mill registry (`GET \u002Frepos`) and\n  parses `owner\u002Frepo` from the remote URL. The GitHub account is a personal account, not an\n  organisation named after the fleet — never guess `\u003Cfleet>\u002F\u003Crepo>`.\n\n- **Queue health monitoring** — use `list_stale_ready_tickets` to detect tickets that have been\n  sitting in the `ready` state without being picked up by a worker. This surfaces queue stalls so\n  the agent can escalate or notify the operator rather than silently waiting.\n\n- **Close a superseded or duplicate ticket** — use `mark_ticket_done` to transition a ticket to the\n  terminal `done` state. Use this when a ticket is superseded by another ticket that is already\n  `DONE` or `CLOSED`, or when work is confirmed complete. Do NOT ask the operator to close tickets\n  manually on the UI when this tool is available.\n\n## Allowed operations\n\n| Tool                          | Description                                                                   |\n| ----------------------------- | ----------------------------------------------------------------------------- |\n| `ticket_poll`                 | HTTP GET to the board API; returns the ticket's current state.                |\n| `resolve_repo`                | Map a mill `repo_id` to its GitHub `owner\u002Frepo` via `GET \u002Frepos`.             |\n| `ticket_poll_batch`           | Concurrent HTTP GETs for multiple tickets; returns full details for triage.   |\n| `merge_pull_request`          | HTTP POST to merge the approved PR associated with a ticket.                  |\n| `mark_ticket_ready`           | HTTP POST to force a stalled draft\u002Fhuman_issue_approval ticket to `ready`.    |\n| `mark_ticket_done`            | HTTP POST to close a ticket by transitioning it to the terminal `done` state. |\n| `find_ticket_by_pr`           | HTTP GET to find the ticket linked to a given PR URL.                         |\n| `prioritize_all_open_tickets` | Lists all open, unflagged tickets and sets priority on every one in a batch.  |\n| `list_stale_ready_tickets`    | Lists tickets stuck in `ready` beyond the staleness threshold.                |\n| `file_ticket`                 | HTTP POST to \u002Ftickets\u002Fingest to file a new ticket on the board.               |\n\nThe tool signatures are:\n\n```python\nticket_poll(ticket_id: str) -> str\nticket_poll_batch(ticket_ids: list[str]) -> str\nmerge_pull_request(ticket_id: str) -> str\nmark_ticket_ready(ticket_id: str, justification: str = \"\") -> str\nmark_ticket_done(ticket_id: str, justification: str = \"\") -> str\nfind_ticket_by_pr(pr_url: str) -> str\nprioritize_all_open_tickets() -> str\nlist_stale_ready_tickets() -> str\nfile_ticket(title: str, description: str = \"\", kind: str = \"task\", repo_id: str = \"\") -> str\n```\n\n## Lifecycle and priority mutation endpoints (via `component_request`)\n\nWhen you need to change a ticket's state or priority, use `component_request` with the correct HTTP\nmethod and path below. **Never guess or fabricate paths** — every mutating operation on a ticket has\na documented endpoint. Guessing a wrong method (e.g. `PATCH`) or a wrong path (e.g. `\u002Fprioritize`)\ncauses 4xx errors and wastes turns.\n\n| Operation         | Method | Path                           | Notes                                                                                                                                                                                              |\n| ----------------- | ------ | ------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| Toggle priority   | POST   | `\u002Ftickets\u002F{id}\u002Fpriority`       | Set or clear a ticket's priority flag.                                                                                                                                                             |\n| Resume blocked    | POST   | `\u002Ftickets\u002F{id}\u002Fresume-blocked` | Body: `{\"justification\": \"why this ticket can safely resume now\"}`.                                                                                                                                |\n| Force to ready    | POST   | `\u002Ftickets\u002F{id}\u002Fmark-ready`     | Transition a stalled `draft` \u002F `human_issue_approval` ticket to `ready`. Body (optional): `{\"justification\": \"why this ticket can move to ready\"}`. Prefer the dedicated `mark_ticket_ready` tool. |\n| Mark done         | POST   | `\u002Ftickets\u002F{id}\u002Fmark-done`      | Transition a ticket to the terminal `done` state. Prefer the dedicated `mark_ticket_done` tool.                                                                                                    |\n| Merge PR          | POST   | `\u002Ftickets\u002F{id}\u002Fmerge-now`      | Prefer the dedicated `merge_pull_request` tool.                                                                                                                                                    |\n| File a new ticket | POST   | `\u002Ftickets\u002Fingest`              | Submit a ticket spec for ingestion into the board. Prefer the dedicated `file_ticket` tool.                                                                                                        |\n| Read ticket state | GET    | `\u002Ftickets\u002F{id}`                | Prefer the dedicated `ticket_poll` \u002F `ticket_poll_batch` tools.                                                                                                                                    |\n| List tickets      | GET    | `\u002Ftickets`                     | Query parameters: `state`, `limit`, etc.                                                                                                                                                           |\n\nAll mutation endpoints require authorization — the `component_request` tool applies the correct auth\nheaders from the roster automatically. However, **mutations must still be authorized by the\noperator** before you call them (see the main prompt's MUTATION AUTHORIZATION section).\n\n**Anti-patterns — do NOT do these:**\n\n- `PATCH \u002Ftickets\u002F{id}` — there is no PATCH endpoint for tickets; use POST with the specific path.\n- `POST \u002Fprioritize` or `POST \u002Ftickets\u002Fprioritize` — the correct path is `\u002Ftickets\u002F{id}\u002Fpriority`.\n- Guessing a path from an operation name — always consult this table first.\n\n## Return values\n\n### `ticket_poll`\n\nA JSON string with these fields:\n\n- `ticket_id` — the ticket identifier you supplied\n- `state` — the ticket's current state string, one of the real mill states: `draft`,\n  `human_issue_approval`, `ready`, `code_review`, `documenting`, `deliverable`,\n  `implement_complete`, `human_mr_approval`, `waiting_auto_merge`, `rebasing`, `fixing_ci`,\n  `addressing_review`, `done`, `closed`, `blocked`, `errored`, `awaiting_user_reply`, `epic_open`,\n  `epic_closed` (there is NO `in_progress`, `approved` or `review` state); `null` when the state\n  could not be determined\n- `error` — empty string on success, or a diagnostic message on failure\n- `pr_url` — the ticket's pull-request URL, or `null`\n- `delivered` — `true` when a `done` \u002F `closed` ticket has a `pr_url` or passed through a merge\n  state (`implement_complete`, `human_mr_approval`, `waiting_auto_merge`, `done`). **A `closed`\n  ticket with a PR is delivered, not dropped** — `closed` follows `done` when the retrospect\n  finishes.\n- `delivery_note` — e.g. `\"closed after delivery (retrospect): PR \u003Curl>\"`, or `null`\n- `unexpected_terminal` — a human-readable diagnostic string ONLY when the ticket reached `closed` \u002F\n  `done` with no PR and without ever entering an active-work or merge state (the `draft → closed` \u002F\n  `ready → closed` shape); `null` otherwise. Before telling the operator that work was dropped,\n  quote `state`, `pr_url` and `delivered` from this tool — never infer \"dropped\" from `closed`\n  alone.\n- `cache_caveat` — *(present only when the board API was unreachable and the response was served\n  from the ticket-state cache)* a human-readable staleness note, e.g.\n  `[last-known state — board API unreachable; showing cached state from 120s ago]`. Entries older\n  than 1 hour are flagged as `stale`.\n\n### `resolve_repo`\n\nA JSON string:\n`{\"repo_id\", \"full_name\": \"owner\u002Frepo\", \"owner\", \"repo\", \"forge_remote_url\", \"error\": \"\"}`. When the\nid is unknown: `full_name: null`, an `error`, and `known_repo_ids` listing the registered ids — pick\none of those or pass an explicit `owner\u002Frepo`.\n\n### `ticket_poll_batch`\n\nA JSON string with a `tickets` array. Each element has:\n\n- `ticket_id` — the ticket identifier\n- `state` — the ticket's current state string (or `null`)\n- `data` — the full JSON response from `GET \u002Ftickets\u002F{id}` (includes events, history, comments,\n  cycle metadata)\n- `error` — empty string on success, or a diagnostic message on failure\n- `unexpected_terminal` — same semantics as in `ticket_poll` above\n\n### `merge_pull_request`\n\nA status message string from the mill API — either a success confirmation or an error describing why\nthe merge failed (e.g. the PR is not approved, conflicts exist, or required status checks have not\npassed). The tool routes through the component roster when available, falling back to the direct\nboard API on any failure.\n\n### `find_ticket_by_pr`\n\nA JSON string with these fields:\n\n- `ticket_id` — the full ticket ID of the matching ticket, or `null` when no match was found\n- `state` — the ticket's current state string, or `null`\n- `pr_url` — the PR URL that was looked up (echoed back)\n- `error` — empty string on success, or a diagnostic message when no matching ticket was found or\n  the board API was unreachable\n\n### `list_stale_ready_tickets`\n\nA JSON string with these fields:\n\n- `stale_ready_count` — number of tickets in `ready` state whose last-update timestamp exceeds the\n  staleness threshold\n- `total_ready` — total number of tickets currently in `ready` state (for context)\n- `threshold_minutes` — the configured staleness threshold (from\n  `autonomous.ready_staleness_minutes`)\n- `stale_tickets` — an array of stale ticket objects, each with:\n  - `ticket_id` — the ticket's full identifier\n  - `title` — the ticket's title\n  - `state` — always `\"READY\"` (only ready-state tickets are returned)\n  - `staleness` — human-readable duration since the ticket's last update (e.g. `\"15m\"`, `\"2.1h\"`)\n  - `staleness_seconds` — the staleness duration as a float (seconds), or `null` when the ticket has\n    no timestamp\n  - `updated_at` — the ticket's `updated_at` timestamp (raw, as returned by the API)\n  - `created_at` — the ticket's `created_at` timestamp (raw, as returned by the API)\n- `error` — *(present only on a listing failure)* a diagnostic message when the board ticket list\n  could not be fetched\n\nTickets are sorted by staleness descending (most stale first). Tickets with no timestamp are\nincluded at the top with `staleness: \"unknown (no timestamp)\"` so they are not silently ignored.\n\nUse this tool to detect queue stalls — tickets sitting in `ready` without being picked up by a\nworker — and to decide whether the queue needs operator attention.\n\n### `prioritize_all_open_tickets`\n\nA JSON string with these fields:\n\n- `prioritized` — number of tickets whose priority was successfully set\n- `skipped` — number of tickets already prioritized (no action taken)\n- `errors` — number of tickets where the priority toggle failed\n- `total_open` — total number of open tickets considered (prioritized + skipped)\n- `results` — an array of per-ticket outcome objects, each with `ticket_id`, `state`, `ok`\n  (boolean), and `error` (empty on success)\n- `note` — *(present when there were no tickets to prioritize)* a human-readable message (e.g. \"No\n  open, unflagged tickets to prioritize.\")\n- `error` — *(present only on a listing failure)* a diagnostic message when the board ticket list\n  could not be fetched\n\nThis tool replaces the manual sequence of listing tickets, identifying unflagged ones, and toggling\npriority on each individually. Call it when the user asks to \"prioritize tickets\" or \"prioritize all\nopen tickets.\"\n\n### `file_ticket`\n\nA JSON string with these fields:\n\n- `ticket_id` — the created ticket's ID on success (e.g. `\"20260816T161602Z-my-ticket-a3f2\"`)\n- `error` — empty on success, or a diagnostic message on failure\n\n**`repo_id` pre-validation.** When a `repo_id` is provided, the tool validates it against the\nboard's registered repo list *before* calling the ingest API. If the `repo_id` is not in the list,\nthe tool returns early with an empty `ticket_id` and an error of the form:\n\n```json\n{\"ticket_id\": \"\", \"error\": \"repo_id '\u003Cvalue>' is not registered on this board.  Available repos: \u003Clist>.  Verify the repo_id matches one listed by GET \u002Frepos on the target board, or check that the agent is connected to the correct board.\"}\n```\n\nValidation is best-effort: when the repo list is unreachable (network error, timeout), the check is\nskipped and filing proceeds without validation — the board API's own 404 is the fallback guard.\n\n## ID resolution\n\nBoth `ticket_poll` and `ticket_poll_batch` resolve paraphrased \u002F abbreviated ticket IDs against the\nlive board before making any per-ticket request. This means you can pass an ID derived from\nnarrative text (e.g. `...-my-ticket-a3f2`) and it will be mapped to the full ticket ID on the board.\nResolution tries, in order:\n\n1. **Exact match** — the candidate ID appears verbatim on the board.\n1. **Hash-suffix match** — the last 4 hex chars (e.g. `a3f2`) uniquely match one ticket.\n1. **Slug-substring match** — the non-timestamp portion appears as a substring of exactly one\n   ticket's full ID.\n\nWhen resolution succeeds, the resolved full ID is used for the request and returned in the response.\nWhen it fails — the candidate is ambiguous or the board is unreachable — the original ID is still\nattempted (which may surface a 404).\n\n## Safety\n\n- **`ticket_poll` \u002F `ticket_poll_batch` \u002F `list_stale_ready_tickets` are read-only** — GET only; no\n  state mutation is possible through these tools.\n- **`merge_pull_request` and `prioritize_all_open_tickets` are mutating** — they issue POST requests\n  that alter ticket state. Only call them when the preconditions are met: `merge_pull_request`\n  requires an approved PR in `waiting_auto_merge` or `human_mr_approval` state;\n  `prioritize_all_open_tickets` should be called when the operator asks to prioritize tickets. Do\n  not call either speculatively.\n- **Roster-first routing** — prefers the component roster (`component_request`) when available;\n  falls back to the direct board API when the roster is absent. This means the tools share the same\n  connectivity path as `component_request` and are equally reliable.\n- **Timeout** — each request has a short timeout; failures are per-ticket (one down ticket won't\n  break the batch).\n- **Connectivity vs. state.** A tool call failure (timeout, unreachable, HTTP 5xx, DNS error) is a\n  transient I\u002FO error — it tells you nothing about the ticket's actual state. Do **not** conflate\n  \"the API returned an error\" with \"the ticket is closed,\" \"the ticket is being tracked by a\n  monitor,\" or any other conclusion about the ticket. When a call fails, report the failure honestly\n  (e.g. \"could not reach the board API — will retry\") and do not fabricate state from the absence of\n  data. Only state facts about a ticket when you have a successful response containing those facts.\n- **Graceful degradation via ticket-state cache.** When the board API is unreachable, `ticket_poll`\n  falls back to the last-known state from an in-memory cache (populated by mill push events and\n  prior successful polls). The cached response includes a `cache_caveat` field with a staleness note\n  (e.g. `[last-known state — board API unreachable; showing cached state from 120s ago]`). Use this\n  to surface last-known state with an honest caveat rather than saying \"I can't confirm.\" Entries\n  older than 1 hour are flagged as `stale`. Only state facts about a ticket when you have a\n  successful response containing those facts.\n\n## Example calls\n\n```python\n# Basic state check\nticket_poll(\"20250101T120000Z-my-ticket-a1b2\")\n\n# Bulk triage of blocked tickets — fetch all at once, then classify\nticket_poll_batch(\n    [\n        \"20250101T120000Z-ticket-a-a1b2\",\n        \"20250102T090000Z-ticket-b-c3d4\",\n        \"20250102T150000Z-ticket-c-e5f6\",\n    ]\n)\n# → inspect each ticket's data.events history to identify failure signatures:\n#   \"implement-loop\u002F3of3\", \"git-failure\", \"capability-gap\", ...\n\n# Combined with component_request for double-check (terminal-state verification)\n# 1. ticket_poll(\"20250101T120000Z-my-ticket-a1b2\")     → state: \"DONE\"\n# 2. component_request(\"mill\", \"GET\", \"\u002Ftickets\u002F...\")    → confirm: \"DONE\"\n\n# Merge an approved PR when a ticket is in waiting_auto_merge or human_mr_approval\nmerge_pull_request(\"20250101T120000Z-my-ticket-a1b2\")\n# → \"HTTP 200\\n{\\\"status\\\": \\\"merged\\\", ...}\"\n\n# Prioritize all open, unflagged tickets in a single call\nprioritize_all_open_tickets()\n# → {\"prioritized\": 5, \"skipped\": 2, \"errors\": 0, \"total_open\": 7, \"results\": [...]}\n\n# Detect tickets stuck in the ready queue\nlist_stale_ready_tickets()\n# → {\"stale_ready_count\": 2, \"total_ready\": 5, \"threshold_minutes\": 10,\n#    \"stale_tickets\": [{\"ticket_id\": \"...\", \"staleness\": \"15m\", ...}, ...]}\n```\n",{},"main","c1d7c05ced8b81c2750ddc6e5e49a7803fc90940","src\u002Frobotsix_chat\u002Fticket_poll","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 ticket_poll",{"tool":34,"command":35},"bunx","bunx skills add damien-robotsix\u002Frobotsix-chat --skill ticket_poll",{"tool":37,"command":38},"pnpm","pnpm dlx skills add damien-robotsix\u002Frobotsix-chat --skill ticket_poll","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fticket_poll\u002Fskill.md",true,[42,48,52,56,60,64,68,72],{"path":43,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":46,"sourceHtmlUrl":47},"__init__.py","SCRIPT","脚本",13344,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fticket_poll\u002F__init__.py",{"path":49,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":50,"sourceHtmlUrl":51},"_internal.py",10292,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fticket_poll\u002F_internal.py",{"path":53,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":54,"sourceHtmlUrl":55},"cache.py",3526,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fticket_poll\u002Fcache.py",{"path":57,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":58,"sourceHtmlUrl":59},"helpers.py",12255,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fticket_poll\u002Fhelpers.py",{"path":61,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":62,"sourceHtmlUrl":63},"mill_states.py",3639,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fticket_poll\u002Fmill_states.py",{"path":65,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":66,"sourceHtmlUrl":67},"ticket_poll_queue.py",22431,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fticket_poll\u002Fticket_poll_queue.py",{"path":69,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":70,"sourceHtmlUrl":71},"ticket_poll_read.py",16804,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fticket_poll\u002Fticket_poll_read.py",{"path":73,"resourceType":44,"resourceTypeDesc":45,"sizeBytes":74,"sourceHtmlUrl":75},"ticket_poll_write.py",35049,"https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fticket_poll\u002Fticket_poll_write.py",[77,83,89,95,101,107],{"skillNo":78,"name":79,"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":80,"categories":81,"keywords":82,"publishedAt":18},"01M75TTQ70FE02S8DNAB423T5H","volume_tools","https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fvolume_tools\u002Fskill.md",[],[],{"skillNo":84,"name":85,"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":86,"categories":87,"keywords":88,"publishedAt":18},"01M75TTHW71NXKXW144682SPF1","subsessions","https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Fsubsessions\u002Fskill.md",[],[],{"skillNo":90,"name":91,"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":92,"categories":93,"keywords":94,"publishedAt":18},"01M75TTGBAFPVH6759BNB3G3NR","security","https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Frepo\u002Fsecurity\u002Fskill.md",[],[],{"skillNo":96,"name":97,"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":98,"categories":99,"keywords":100,"publishedAt":18},"01M75TTCZN8GTQQ92GR7Z6E7Y2","direct","https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Frepo\u002Fdirect\u002Fskill.md",[],[],{"skillNo":102,"name":103,"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":104,"categories":105,"keywords":106,"publishedAt":18},"01M75TT98KF65BJQNPQ61GQFKV","actions","https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Frepo\u002Factions\u002Fskill.md",[],[],{"skillNo":108,"name":109,"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":110,"categories":111,"keywords":112,"publishedAt":18},"01M75TT6G40RCR0E5P4KFP7ZEN","render_url","https:\u002F\u002Fgithub.com\u002Fdamien-robotsix\u002Frobotsix-chat\u002Fblob\u002Fmain\u002Fsrc\u002Frobotsix_chat\u002Frender_url\u002Fskill.md",[],[]]