القائمة
Use Cursor through iii as a login-backed text provider or as a direct coding agent with durable local and cloud sessions.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/iii-hq/workers --skill cursorيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Build, structure, and validate polished responsive worker UI (React pages, function-trigger and trigger-activity renderers, configuration forms, and stylesheets) injected into the running iii console. Use when adding or changing a worker's console UI, especially when it must match the visual quality of database, console functions/triggers, iii-directory, and state; retain the shared header and visual system; work in narrow/mobile-sized panes; preserve state safely; hot reload; and ship without rebuilding the console.
Discovery entry point for the engine — search the live function catalog, read the skills, system prompts, and agent profiles that installed workers ship off local disk, browse the public iii workers registry over HTTP, and install new worker bundles. Reach for it first to find out which workers exist and how to call them.
Connect this engine to another iii engine over a long-lived WebSocket so functions call across the boundary. Wire stable ids with `forward:`/`expose:`; `bridge.invoke` is the ad-hoc escape hatch.
عرض SKILL.md
| name | cursor |
| description | Use Cursor through iii as a login-backed text provider or as a direct coding agent with durable local and cloud sessions. |
Use this worker when a task should be handled by a Cursor coding agent. Local execution defaults to the official Cursor Agent CLI ACP and reuses credentials created by cursor-agent login; it does not require CURSOR_API_KEY or the SDK Bridge. Use the official CLI's absolute path when an installation exposes it only as agent.
Select a cursor/* model in LLM Router for text-only chat through the normal Cursor login. The provider does not advertise router tools, vision, structured output, usage, or cost because Cursor ACP does not expose those raw-model contracts.
Call cursor::run for a blocking turn. run::start_and_wait is its standard alias.
Call cursor::start, subscribe to agent::events with the returned session ID as group_id, and call cursor::stop when asynchronous lifecycle control is needed.
Reuse session_id for follow-up turns. Local sessions must keep their original cwd; sdk-bridge sessions must also keep their original tool list.
Call cursor::status or cursor::sessions::list for durable lifecycle discovery.
Call cursor::auth::status to check login availability without returning account details or credentials.
Call cursor::models::list instead of guessing account-scoped model IDs. Login-backed results contain only ACP-compatible IDs and expose ACP default as auto; cursor-agent --list-models also contains CLI-only IDs that ACP rejects. Pass { "backend": "sdk-bridge" } for the cloud/API-key catalog.
Call cursor::usage only for cloud agents. Treat missing usage or cost as unreported, never as zero.
Login-backed local execution stays in Cursor's ask mode and cancels every permission request. Cursor ACP cannot enforce a per-request tool list, so omit tools; any explicit value is rejected. Cloud runs require the separately installed SDK Bridge and CURSOR_API_KEY, and default to neither working on the current branch nor creating a pull request.
The LLM Router provider functions are internal and denied to agents; use router::chat or router::complete through a selected cursor/* model. Read-only status, session, auth, and model discovery are allowed by the default policy; direct run, start, stop, and usage stay approval-gated.