[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CTA888ASXSRNX2V8KXDBDH":3,"skill-same:01M7CTA888ASXSRNX2V8KXDBDH":44},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7CTA888ASXSRNX2V8KXDBDH","cursor-sdk-e2e-dev",null,"Spin up a live local Omnigent server and exercise the Cursor SDK harness end-to-end — build cursor agents, run real turns, smoke-test, and bug-bash. Load when developing, testing, or debugging the cursor harness (omnigent\u002Finner\u002Fcursor_executor.py, cursor_harness.py, cursor_auth.py) or its auth \u002F model \u002F tool-bridge behavior.","roland-id-au\u002Fomniagent","roland-id-au","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2590653?v=4","01M7CT4DEBVK4R185WFWCWN4JD","Buck Chancey","01M7CT4DFGWX49CGE347EF4V6T",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Froland-id-au\u002Fomniagent\u002Fblob\u002Fdeploy\u002Froland-id-au-omniagent\u002Fwork\u002Fomnigent-main\u002F.claude\u002Fskills\u002Fcursor-sdk-e2e-dev\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cursor-sdk-e2e-dev\ndescription: Spin up a live local Omnigent server and exercise the Cursor SDK harness end-to-end — build cursor agents, run real turns, smoke-test, and bug-bash. Load when developing, testing, or debugging the cursor harness (omnigent\u002Finner\u002Fcursor_executor.py, cursor_harness.py, cursor_auth.py) or its auth \u002F model \u002F tool-bridge behavior.\n---\n\n# Cursor SDK harness: end-to-end dev & testing\n\nThe `cursor` harness drives the **Cursor Python SDK** (`cursor_sdk`, an\n`AsyncAgent` over a local bridge) and bridges Omnigent's `sys_*` tools into\nCursor as SDK `custom_tools`. This skill is the proven recipe for running it\n**for real** against a live local server — not just the unit tests.\n\n> The harness runs as a **local runner** from your current checkout, so\n> `omni run \u003Cbundle> --server \u003Curl>` exercises exactly the code you're on.\n\n## Prerequisites (check these first)\n\n1. **You're on the branch you want to test.** The cursor harness merged to\n   `main` (#203\u002F#204). Test on `main` unless validating a specific branch.\n2. **A Cursor API key is configured.** The SDK *requires* an API key\n   (`crsr_…`); there is no `cursor-agent login` path. Verify (booleans only —\n   never print the key):\n   ```bash\n   .venv\u002Fbin\u002Fpython -c \"from omnigent.onboarding.cursor_auth import cursor_api_key_configured; import os; print('config:', cursor_api_key_configured(), 'env:', bool(os.environ.get('CURSOR_API_KEY')))\"\n   ```\n   If both are `False`, run `omni setup` and register a Cursor key, or\n   `export CURSOR_API_KEY=crsr_…`.\n3. **`cursor-sdk` is installed** (a baseline dependency):\n   `.venv\u002Fbin\u002Fpython -c \"import cursor_sdk; print(cursor_sdk.__file__)\"`.\n4. **Network egress to Cursor's backend.** The bridge subprocess talks to\n   Cursor's own API; a turn that hangs or fails to connect on a locked-down\n   host is usually an egress problem, not a harness bug.\n\n## Step 1 — start a local server\n\n```bash\ncd \u002Fpath\u002Fto\u002Fomnigent\n.venv\u002Fbin\u002Fomni server --background          # spawns a detached server on a free loopback port\n.venv\u002Fbin\u002Fomni server status         # prints the URL, e.g. http:\u002F\u002F127.0.0.1:6767\n```\n\nUse the **printed URL** below as `$SERVER`. (You can also run a foreground\nserver on a fixed port with `omnigent server --port 7777 --no-open`.)\n\n## Step 2 — build a cursor agent bundle\n\nA spec with `spec_version` **must be a directory containing `config.yaml`** —\nnot a single `.yaml` file. Minimal cursor agent:\n\n```bash\nmkdir -p \u002Ftmp\u002Fcursor-dev\ncat > \u002Ftmp\u002Fcursor-dev\u002Fconfig.yaml \u003C\u003C'YAML'\nspec_version: 1\nname: cursor-dev\ndescription: Cursor SDK dev\u002Ftest agent.\nexecutor:\n  type: omnigent\n  config:\n    harness: cursor\n    # model: gpt-5            # optional; omit for cursor \"auto\"\nprompt: |\n  You are a terse test agent. Answer in as few words as possible.\nYAML\n```\n\nFor sub-agents, tools, guardrails\u002Fpolicies, copy the field shapes from\n`examples\u002Fpolly\u002Fconfig.yaml` and `examples\u002Fdebby\u002Fconfig.yaml`.\n\n## Step 3 — run a turn (and smoke-test)\n\n```bash\nSERVER=http:\u002F\u002F127.0.0.1:6767   # the URL from `omni server status`\ntimeout 280 .venv\u002Fbin\u002Fomni run \u002Ftmp\u002Fcursor-dev \\\n  -p \"Reply with exactly the single word: PONG\" \\\n  --server \"$SERVER\" 2>&1\n```\n\nA healthy run prints connection lines then the assistant reply (`PONG`). If\nthat works, the full stack is good: key, egress, bridge, harness.\n\n- **Shell \u002F file tools:** add `--tools coding`.\n- **Specific model:** add `--model gpt-5` (or `composer-1`, `auto`,\n  `databricks-claude-opus-4-8`, …).\n\n## Targeted scenarios\n\n| Goal | How |\n|------|-----|\n| Native tools (shell\u002Fedit\u002Fread) | `--tools coding`, prompt to create→read→edit a file and run a shell command; confirm it actually touches disk |\n| Bridged `sys_*` \u002F sub-agent dispatch | declare a sub-agent (`tools.agents`\u002F`spawn`), prompt the cursor agent to delegate — exercises the `custom_tools` daemon-thread bridge (`run_coroutine_threadsafe`) |\n| Model routing | run the same bundle with several `--model` values; note which actually runs |\n| Policy \u002F guardrail | add a guardrail that denies a keyword; confirm `PHASE_LLM_REQUEST`\u002F`PHASE_LLM_RESPONSE` blocks it |\n| Concurrency \u002F leaks | fire several `omni run … &` at once; then `pgrep -af \"cursor-sdk-bridge|cursor_sdk\"` to check for orphaned bridge subprocesses |\n\n## Gotchas (these cost real time)\n\n1. **`config.yaml`'s `server:` defaults to a *remote* server** (e.g. a\n   Databricks Apps URL). Omitting `--server` sends your turn to that remote\n   deploy — which may be **stale** and reject the cursor harness with\n   `executor.config.harness: must be one of […], got 'cursor'`. **Always pass\n   `--server http:\u002F\u002F127.0.0.1:\u003Cport>`** for local testing. (That allowlist is\n   `omnigent\u002Fspec\u002F_omnigent_compat.py`; if a *local* server rejects `cursor`,\n   it's running stale code — restart it from your checkout.)\n2. **A spec with `spec_version` must be a directory + `config.yaml`**, never a\n   single `.yaml` file.\n3. **Cursor needs a `crsr_` API key** (no CLI login). Resolution precedence:\n   spec `executor.auth` (api_key) > stored `cursor:` config block (`omni\n   setup`) > ambient `CURSOR_API_KEY`.\n4. **No Databricks gateway.** Cursor talks only to Cursor's backend, so a\n   `databricks-*` model is silently resolved to cursor `auto` — it will *not*\n   route through the AI Gateway like claude-sdk\u002Fcodex\u002Fpi.\n5. **Use a model id from the account's catalog.** Bare `gpt-5` is **not** valid;\n   the SDK rejects unknown ids. Valid examples seen live: `default`,\n   `composer-2.5`, `claude-opus-4-8`, `gpt-5.5`. Run with `--model` and read the\n   SDK's `Available models:` list to discover the live set.\n5. **Turns take 30–90s** — always wrap in `timeout 280`.\n6. **Local-runner topology:** `omni run \u003Cbundle> --server \u003Curl>` runs the\n   harness from your **current checkout**; the server only holds state. The\n   managed `omni server --background` server runs from whatever venv launched it.\n7. **Never print\u002Fecho the Cursor key** in logs or commands.\n\n## Code & tests\n\n- **Executor (SDK bridge):** `omnigent\u002Finner\u002Fcursor_executor.py`\n- **Wrap (HARNESS_CURSOR_* env → executor):** `omnigent\u002Finner\u002Fcursor_harness.py`\n- **Auth \u002F key resolution:** `omnigent\u002Fonboarding\u002Fcursor_auth.py`\n- **Spawn env:** `_build_cursor_spawn_env` in `omnigent\u002Fruntime\u002Fworkflow.py`\n\n```bash\n# Unit tests (use --frozen; the cwsandbox extra is unsatisfiable on public PyPI here)\nuv run --frozen --group test python -m pytest \\\n  tests\u002Finner\u002Ftest_cursor_executor.py \\\n  tests\u002Fruntime\u002Ftest_cursor_spawn_env.py \\\n  tests\u002Fonboarding\u002Ftest_cursor_auth.py -q\n# Gated end-to-end harness test\nuv run --frozen --group test python -m pytest tests\u002Fe2e\u002Fomnigent\u002Ftest_per_harness_cursor.py -q\n```\n\n## Bug-bash (fan out)\n\nTo stress the harness, run several scenario probes in parallel — each builds a\nbundle and runs real turns against the same `$SERVER`, then reports what broke.\nHighest-value targets: the `custom_tools` bridge (hangs \u002F lost tool results \u002F\nerrors reported as success), model routing, policy enforcement, streamed-output\nrendering, and orphaned bridge processes after teardown.\n\n## Known sharp edges (found via live bug-bash — \"as of this writing\")\n\nLive-observed cursor-harness behaviors to watch for while testing (some may be\nfixed by the time you read this — verify):\n\n- **Start failures are swallowed.** An invalid\u002Funavailable `--model` (or any\n  bridge start error) makes `omni run -p` exit **0 with empty output**, while\n  the server records a `failed` session + a `RuntimeError` item the user never\n  sees. If a turn returns nothing, check the session status \u002F items\n  (`GET \u002Fv1\u002Fsessions\u002F{id}\u002Fitems`) — don't assume success. (claude-sdk surfaces\n  such errors; cursor doesn't yet.)\n- **Built-in coding tools bypass `on:[tool_call]` policies.** Cursor's native\n  shell\u002Ffile tools (`--tools coding`) don't emit `tool_call` events, so\n  `on:[tool_call]` guardrails (e.g. `blast_radius`) never see them — a built-in\n  shell can run `git push --force` even under a DENY policy. **Bridged `sys_*`\n  tools *are* gated correctly.** Don't rely on `on:[tool_call]` guardrails for\n  cursor built-in tools.\n- **Run-on assistant text.** Adjacent assistant text blocks are concatenated\n  with no separator, so pre-tool narration can glue onto the post-tool answer.\n- **Non-graceful exit orphans the bridge.** Graceful teardown reaps it (the\n  #221 `aclose` fix works), but a `SIGKILL`\u002Fhard-exit leaves an orphaned\n  `cursor-sdk-bridge`. After hard kills, sweep `pgrep -af cursor-sdk-bridge`.\n\n## Cleanup\n\n```bash\n.venv\u002Fbin\u002Fomni server stop      # stop the managed background server\nrm -rf \u002Ftmp\u002Fcursor-dev          # remove scratch bundles\npgrep -af \"cursor-sdk-bridge\"   # confirm no orphaned bridge subprocesses linger\n```\n","# Cursor SDK harness: end-to-end dev & testing\n\nThe `cursor` harness drives the **Cursor Python SDK** (`cursor_sdk`, an\n`AsyncAgent` over a local bridge) and bridges Omnigent's `sys_*` tools into\nCursor as SDK `custom_tools`. This skill is the proven recipe for running it\n**for real** against a live local server — not just the unit tests.\n\n> The harness runs as a **local runner** from your current checkout, so\n> `omni run \u003Cbundle> --server \u003Curl>` exercises exactly the code you're on.\n\n## Prerequisites (check these first)\n\n1. **You're on the branch you want to test.** The cursor harness merged to\n   `main` (#203\u002F#204). Test on `main` unless validating a specific branch.\n2. **A Cursor API key is configured.** The SDK *requires* an API key\n   (`crsr_…`); there is no `cursor-agent login` path. Verify (booleans only —\n   never print the key):\n   ```bash\n   .venv\u002Fbin\u002Fpython -c \"from omnigent.onboarding.cursor_auth import cursor_api_key_configured; import os; print('config:', cursor_api_key_configured(), 'env:', bool(os.environ.get('CURSOR_API_KEY')))\"\n   ```\n   If both are `False`, run `omni setup` and register a Cursor key, or\n   `export CURSOR_API_KEY=crsr_…`.\n3. **`cursor-sdk` is installed** (a baseline dependency):\n   `.venv\u002Fbin\u002Fpython -c \"import cursor_sdk; print(cursor_sdk.__file__)\"`.\n4. **Network egress to Cursor's backend.** The bridge subprocess talks to\n   Cursor's own API; a turn that hangs or fails to connect on a locked-down\n   host is usually an egress problem, not a harness bug.\n\n## Step 1 — start a local server\n\n```bash\ncd \u002Fpath\u002Fto\u002Fomnigent\n.venv\u002Fbin\u002Fomni server --background          # spawns a detached server on a free loopback port\n.venv\u002Fbin\u002Fomni server status         # prints the URL, e.g. http:\u002F\u002F127.0.0.1:6767\n```\n\nUse the **printed URL** below as `$SERVER`. (You can also run a foreground\nserver on a fixed port with `omnigent server --port 7777 --no-open`.)\n\n## Step 2 — build a cursor agent bundle\n\nA spec with `spec_version` **must be a directory containing `config.yaml`** —\nnot a single `.yaml` file. Minimal cursor agent:\n\n```bash\nmkdir -p \u002Ftmp\u002Fcursor-dev\ncat > \u002Ftmp\u002Fcursor-dev\u002Fconfig.yaml \u003C\u003C'YAML'\nspec_version: 1\nname: cursor-dev\ndescription: Cursor SDK dev\u002Ftest agent.\nexecutor:\n  type: omnigent\n  config:\n    harness: cursor\n    # model: gpt-5            # optional; omit for cursor \"auto\"\nprompt: |\n  You are a terse test agent. Answer in as few words as possible.\nYAML\n```\n\nFor sub-agents, tools, guardrails\u002Fpolicies, copy the field shapes from\n`examples\u002Fpolly\u002Fconfig.yaml` and `examples\u002Fdebby\u002Fconfig.yaml`.\n\n## Step 3 — run a turn (and smoke-test)\n\n```bash\nSERVER=http:\u002F\u002F127.0.0.1:6767   # the URL from `omni server status`\ntimeout 280 .venv\u002Fbin\u002Fomni run \u002Ftmp\u002Fcursor-dev \\\n  -p \"Reply with exactly the single word: PONG\" \\\n  --server \"$SERVER\" 2>&1\n```\n\nA healthy run prints connection lines then the assistant reply (`PONG`). If\nthat works, the full stack is good: key, egress, bridge, harness.\n\n- **Shell \u002F file tools:** add `--tools coding`.\n- **Specific model:** add `--model gpt-5` (or `composer-1`, `auto`,\n  `databricks-claude-opus-4-8`, …).\n\n## Targeted scenarios\n\n| Goal | How |\n|------|-----|\n| Native tools (shell\u002Fedit\u002Fread) | `--tools coding`, prompt to create→read→edit a file and run a shell command; confirm it actually touches disk |\n| Bridged `sys_*` \u002F sub-agent dispatch | declare a sub-agent (`tools.agents`\u002F`spawn`), prompt the cursor agent to delegate — exercises the `custom_tools` daemon-thread bridge (`run_coroutine_threadsafe`) |\n| Model routing | run the same bundle with several `--model` values; note which actually runs |\n| Policy \u002F guardrail | add a guardrail that denies a keyword; confirm `PHASE_LLM_REQUEST`\u002F`PHASE_LLM_RESPONSE` blocks it |\n| Concurrency \u002F leaks | fire several `omni run … &` at once; then `pgrep -af \"cursor-sdk-bridge|cursor_sdk\"` to check for orphaned bridge subprocesses |\n\n## Gotchas (these cost real time)\n\n1. **`config.yaml`'s `server:` defaults to a *remote* server** (e.g. a\n   Databricks Apps URL). Omitting `--server` sends your turn to that remote\n   deploy — which may be **stale** and reject the cursor harness with\n   `executor.config.harness: must be one of […], got 'cursor'`. **Always pass\n   `--server http:\u002F\u002F127.0.0.1:\u003Cport>`** for local testing. (That allowlist is\n   `omnigent\u002Fspec\u002F_omnigent_compat.py`; if a *local* server rejects `cursor`,\n   it's running stale code — restart it from your checkout.)\n2. **A spec with `spec_version` must be a directory + `config.yaml`**, never a\n   single `.yaml` file.\n3. **Cursor needs a `crsr_` API key** (no CLI login). Resolution precedence:\n   spec `executor.auth` (api_key) > stored `cursor:` config block (`omni\n   setup`) > ambient `CURSOR_API_KEY`.\n4. **No Databricks gateway.** Cursor talks only to Cursor's backend, so a\n   `databricks-*` model is silently resolved to cursor `auto` — it will *not*\n   route through the AI Gateway like claude-sdk\u002Fcodex\u002Fpi.\n5. **Use a model id from the account's catalog.** Bare `gpt-5` is **not** valid;\n   the SDK rejects unknown ids. Valid examples seen live: `default`,\n   `composer-2.5`, `claude-opus-4-8`, `gpt-5.5`. Run with `--model` and read the\n   SDK's `Available models:` list to discover the live set.\n5. **Turns take 30–90s** — always wrap in `timeout 280`.\n6. **Local-runner topology:** `omni run \u003Cbundle> --server \u003Curl>` runs the\n   harness from your **current checkout**; the server only holds state. The\n   managed `omni server --background` server runs from whatever venv launched it.\n7. **Never print\u002Fecho the Cursor key** in logs or commands.\n\n## Code & tests\n\n- **Executor (SDK bridge):** `omnigent\u002Finner\u002Fcursor_executor.py`\n- **Wrap (HARNESS_CURSOR_* env → executor):** `omnigent\u002Finner\u002Fcursor_harness.py`\n- **Auth \u002F key resolution:** `omnigent\u002Fonboarding\u002Fcursor_auth.py`\n- **Spawn env:** `_build_cursor_spawn_env` in `omnigent\u002Fruntime\u002Fworkflow.py`\n\n```bash\n# Unit tests (use --frozen; the cwsandbox extra is unsatisfiable on public PyPI here)\nuv run --frozen --group test python -m pytest \\\n  tests\u002Finner\u002Ftest_cursor_executor.py \\\n  tests\u002Fruntime\u002Ftest_cursor_spawn_env.py \\\n  tests\u002Fonboarding\u002Ftest_cursor_auth.py -q\n# Gated end-to-end harness test\nuv run --frozen --group test python -m pytest tests\u002Fe2e\u002Fomnigent\u002Ftest_per_harness_cursor.py -q\n```\n\n## Bug-bash (fan out)\n\nTo stress the harness, run several scenario probes in parallel — each builds a\nbundle and runs real turns against the same `$SERVER`, then reports what broke.\nHighest-value targets: the `custom_tools` bridge (hangs \u002F lost tool results \u002F\nerrors reported as success), model routing, policy enforcement, streamed-output\nrendering, and orphaned bridge processes after teardown.\n\n## Known sharp edges (found via live bug-bash — \"as of this writing\")\n\nLive-observed cursor-harness behaviors to watch for while testing (some may be\nfixed by the time you read this — verify):\n\n- **Start failures are swallowed.** An invalid\u002Funavailable `--model` (or any\n  bridge start error) makes `omni run -p` exit **0 with empty output**, while\n  the server records a `failed` session + a `RuntimeError` item the user never\n  sees. If a turn returns nothing, check the session status \u002F items\n  (`GET \u002Fv1\u002Fsessions\u002F{id}\u002Fitems`) — don't assume success. (claude-sdk surfaces\n  such errors; cursor doesn't yet.)\n- **Built-in coding tools bypass `on:[tool_call]` policies.** Cursor's native\n  shell\u002Ffile tools (`--tools coding`) don't emit `tool_call` events, so\n  `on:[tool_call]` guardrails (e.g. `blast_radius`) never see them — a built-in\n  shell can run `git push --force` even under a DENY policy. **Bridged `sys_*`\n  tools *are* gated correctly.** Don't rely on `on:[tool_call]` guardrails for\n  cursor built-in tools.\n- **Run-on assistant text.** Adjacent assistant text blocks are concatenated\n  with no separator, so pre-tool narration can glue onto the post-tool answer.\n- **Non-graceful exit orphans the bridge.** Graceful teardown reaps it (the\n  #221 `aclose` fix works), but a `SIGKILL`\u002Fhard-exit leaves an orphaned\n  `cursor-sdk-bridge`. After hard kills, sweep `pgrep -af cursor-sdk-bridge`.\n\n## Cleanup\n\n```bash\n.venv\u002Fbin\u002Fomni server stop      # stop the managed background server\nrm -rf \u002Ftmp\u002Fcursor-dev          # remove scratch bundles\npgrep -af \"cursor-sdk-bridge\"   # confirm no orphaned bridge subprocesses linger\n```\n",{"name":5,"description":7},"deploy\u002Froland-id-au-omniagent","83ee3dcd78468bbe3baf4bb264a0c99a53aa0fec","work\u002Fomnigent-main\u002F.claude\u002Fskills\u002Fcursor-sdk-e2e-dev","https:\u002F\u002Fgithub.com\u002Froland-id-au\u002Fomniagent","https:\u002F\u002Fgithub.com\u002Froland-id-au","2026-09-16 03:15:34",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add roland-id-au\u002Fomniagent --skill cursor-sdk-e2e-dev",{"tool":36,"command":37},"bunx","bunx skills add roland-id-au\u002Fomniagent --skill cursor-sdk-e2e-dev",{"tool":39,"command":40},"pnpm","pnpm dlx skills add roland-id-au\u002Fomniagent --skill cursor-sdk-e2e-dev","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Froland-id-au\u002Fomniagent\u002Fblob\u002Fdeploy\u002Froland-id-au-omniagent\u002Fwork\u002Fomnigent-main\u002F.claude\u002Fskills\u002Fcursor-sdk-e2e-dev\u002FSKILL.md",true,[],[45,52,59,66,71,76],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M7CTDVNPM78AJ051GVDB44X5","deep-research","Research checklist and source-quality guidance for the archer e2e fixture.","https:\u002F\u002Fgithub.com\u002Froland-id-au\u002Fomniagent\u002Fblob\u002Fdeploy\u002Froland-id-au-omniagent\u002Fwork\u002Fomnigent-main\u002Ftests\u002Fresources\u002Fexamples\u002Farcher\u002Fskills\u002Fdeep-research\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7CTDS8SPN8P5GK1Q4SCSY7K","pi-e2e-xyz-greet-c4a8d5","Test greeter — pi skills e2e. The unique suffix c4a8d5 appears in the skill name so a string match in the agent's output proves Pi loaded this skill.","https:\u002F\u002Fgithub.com\u002Froland-id-au\u002Fomniagent\u002Fblob\u002Fdeploy\u002Froland-id-au-omniagent\u002Fwork\u002Fomnigent-main\u002Ftests\u002Fresources\u002Fagents\u002Fpi_skills_none\u002Fskills\u002Fpi-e2e-xyz-greet-c4a8d5\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7CTDP4R9F06966W78WNZS2Y","pi-e2e-xyz-count-d2f6e1","Test counter — pi skills e2e. The unique suffix d2f6e1 appears in the skill name so a string match in the agent's output proves Pi loaded this skill.","https:\u002F\u002Fgithub.com\u002Froland-id-au\u002Fomniagent\u002Fblob\u002Fdeploy\u002Froland-id-au-omniagent\u002Fwork\u002Fomnigent-main\u002Ftests\u002Fresources\u002Fagents\u002Fpi_skills_none\u002Fskills\u002Fpi-e2e-xyz-count-d2f6e1\u002FSKILL.md",[],[],{"skillNo":67,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7CTDKP4W1Q18ZCY0XANDSEG","https:\u002F\u002Fgithub.com\u002Froland-id-au\u002Fomniagent\u002Fblob\u002Fdeploy\u002Froland-id-au-omniagent\u002Fwork\u002Fomnigent-main\u002Ftests\u002Fresources\u002Fagents\u002Fpi_skills_list\u002Fskills\u002Fpi-e2e-xyz-greet-c4a8d5\u002FSKILL.md",[],[],{"skillNo":72,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7CTDFBMA3EBZNV7J380THGP","https:\u002F\u002Fgithub.com\u002Froland-id-au\u002Fomniagent\u002Fblob\u002Fdeploy\u002Froland-id-au-omniagent\u002Fwork\u002Fomnigent-main\u002Ftests\u002Fresources\u002Fagents\u002Fpi_skills_list\u002Fskills\u002Fpi-e2e-xyz-count-d2f6e1\u002FSKILL.md",[],[],{"skillNo":77,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7CTDCVTXTG72BKEV2HY7M6W","https:\u002F\u002Fgithub.com\u002Froland-id-au\u002Fomniagent\u002Fblob\u002Fdeploy\u002Froland-id-au-omniagent\u002Fwork\u002Fomnigent-main\u002Ftests\u002Fresources\u002Fagents\u002Fpi_skills_all\u002Fskills\u002Fpi-e2e-xyz-greet-c4a8d5\u002FSKILL.md",[],[]]