← AICtrlCONTENT HISTORY

Update to AICtrl

Snapshot Oct 25, 2026 · 00:00 UTC · version 1.2.0

WHAT CHANGED

Declared capabilities changed

Declared skills — Now says: [{"description":"Review the exact head revision of a pull request for actionable correctness, security, reliability, performance, and test findings without...

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save AICtrl and check future changes in Following.

Up to 10 plugins free · no card required.

All fields and original values.

Declared skills

Before

Oct 24, 2026 · 12:40 UTC

[{"description":"Review the exact head revision of a pull request for actionable correctness, security, reliability, performance, and test findings without modifying code. Use when the user says \"review this PR\", \"do a code review\", ...

After

Oct 25, 2026 · 00:00 UTC

[{"description":"Review the exact head revision of a pull request for actionable correctness, security, reliability, performance, and test findings without modifying code. Use when the user says \"review this PR\", \"do a code review\", ...

Full description

Before

Oct 24, 2026 · 12:40 UTC

aictrl.dev helps engineering teams inspect project context and backlogs, discover governed workflows, start versioned workflow runs, review run evidence, decide approval gates, and cancel active runs through ChatGPT.

After

Oct 25, 2026 · 00:00 UTC

Portable engineering skills with controlled AICtrl workflow execution

Short description

Before

Oct 24, 2026 · 12:40 UTC

Control engineering workflows

After

Oct 25, 2026 · 00:00 UTC

Engineering skills & workflows

Long description

Before

Oct 24, 2026 · 12:40 UTC

aictrl.dev helps engineering teams inspect project context and backlogs, discover governed workflows, start versioned workflow runs, review run evidence, decide approval gates, and cancel active runs through ChatGPT.

After

Oct 25, 2026 · 00:00 UTC

aictrl brings engineering skills and controlled delivery workflows to software teams that use aictrl.dev. What it does: - Skills that run in your session: turn requests into implementation-ready issues, review specs, implement changes a...

Compare saved observations

Download comparison JSON
Full technical diff · 19 changed fields

added /release/app_manifest/apps/aictrl

BEFORE
Field was absent
AFTER
{
  "id": "asdk_app_6a5d18a424c48191bd58114d73a14b38",
  "required": true
}

removed /release/app_manifest/apps/app-6a5d18a424c48191bd58114d73a14b38

BEFORE
{
  "id": "asdk_app_6a5d18a424c48191bd58114d73a14b38",
  "required": true
}
AFTER
Field is absent

changed /release/description

BEFORE
"aictrl.dev helps engineering teams inspect project context and backlogs, discover governed workflows, start versioned workflow runs, review run evidence, decide approval gates, and cancel active runs through ChatGPT."
AFTER
"Portable engineering skills with controlled AICtrl workflow execution"

changed /release/display_name

BEFORE
"aictrl.dev"
AFTER
"AICtrl"

changed /release/id

BEFORE
"pluginrel_96a0f2e720308191956686f47e8c1c42"
AFTER
"pluginrel_7162c47ae9288191b1bc7f2baa3b66fd"

changed /release/interface/brand_color

BEFORE
null
AFTER
"#4C6EF5"

changed /release/interface/capabilities

BEFORE
[]
AFTER
[
  "Read",
  "Write",
  "MCP"
]

changed /release/interface/composer_icon_dark_url

BEFORE
"https://files.openai.com/content?id=file_0000000081a882438f48d36161a94f54"
AFTER
null

changed /release/interface/composer_icon_url

BEFORE
"https://files.openai.com/content?id=file_0000000081a882438f48d36161a94f54"
AFTER
"https://files.openai.com/content?id=file_0000000052b88243bfcea7b7a20beaf8"

changed /release/interface/default_prompt

BEFORE
null
AFTER
"Turn this request into an implementation-ready issue."

changed /release/interface/default_prompts

BEFORE
null
AFTER
[
  "Turn this request into an implementation-ready issue.",
  "Implement this issue and prepare a merge-ready pull request.",
  "Review this pull request at its current head revision."
]

changed /release/interface/logo_url

BEFORE
"https://files.openai.com/content?id=file_00000000526881f48bce36c09e574dfb"
AFTER
"https://files.openai.com/content?id=file_0000000036d481f4a31f2e9a3fc406d8"

changed /release/interface/logo_url_dark

BEFORE
"https://files.openai.com/content?id=file_00000000526881f48bce36c09e574dfb"
AFTER
null

changed /release/interface/long_description

BEFORE
"aictrl.dev helps engineering teams inspect project context and backlogs, discover governed workflows, start versioned workflow runs, review run evidence, decide approval gates, and cancel active runs through ChatGPT."
AFTER
"aictrl brings engineering skills and controlled delivery workflows to software teams that use aictrl.dev.\n\nWhat it does:\n- Skills that run in your session: turn requests into implementation-ready issues, review specs, implement changes and prepare pull requests, review code at the current head revision, judge and reply to review findings, run root-cause analyses, plan measurements, polish UI, test agent usability, author and run workflows, and explain changes.\n- An aictrl.dev connector (OAuth) that lets you search connected repository context, update your project backlog, list and inspect published workflows, start a workflow run after you confirm its inputs and side effects, follow run status, approve or cancel gated steps, start PR Explanation or Code Review tasks, and record verdicts on code-review findings.\n\nWho it is for: software engineers and engineering leads whose organization has connected GitHub repositories to aictrl.dev.\n\nLimitations: the connector only sees the organizations, repositories, and workflows your aictrl.dev account can access. It does not push code itself; repository changes happen only inside workflow runs, which perform only the side effects their published definition declares and wait at gated steps for explicit approval. The skills work without an account; connector features need an aictrl.dev organization."

changed /release/interface/short_description

BEFORE
"Control engineering workflows"
AFTER
"Engineering skills & workflows"

changed /release/interface/website_url

BEFORE
"https://www.aictrl.dev"
AFTER
"https://aictrl.dev"

changed /release/keywords

BEFORE
[]
AFTER
[
  "sdlc",
  "engineering",
  "code-review",
  "workflow",
  "agent-skills"
]

changed /release/skills

BEFORE
[
  {
    "description": "Review the exact head revision of a pull request for actionable correctness, security, reliability, performance, and test findings without modifying code. Use when the user says \"review this PR\", \"do a code review\", \"find defects in this change\", or provides a pull or merge request identifier.",
    "interface": {
      "brand_color": null,
      "default_prompt": null,
      "display_name": "code-review",
      "icon_large_url": null,
      "icon_small_url": null,
      "iconography": "search",
      "short_description": "Review the exact head revision of a pull request for actionable correctness, security, reliability, performance, and test findings without modifying code. Use when the user says \"review this PR\", \"do a code review\", \"find defects in this change\", or provides a pull or merge request identifier."
    },
    "name": "code-review",
    "plugin_release_skill_id": "pluginrsk_6a6007ea01208191858106fa90d6be7d"
  },
  {
    "description": "Create an evidence-backed bug report with reproduction, expected and actual behavior, impact, code context, and a regression-test requirement. Use when the user says \"file a bug\", \"report this defect\", \"turn these symptoms into a ticket\", or describes broken or regressed behavior.",
    "interface": {
      "brand_color": null,
      "default_prompt": null,
      "display_name": "create-bug",
      "icon_large_url": null,
      "icon_small_url": null,
      "iconography": "default",
      "short_description": "Create an evidence-backed bug report with reproduction, expected and actual behavior, impact, code context, and a regression-test requirement. Use when the user says \"file a bug\", \"report this defect\", \"turn these symptoms into a ticket\", or describes broken or regressed behavior."
    },
    "name": "create-bug",
    "plugin_release_skill_id": "pluginrsk_6a6007ea54c48191bc5d57f8ef7ff5cf"
  },
  {
    "description": "Create a code-grounded engineering story or task with scope, acceptance criteria, test expectations, risks, and open questions. Use when the user says \"create an issue\", \"open a ticket\", \"make a backlog item\", or describes a feature or chore that should be tracked; delegate defects to create-bug.",
    "interface": {
      "brand_color": null,
      "default_prompt": null,
      "display_name": "create-issue",
      "icon_large_url": null,
      "icon_small_url": null,
      "iconography": "hierarchy",
      "short_description": "Create a code-grounded engineering story or task with scope, acceptance criteria, test expectations, risks, and open questions. Use when the user says \"create an issue\", \"open a ticket\", \"make a backlog item\", or describes a feature or chore that should be tracked; delegate defects to create-bug."
    },
    "name": "create-issue",
    "plugin_release_skill_id": "pluginrsk_6a6007eab698819190ebf98d7447d4b9"
  },
  {
    "description": "Create and validate an AICtrl workflow v2 YAML file with typed parameters, inline task nodes, mappings, conditions, loops, retries, triggers, and approval gates. Use when the user says \"create a workflow\", \"write workflow YAML\", \"automate this engineering process\", or asks for a file under .aictrl/workflows/.",
    "interface": {
      "brand_color": null,
      "default_prompt": null,
      "display_name": "create-workflow",
      "icon_large_url": null,
      "icon_small_url": null,
      "iconography": "hierarchy",
      "short_description": "Create and validate an AICtrl workflow v2 YAML file with typed parameters, inline task nodes, mappings, conditions, loops, retries, triggers, and approval gates. Use when the user says \"create a workflow\", \"write workflow YAML\", \"automate this engineering process\", or asks for a file under .aictrl/workflows/."
    },
    "name": "create-workflow",
    "plugin_release_skill_id": "pluginrsk_6a6007eb155c8191961456aae85f79aa"
  },
  {
    "description": "Professional design review of any UI — a marketing page OR a product internal (dashboard, table, list, detail view, settings, a flow). Actionable, located critique against orientation, information architecture, primary task, visual hierarchy, friction/cognitive load, accessibility, and — for app screens — density, states, navigation, consistency, and data legibility. Use when the user says \"review this design\", \"review this screen\", \"review this dashboard\", \"critique this UI\", \"is this UI good\", \"review this mock\", \"design review\", \"roast my design\", \"roast my landing page\", or drops an HTML file / screenshot for feedback.",
    "interface": {
      "brand_color": null,
      "default_prompt": null,
      "display_name": "design-review",
      "icon_large_url": null,
      "icon_small_url": null,
      "iconography": "pen",
      "short_description": "Professional design review of any UI — a marketing page OR a product internal (dashboard, table, list, detail view, settings, a flow). Actionable, located critique against orientation, information architecture, primary task, visual hierarchy, friction/cognitive load, accessibility, and — for app screens — density, states, navigation, consistency, and data legibility. Use when the user says \"review this design\", \"review this screen\", \"review this dashboard\", \"critique this UI\", \"is this UI good\", \"review this mock\", \"design review\", \"roast my design\", \"roast my landing page\", or drops an HTML file / screenshot for feedback."
    },
    "name": "design-review",
    "plugin_release_skill_id": "pluginrsk_6a6007eb62fc81918e950369a1714992"
  },
  {
    "description": "Implement an engineering issue through tests, code, review, and CI, with separate story and bug paths and an optional connected AICtrl workflow. Use when the user says \"implement issue 123\", \"fix this bug\", \"make this code change\", or \"take this ticket to a merge-ready PR\".",
    "interface": {
      "brand_color": null,
      "default_prompt": null,
      "display_name": "implement-code-change",
      "icon_large_url": null,
      "icon_small_url": null,
      "iconography": "code",
      "short_description": "Implement an engineering issue through tests, code, review, and CI, with separate story and bug paths and an optional connected AICtrl workflow. Use when the user says \"implement issue 123\", \"fix this bug\", \"make this code change\", or \"take this ticket to a merge-ready PR\"."
    },
    "name": "implement-code-change",
    "plugin_release_skill_id": "pluginrsk_6a6007ec701481919e4f68b0c4cb580e"
  },
  {
    "description": "Judge untriaged code-review findings for the current pull-request head as TRUE, FALSE, or UNCERTAIN and choose FIX, DEFER, or IGNORE without changing code. Use when the user says \"triage review findings\", \"judge these comments\", \"which findings are real\", or \"decide what to fix from this review\".",
    "interface": {
      "brand_color": null,
      "default_prompt": null,
      "display_name": "judge-review-findings",
      "icon_large_url": null,
      "icon_small_url": null,
      "iconography": "hierarchy",
      "short_description": "Judge untriaged code-review findings for the current pull-request head as TRUE, FALSE, or UNCERTAIN and choose FIX, DEFER, or IGNORE without changing code. Use when the user says \"triage review findings\", \"judge these comments\", \"which findings are real\", or \"decide what to fix from this review\"."
    },
    "name": "judge-review-findings",
    "plugin_release_skill_id": "pluginrsk_6a6007ecbc608191a3df14a0266a3393"
  },
  {
    "description": "Create a measurement plan for a feature using the Goal-Question-Metric (GQM) structure — defines a measurement goal, learning objectives, metrics, and implementation (product analytics events, warehouse tables, event pipeline). Use when user says 'measurement plan', 'GQM', 'goal question metric', 'goal-question-metric', 'measurement goal', 'how do we measure this', 'what metrics for this feature', 'tracking plan', 'analytics requirements', 'how do we know if this works', 'define KPIs for', or when planning a new feature and analytics instrumentation is needed.",
    "interface": {
      "brand_color": null,
      "default_prompt": null,
      "display_name": "measurement-plan",
      "icon_large_url": null,
      "icon_small_url": null,
      "iconography": "hierarchy",
      "short_description": "Create a measurement plan for a feature using the Goal-Question-Metric (GQM) structure — defines a measurement goal, learning objectives, metrics, and implementation (product analytics events, warehouse tables, event pipeline). Use when user says 'measurement plan', 'GQM', 'goal question metric', 'goal-question-metric', 'measurement goal', 'how do we measure this', 'what metrics for this feature', 'tracking plan', 'analytics requirements', 'how do we know if this works', 'define KPIs for', or when planning a new feature and analytics instrumentation is needed."
    },
    "name": "measurement-plan",
    "plugin_release_skill_id": "pluginrsk_6a6007ed24d4819193bd8514364bc17e"
  },
  {
    "description": "End-to-end pipeline for producing a narrated product demo video from any repo with a web UI — the agent discovers and boots the app locally, preps demo data and auth, writes the narration and a scripted browser journey, records a time-locked Playwright take synced to an ElevenLabs voiceover, assembles a 1080p MP4 with branded title/agenda/end cards, and builds a publish kit (faststart MP4, 720p, poster, SRT captions, embed snippet, optional GCS/S3/YouTube upload). Use when the user says 'record a demo video', 'make a product demo', 'demo video for this app/repo', or wants to re-record an existing demo after UI changes.",
    "interface": {
      "brand_color": null,
      "default_prompt": null,
      "display_name": "recording-product-demo",
      "icon_large_url": null,
      "icon_small_url": null,
      "iconography": "code",
      "short_description": "End-to-end pipeline for producing a narrated product demo video from any repo with a web UI — the agent discovers and boots the app locally, preps demo data and auth, writes the narration and a scripted browser journey, records a time-locked Playwright take synced to an ElevenLabs voiceover, assembles a 1080p MP4 with branded title/agenda/end cards, and builds a publish kit (faststart MP4, 720p, poster, SRT captions, embed snippet, optional GCS/S3/YouTube upload). Use when the user says 'record a demo video', 'make a product demo', 'demo video for this app/repo', or wants to re-record an existing demo after UI changes."
    },
    "name": "recording-product-demo",
    "plugin_release_skill_id": "pluginrsk_6a6007eda420819195f022f95fdedb2f"
  },
  {
    "description": "Judge current-head review findings, fix accepted defects, run verification, post evidence-backed replies, and request bounded re-review. Use when the user says \"address review comments\", \"reply to code review\", \"fix accepted findings\", or \"get this PR through review\".",
    "interface": {
      "brand_color": null,
      "default_prompt": null,
      "display_name": "reply-to-code-review",
      "icon_large_url": null,
      "icon_small_url": null,
      "iconography": "chat",
      "short_description": "Judge current-head review findings, fix accepted defects, run verification, post evidence-backed replies, and request bounded re-review. Use when the user says \"address review comments\", \"reply to code review\", \"fix accepted findings\", or \"get this PR through review\"."
    },
    "name": "reply-to-code-review",
    "plugin_release_skill_id": "pluginrsk_6a6007edfe9c8191ac3b4171e2acc75f"
  },
  {
    "description": "Review an engineering issue or specification against repository evidence for ambiguity, missing acceptance criteria, hidden scope, test gaps, and implementation risk. Use when the user says \"review this spec\", \"check issue 123\", \"is this ready to build\", or \"find gaps in this ticket\".",
    "interface": {
      "brand_color": null,
      "default_prompt": null,
      "display_name": "spec-review",
      "icon_large_url": null,
      "icon_small_url": null,
      "iconography": "search",
      "short_description": "Review an engineering issue or specification against repository evidence for ambiguity, missing acceptance criteria, hidden scope, test gaps, and implementation risk. Use when the user says \"review this spec\", \"check issue 123\", \"is this ready to build\", or \"find gaps in this ticket\"."
    },
    "name": "spec-review",
    "plugin_release_skill_id": "pluginrsk_6a6007ee4cdc8191bf4717ffa5ed6cf5"
  }
]
AFTER
[
  {
    "description": "Review the exact head revision of a pull request for actionable correctness, security, reliability, performance, and test findings without modifying code. Use when the user says \"review this PR\", \"do a code review\", \"find defects in this change\", or provides a pull or merge request identifier.",
    "interface": {
      "brand_color": null,
      "default_prompt": null,
      "display_name": "code-review",
      "icon_large_url": null,
      "icon_small_url": null,
      "iconography": "code",
      "short_description": "Review the exact head revision of a pull request for actionable correctness, security, reliability, performance, and test findings without modifying code. Use when the user says \"review this PR\", \"do a code review\", \"find defects in this change\", or provides a pull or merge request identifier."
    },
    "name": "code-review",
    "plugin_release_skill_id": "pluginrsk_6ad28a848f788191817e218dac43d6f3"
  },
  {
    "description": "Create an evidence-backed bug report with reproduction, expected and actual behavior, impact, code context, and a regression-test requirement. Use when the user says \"file a bug\", \"report this defect\", \"turn these symptoms into a ticket\", or describes broken or regressed behavior.",
    "interface": {
      "brand_color": null,
      "default_prompt": null,
      "display_name": "create-bug",
      "icon_large_url": null,
      "icon_small_url": null,
      "iconography": "radar",
      "short_description": "Create an evidence-backed bug report with reproduction, expected and actual behavior, impact, code context, and a regression-test requirement. Use when the user says \"file a bug\", \"report this defect\", \"turn these symptoms into a ticket\", or describes broken or regressed behavior."
    },
    "name": "create-bug",
    "plugin_release_skill_id": "pluginrsk_6ad28a833f448191b8161aa3baba1232"
  },
  {
    "description": "Create a code-grounded engineering story or task with scope, acceptance criteria, test expectations, risks, and open questions. Use when the user says \"create an issue\", \"open a ticket\", \"make a backlog item\", or describes a feature or chore that should be tracked; delegate defects to create-bug.",
    "interface": {
      "brand_color": null,
      "default_prompt": null,
      "display_name": "create-issue",
      "icon_large_url": null,
      "icon_small_url": null,
      "iconography": "hierarchy",
      "short_description": "Create a code-grounded engineering story or task with scope, acceptance criteria, test expectations, risks, and open questions. Use when the user says \"create an issue\", \"open a ticket\", \"make a backlog item\", or describes a feature or chore that should be tracked; delegate defects to create-bug."
    },
    "name": "create-issue",
    "plugin_release_skill_id": "pluginrsk_6ad28a86dd708191b91c88fd5ab7ed72"
  },
  {
    "description": "Draft or improve a reviewer-ready pull request title and body from an exact revision, linked issue, implementation context, and verification evidence. Use when the user says \"create a PR\", \"draft a PR\", \"write the PR body\", \"improve this pull request description\", or \"update the PR title and body\".",
    "interface": {
      "brand_color": null,
      "default_prompt": null,
      "display_name": "create-pr",
      "icon_large_url": null,
      "icon_small_url": null,
      "iconography": "code",
      "short_description": "Draft or improve a reviewer-ready pull request title and body from an exact revision, linked issue, implementation context, and verification evidence. Use when the user says \"create a PR\", \"draft a PR\", \"write the PR body\", \"improve this pull request description\", or \"update the PR title and body\"."
    },
    "name": "create-pr",
    "plugin_release_skill_id": "pluginrsk_6ad28a835d9881918fd940af771d2538"
  },
  {
    "description": "Create and validate an aictrl.dev workflow v2 YAML file with typed parameters, inline task nodes, mappings, conditions, loops, retries, triggers, and approval gates. Use when the user says \"create a workflow\", \"write workflow YAML\", \"automate this engineering process\", or asks for a file under .aictrl/workflows/.",
    "interface": {
      "brand_color": null,
      "default_prompt": null,
      "display_name": "create-workflow",
      "icon_large_url": null,
      "icon_small_url": null,
      "iconography": "hierarchy",
      "short_description": "Create and validate an aictrl.dev workflow v2 YAML file with typed parameters, inline task nodes, mappings, conditions, loops, retries, triggers, and approval gates. Use when the user says \"create a workflow\", \"write workflow YAML\", \"automate this engineering process\", or asks for a file under .aictrl/workflows/."
    },
    "name": "create-workflow",
    "plugin_release_skill_id": "pluginrsk_6ad28a87deac819191615d8a5ab9fc8d"
  },
  {
    "description": "Professional design review of any UI — a marketing page OR a product internal (dashboard, table, list, detail view, settings, a flow). Actionable, located critique against orientation, information architecture (within and across screens), primary task, visual hierarchy, friction/cognitive load, accessibility, and — for app screens — density, states, navigation, consistency, and data legibility. Use when the user says \"review this design\", \"review this screen\", \"review this dashboard\", \"critique this UI\", \"is this UI good\", \"review this mock\", \"design review\", \"roast my design\", \"roast my landing page\", or drops an HTML file / screenshot for feedback.",
    "interface": {
      "brand_color": null,
      "default_prompt": null,
      "display_name": "design-review",
      "icon_large_url": null,
      "icon_small_url": null,
      "iconography": "pen",
      "short_description": "Professional design review of any UI — a marketing page OR a product internal (dashboard, table, list, detail view, settings, a flow). Actionable, located critique against orientation, information architecture (within and across screens), primary task, visual hierarchy, friction/cognitive load, accessibility, and — for app screens — density, states, navigation, consistency, and data legibility. Use when the user says \"review this design\", \"review this screen\", \"review this dashboard\", \"critique this UI\", \"is this UI good\", \"review this mock\", \"design review\", \"roast my design\", \"roast my landing page\", or drops an HTML file / screenshot for feedback."
    },
    "name": "design-review",
    "plugin_release_skill_id": "pluginrsk_6ad28a87ea488191adeed201dfa83f48"
  },
  {
    "description": "Discover, inspect, start, monitor, approve, or cancel an existing published aictrl.dev workflow with explicit authorization and durable run handoff. Use when the user says \"run a workflow\", \"start this aictrl workflow\", \"monitor workflow run\", \"approve workflow step\", or \"cancel workflow run\".",
    "interface": {
      "brand_color": null,
      "default_prompt": null,
      "display_name": "execute-workflow",
      "icon_large_url": null,
      "icon_small_url": null,
      "iconography": "hierarchy",
      "short_description": "Discover, inspect, start, monitor, approve, or cancel an existing published aictrl.dev workflow with explicit authorization and durable run handoff. Use when the user says \"run a workflow\", \"start this aictrl workflow\", \"monitor workflow run\", \"approve workflow step\", or \"cancel workflow run\"."
    },
    "name": "execute-workflow",
    "plugin_release_skill_id": "pluginrsk_6ad28a852c148191b0a81976d3d5be05"
  },
  {
    "description": "Turn a pull request, commit range, issue, ADR, or other completed change into a repository-grounded technical explainer that teaches the design, difficult trade-offs, and current rollout state. Use when the user says \"explain this change\", \"walk me through this PR\", \"what does this commit do\", \"document this change\", \"write an architecture explainer\", or \"teach me this subsystem\".",
    "interface": {
      "brand_color": null,
      "default_prompt": null,
      "display_name": "explain-change",
      "icon_large_url": null,
      "icon_small_url": null,
      "iconography": "code",
      "short_description": "Turn a pull request, commit range, issue, ADR, or other completed change into a repository-grounded technical explainer that teaches the design, difficult trade-offs, and current rollout state. Use when the user says \"explain this change\", \"walk me through this PR\", \"what does this commit do\", \"document this change\", \"write an architecture explainer\", or \"teach me this subsystem\"."
    },
    "name": "explain-change",
    "plugin_release_skill_id": "pluginrsk_6ad28a869b0c81919220f71feeaadee6"
  },
  {
    "description": "Implement an engineering issue through tests, code, review, and CI, with separate story and bug paths and an optional connected aictrl.dev workflow. Use when the user says \"implement issue 123\", \"fix this bug\", \"make this code change\", or \"take this ticket to a merge-ready PR\".",
    "interface": {
      "brand_color": null,
      "default_prompt": null,
      "display_name": "implement-code-change",
      "icon_large_url": null,
      "icon_small_url": null,
      "iconography": "code",
      "short_description": "Implement an engineering issue through tests, code, review, and CI, with separate story and bug paths and an optional connected aictrl.dev workflow. Use when the user says \"implement issue 123\", \"fix this bug\", \"make this code change\", or \"take this ticket to a merge-ready PR\"."
    },
    "name": "implement-code-change",
    "plugin_release_skill_id": "pluginrsk_6ad28a83ca188191a3d697c292b1a12c"
  },
  {
    "description": "Judge untriaged code-review findings for the current pull-request head as TRUE, FALSE, or UNCERTAIN and choose FIX, DEFER, or IGNORE without changing code. Use when the user says \"triage review findings\", \"judge these comments\", \"which findings are real\", or \"decide what to fix from this review\".",
    "interface": {
      "brand_color": null,
      "default_prompt": null,
      "display_name": "judge-review-findings",
      "icon_large_url": null,
      "icon_small_url": null,
      "iconography": "code",
      "short_description": "Judge untriaged code-review findings for the current pull-request head as TRUE, FALSE, or UNCERTAIN and choose FIX, DEFER, or IGNORE without changing code. Use when the user says \"triage review findings\", \"judge these comments\", \"which findings are real\", or \"decide what to fix from this review\"."
    },
    "name": "judge-review-findings",
    "plugin_release_skill_id": "pluginrsk_6ad28a8340dc81918d705353e27024eb"
  },
  {
    "description": "Create a measurement plan for a feature using the Goal-Question-Metric (GQM) structure — defines a measurement goal, learning objectives, metrics, and implementation (product analytics events, warehouse tables, event pipeline). Use when user says 'measurement plan', 'GQM', 'goal question metric', 'goal-question-metric', 'measurement goal', 'how do we measure this', 'what metrics for this feature', 'tracking plan', 'analytics requirements', 'how do we know if this works', 'define KPIs for', or when planning a new feature and analytics instrumentation is needed.",
    "interface": {
      "brand_color": null,
      "default_prompt": null,
      "display_name": "measurement-plan",
      "icon_large_url": null,
      "icon_small_url": null,
      "iconography": "chart",
      "short_description": "Create a measurement plan for a feature using the Goal-Question-Metric (GQM) structure — defines a measurement goal, learning objectives, metrics, and implementation (product analytics events, warehouse tables, event pipeline). Use when user says 'measurement plan', 'GQM', 'goal question metric', 'goal-question-metric', 'measurement goal', 'how do we measure this', 'what metrics for this feature', 'tracking plan', 'analytics requirements', 'how do we know if this works', 'define KPIs for', or when planning a new feature and analytics instrumentation is needed."
    },
    "name": "measurement-plan",
    "plugin_release_skill_id": "pluginrsk_6ad28a849424819187850bccc7c0737c"
  },
  {
    "description": "Judge current-head review findings, fix accepted defects, run verification, post evidence-backed replies, and request bounded re-review. Use when the user says \"address review comments\", \"reply to code review\", \"fix accepted findings\", or \"get this PR through review\".",
    "interface": {
      "brand_color": null,
      "default_prompt": null,
      "display_name": "reply-to-code-review",
      "icon_large_url": null,
      "icon_small_url": null,
      "iconography": "code",
      "short_description": "Judge current-head review findings, fix accepted defects, run verification, post evidence-backed replies, and request bounded re-review. Use when the user says \"address review comments\", \"reply to code review\", \"fix accepted findings\", or \"get this PR through review\"."
    },
    "name": "reply-to-code-review",
    "plugin_release_skill_id": "pluginrsk_6ad28a85e3908191942359820a643045"
  },
  {
    "description": "Perform an evidence-driven root cause analysis of an incident, recurring defect, failed release, or reliability problem. Use when the user says \"perform root-cause analysis\", \"do a five-whys analysis\", \"why did this happen\", \"analyze this incident systemically\", \"why does this keep recurring\", or \"find broader prevention opportunities\".",
    "interface": {
      "brand_color": null,
      "default_prompt": null,
      "display_name": "root-cause-analysis",
      "icon_large_url": null,
      "icon_small_url": null,
      "iconography": "radar",
      "short_description": "Perform an evidence-driven root cause analysis of an incident, recurring defect, failed release, or reliability problem. Use when the user says \"perform root-cause analysis\", \"do a five-whys analysis\", \"why did this happen\", \"analyze this incident systemically\", \"why does this keep recurring\", or \"find broader prevention opportunities\"."
    },
    "name": "root-cause-analysis",
    "plugin_release_skill_id": "pluginrsk_6ad28a85ad10819198e30fd04004893f"
  },
  {
    "description": "Review an engineering issue or specification against repository evidence for ambiguity, missing acceptance criteria, hidden scope, test gaps, and implementation risk. Use when the user says \"review this spec\", \"check issue 123\", \"is this ready to build\", or \"find gaps in this ticket\".",
    "interface": {
      "brand_color": null,
      "default_prompt": null,
      "display_name": "spec-review",
      "icon_large_url": null,
      "icon_small_url": null,
      "iconography": "search",
      "short_description": "Review an engineering issue or specification against repository evidence for ambiguity, missing acceptance criteria, hidden scope, test gaps, and implementation risk. Use when the user says \"review this spec\", \"check issue 123\", \"is this ready to build\", or \"find gaps in this ticket\"."
    },
    "name": "spec-review",
    "plugin_release_skill_id": "pluginrsk_6ad28a851b308191817f5cb25fae1d07"
  },
  {
    "description": "Polish an existing UI screen with evidence. Renders it at phone and desktop width, measures what screenshots hide (column alignment, field widths, label placement, tap targets, input font size, contrast, overflow, dead space, distance to the primary action), judges the look against a short polish rubric, fixes the source, then re-measures until the checks pass. Use when the user says \"polish this UI\", \"tighten the details\", \"this form looks off\", \"make this screen feel finished\", \"fix alignment and spacing\", or asks to bring a screen closer to a reference design. For information architecture, value proposition or flow critique, use design-review instead.",
    "interface": {
      "brand_color": null,
      "default_prompt": null,
      "display_name": "ui-polish",
      "icon_large_url": null,
      "icon_small_url": null,
      "iconography": "cursor",
      "short_description": "Polish an existing UI screen with evidence. Renders it at phone and desktop width, measures what screenshots hide (column alignment, field widths, label placement, tap targets, input font size, contrast, overflow, dead space, distance to the primary action), judges the look against a short polish rubric, fixes the source, then re-measures until the checks pass. Use when the user says \"polish this UI\", \"tighten the details\", \"this form looks off\", \"make this screen feel finished\", \"fix alignment and spacing\", or asks to bring a screen closer to a reference design. For information architecture, value proposition or flow critique, use design-review instead."
    },
    "name": "ui-polish",
    "plugin_release_skill_id": "pluginrsk_6ad28a882d2081918d2a01005a6a9e93"
  },
  {
    "description": "Usability-test any web page or HTML prototype with AI agents acting as first-time users, then improve it in a measured loop. Tester agents drive the page through a local Playwright harness that shows them only the accessibility tree (or only screenshots, for vision testers); success is verified from page state, never from the tester's claim. Produces a baseline scorecard, stops for approval, then runs design review, fixes and a re-test into a before/after report. Optional extras are a role and task model with a weighted cost score, simulated users from a fast System One model to screen layout hypotheses, and session replays for a visual report. Use when the user says \"usability-test this page\", \"run agent UX tests\", \"can a new user complete these tasks\", \"test this prototype with users\", \"simulate users on this design\", or \"test this UX hypothesis\". For a critique without testing use design-review; for measured visual polish use ui-polish.",
    "interface": {
      "brand_color": null,
      "default_prompt": null,
      "display_name": "ux-testing",
      "icon_large_url": null,
      "icon_small_url": null,
      "iconography": "radar",
      "short_description": "Usability-test any web page or HTML prototype with AI agents acting as first-time users, then improve it in a measured loop. Tester agents drive the page through a local Playwright harness that shows them only the accessibility tree (or only screenshots, for vision testers); success is verified from page state, never from the tester's claim. Produces a baseline scorecard, stops for approval, then runs design review, fixes and a re-test into a before/after report. Optional extras are a role and task model with a weighted cost score, simulated users from a fast System One model to screen layout hypotheses, and session replays for a visual report. Use when the user says \"usability-test this page\", \"run agent UX tests\", \"can a new user complete these tasks\", \"test this prototype with users\", \"simulate users on this design\", or \"test this UX hypothesis\". For a critique without testing use design-review; for measured visual polish use ui-polish."
    },
    "name": "ux-testing",
    "plugin_release_skill_id": "pluginrsk_6ad28a86df3481918d5a5efa49a806da"
  }
]

changed /release/version

BEFORE
"1.0.0"
AFTER
"1.2.0"
Full snapshot data
{
  "canonical_app_id": "asdk_app_6a5d18a424c48191bd58114d73a14b38",
  "connector_id": "asdk_app_6a5d18a424c48191bd58114d73a14b38",
  "created_at": "2026-07-19T18:34:12.391118Z",
  "discoverability": "LISTED",
  "id": "plugin_asdk_app_6a5d18a424c48191bd58114d73a14b38",
  "is_template": false,
  "is_template_instance": false,
  "name": "app-6a5d18a424c48191bd58114d73a14b38",
  "release": {
    "app_ids": [
      "asdk_app_6a5d18a424c48191bd58114d73a14b38"
    ],
    "app_manifest": {
      "apps": {
        "aictrl": {
          "id": "asdk_app_6a5d18a424c48191bd58114d73a14b38",
          "required": true
        }
      }
    },
    "app_templates": [],
    "description": "Portable engineering skills with controlled AICtrl workflow execution",
    "display_name": "AICtrl",
    "id": "pluginrel_7162c47ae9288191b1bc7f2baa3b66fd",
    "interface": {
      "brand_color": "#4C6EF5",
      "capabilities": [
        "Read",
        "Write",
        "MCP"
      ],
      "category": "Developer Tools",
      "composer_icon_dark_url": null,
      "composer_icon_url": "https://files.openai.com/content?id=file_0000000052b88243bfcea7b7a20beaf8",
      "default_prompt": "Turn this request into an implementation-ready issue.",
      "default_prompts": [
        "Turn this request into an implementation-ready issue.",
        "Implement this issue and prepare a merge-ready pull request.",
        "Review this pull request at its current head revision."
      ],
      "developer_name": "aictrl.dev",
      "logo_url": "https://files.openai.com/content?id=file_0000000036d481f4a31f2e9a3fc406d8",
      "logo_url_dark": null,
      "long_description": "aictrl brings engineering skills and controlled delivery workflows to software teams that use aictrl.dev.\n\nWhat it does:\n- Skills that run in your session: turn requests into implementation-ready issues, review specs, implement changes and prepare pull requests, review code at the current head revision, judge and reply to review findings, run root-cause analyses, plan measurements, polish UI, test agent usability, author and run workflows, and explain changes.\n- An aictrl.dev connector (OAuth) that lets you search connected repository context, update your project backlog, list and inspect published workflows, start a workflow run after you confirm its inputs and side effects, follow run status, approve or cancel gated steps, start PR Explanation or Code Review tasks, and record verdicts on code-review findings.\n\nWho it is for: software engineers and engineering leads whose organization has connected GitHub repositories to aictrl.dev.\n\nLimitations: the connector only sees the organizations, repositories, and workflows your aictrl.dev account can access. It does not push code itself; repository changes happen only inside workflow runs, which perform only the side effects their published definition declares and wait at gated steps for explicit approval. The skills work without an account; connector features need an aictrl.dev organization.",
      "plugin_category_id": "developer tools",
      "privacy_policy_url": "https://aictrl.dev/privacy",
      "screenshot_urls": [],
      "short_description": "Engineering skills & workflows",
      "terms_of_service_url": "https://aictrl.dev/terms",
      "website_url": "https://aictrl.dev"
    },
    "keywords": [
      "sdlc",
      "engineering",
      "code-review",
      "workflow",
      "agent-skills"
    ],
    "onboarding_skill_name": null,
    "requires_local_executor": false,
    "skills": [
      {
        "description": "Review the exact head revision of a pull request for actionable correctness, security, reliability, performance, and test findings without modifying code. Use when the user says \"review this PR\", \"do a code review\", \"find defects in this change\", or provides a pull or merge request identifier.",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "code-review",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "code",
          "short_description": "Review the exact head revision of a pull request for actionable correctness, security, reliability, performance, and test findings without modifying code. Use when the user says \"review this PR\", \"do a code review\", \"find defects in this change\", or provides a pull or merge request identifier."
        },
        "name": "code-review",
        "plugin_release_skill_id": "pluginrsk_6ad28a848f788191817e218dac43d6f3"
      },
      {
        "description": "Create an evidence-backed bug report with reproduction, expected and actual behavior, impact, code context, and a regression-test requirement. Use when the user says \"file a bug\", \"report this defect\", \"turn these symptoms into a ticket\", or describes broken or regressed behavior.",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "create-bug",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "radar",
          "short_description": "Create an evidence-backed bug report with reproduction, expected and actual behavior, impact, code context, and a regression-test requirement. Use when the user says \"file a bug\", \"report this defect\", \"turn these symptoms into a ticket\", or describes broken or regressed behavior."
        },
        "name": "create-bug",
        "plugin_release_skill_id": "pluginrsk_6ad28a833f448191b8161aa3baba1232"
      },
      {
        "description": "Create a code-grounded engineering story or task with scope, acceptance criteria, test expectations, risks, and open questions. Use when the user says \"create an issue\", \"open a ticket\", \"make a backlog item\", or describes a feature or chore that should be tracked; delegate defects to create-bug.",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "create-issue",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "hierarchy",
          "short_description": "Create a code-grounded engineering story or task with scope, acceptance criteria, test expectations, risks, and open questions. Use when the user says \"create an issue\", \"open a ticket\", \"make a backlog item\", or describes a feature or chore that should be tracked; delegate defects to create-bug."
        },
        "name": "create-issue",
        "plugin_release_skill_id": "pluginrsk_6ad28a86dd708191b91c88fd5ab7ed72"
      },
      {
        "description": "Draft or improve a reviewer-ready pull request title and body from an exact revision, linked issue, implementation context, and verification evidence. Use when the user says \"create a PR\", \"draft a PR\", \"write the PR body\", \"improve this pull request description\", or \"update the PR title and body\".",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "create-pr",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "code",
          "short_description": "Draft or improve a reviewer-ready pull request title and body from an exact revision, linked issue, implementation context, and verification evidence. Use when the user says \"create a PR\", \"draft a PR\", \"write the PR body\", \"improve this pull request description\", or \"update the PR title and body\"."
        },
        "name": "create-pr",
        "plugin_release_skill_id": "pluginrsk_6ad28a835d9881918fd940af771d2538"
      },
      {
        "description": "Create and validate an aictrl.dev workflow v2 YAML file with typed parameters, inline task nodes, mappings, conditions, loops, retries, triggers, and approval gates. Use when the user says \"create a workflow\", \"write workflow YAML\", \"automate this engineering process\", or asks for a file under .aictrl/workflows/.",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "create-workflow",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "hierarchy",
          "short_description": "Create and validate an aictrl.dev workflow v2 YAML file with typed parameters, inline task nodes, mappings, conditions, loops, retries, triggers, and approval gates. Use when the user says \"create a workflow\", \"write workflow YAML\", \"automate this engineering process\", or asks for a file under .aictrl/workflows/."
        },
        "name": "create-workflow",
        "plugin_release_skill_id": "pluginrsk_6ad28a87deac819191615d8a5ab9fc8d"
      },
      {
        "description": "Professional design review of any UI — a marketing page OR a product internal (dashboard, table, list, detail view, settings, a flow). Actionable, located critique against orientation, information architecture (within and across screens), primary task, visual hierarchy, friction/cognitive load, accessibility, and — for app screens — density, states, navigation, consistency, and data legibility. Use when the user says \"review this design\", \"review this screen\", \"review this dashboard\", \"critique this UI\", \"is this UI good\", \"review this mock\", \"design review\", \"roast my design\", \"roast my landing page\", or drops an HTML file / screenshot for feedback.",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "design-review",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "pen",
          "short_description": "Professional design review of any UI — a marketing page OR a product internal (dashboard, table, list, detail view, settings, a flow). Actionable, located critique against orientation, information architecture (within and across screens), primary task, visual hierarchy, friction/cognitive load, accessibility, and — for app screens — density, states, navigation, consistency, and data legibility. Use when the user says \"review this design\", \"review this screen\", \"review this dashboard\", \"critique this UI\", \"is this UI good\", \"review this mock\", \"design review\", \"roast my design\", \"roast my landing page\", or drops an HTML file / screenshot for feedback."
        },
        "name": "design-review",
        "plugin_release_skill_id": "pluginrsk_6ad28a87ea488191adeed201dfa83f48"
      },
      {
        "description": "Discover, inspect, start, monitor, approve, or cancel an existing published aictrl.dev workflow with explicit authorization and durable run handoff. Use when the user says \"run a workflow\", \"start this aictrl workflow\", \"monitor workflow run\", \"approve workflow step\", or \"cancel workflow run\".",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "execute-workflow",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "hierarchy",
          "short_description": "Discover, inspect, start, monitor, approve, or cancel an existing published aictrl.dev workflow with explicit authorization and durable run handoff. Use when the user says \"run a workflow\", \"start this aictrl workflow\", \"monitor workflow run\", \"approve workflow step\", or \"cancel workflow run\"."
        },
        "name": "execute-workflow",
        "plugin_release_skill_id": "pluginrsk_6ad28a852c148191b0a81976d3d5be05"
      },
      {
        "description": "Turn a pull request, commit range, issue, ADR, or other completed change into a repository-grounded technical explainer that teaches the design, difficult trade-offs, and current rollout state. Use when the user says \"explain this change\", \"walk me through this PR\", \"what does this commit do\", \"document this change\", \"write an architecture explainer\", or \"teach me this subsystem\".",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "explain-change",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "code",
          "short_description": "Turn a pull request, commit range, issue, ADR, or other completed change into a repository-grounded technical explainer that teaches the design, difficult trade-offs, and current rollout state. Use when the user says \"explain this change\", \"walk me through this PR\", \"what does this commit do\", \"document this change\", \"write an architecture explainer\", or \"teach me this subsystem\"."
        },
        "name": "explain-change",
        "plugin_release_skill_id": "pluginrsk_6ad28a869b0c81919220f71feeaadee6"
      },
      {
        "description": "Implement an engineering issue through tests, code, review, and CI, with separate story and bug paths and an optional connected aictrl.dev workflow. Use when the user says \"implement issue 123\", \"fix this bug\", \"make this code change\", or \"take this ticket to a merge-ready PR\".",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "implement-code-change",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "code",
          "short_description": "Implement an engineering issue through tests, code, review, and CI, with separate story and bug paths and an optional connected aictrl.dev workflow. Use when the user says \"implement issue 123\", \"fix this bug\", \"make this code change\", or \"take this ticket to a merge-ready PR\"."
        },
        "name": "implement-code-change",
        "plugin_release_skill_id": "pluginrsk_6ad28a83ca188191a3d697c292b1a12c"
      },
      {
        "description": "Judge untriaged code-review findings for the current pull-request head as TRUE, FALSE, or UNCERTAIN and choose FIX, DEFER, or IGNORE without changing code. Use when the user says \"triage review findings\", \"judge these comments\", \"which findings are real\", or \"decide what to fix from this review\".",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "judge-review-findings",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "code",
          "short_description": "Judge untriaged code-review findings for the current pull-request head as TRUE, FALSE, or UNCERTAIN and choose FIX, DEFER, or IGNORE without changing code. Use when the user says \"triage review findings\", \"judge these comments\", \"which findings are real\", or \"decide what to fix from this review\"."
        },
        "name": "judge-review-findings",
        "plugin_release_skill_id": "pluginrsk_6ad28a8340dc81918d705353e27024eb"
      },
      {
        "description": "Create a measurement plan for a feature using the Goal-Question-Metric (GQM) structure — defines a measurement goal, learning objectives, metrics, and implementation (product analytics events, warehouse tables, event pipeline). Use when user says 'measurement plan', 'GQM', 'goal question metric', 'goal-question-metric', 'measurement goal', 'how do we measure this', 'what metrics for this feature', 'tracking plan', 'analytics requirements', 'how do we know if this works', 'define KPIs for', or when planning a new feature and analytics instrumentation is needed.",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "measurement-plan",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "chart",
          "short_description": "Create a measurement plan for a feature using the Goal-Question-Metric (GQM) structure — defines a measurement goal, learning objectives, metrics, and implementation (product analytics events, warehouse tables, event pipeline). Use when user says 'measurement plan', 'GQM', 'goal question metric', 'goal-question-metric', 'measurement goal', 'how do we measure this', 'what metrics for this feature', 'tracking plan', 'analytics requirements', 'how do we know if this works', 'define KPIs for', or when planning a new feature and analytics instrumentation is needed."
        },
        "name": "measurement-plan",
        "plugin_release_skill_id": "pluginrsk_6ad28a849424819187850bccc7c0737c"
      },
      {
        "description": "Judge current-head review findings, fix accepted defects, run verification, post evidence-backed replies, and request bounded re-review. Use when the user says \"address review comments\", \"reply to code review\", \"fix accepted findings\", or \"get this PR through review\".",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "reply-to-code-review",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "code",
          "short_description": "Judge current-head review findings, fix accepted defects, run verification, post evidence-backed replies, and request bounded re-review. Use when the user says \"address review comments\", \"reply to code review\", \"fix accepted findings\", or \"get this PR through review\"."
        },
        "name": "reply-to-code-review",
        "plugin_release_skill_id": "pluginrsk_6ad28a85e3908191942359820a643045"
      },
      {
        "description": "Perform an evidence-driven root cause analysis of an incident, recurring defect, failed release, or reliability problem. Use when the user says \"perform root-cause analysis\", \"do a five-whys analysis\", \"why did this happen\", \"analyze this incident systemically\", \"why does this keep recurring\", or \"find broader prevention opportunities\".",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "root-cause-analysis",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "radar",
          "short_description": "Perform an evidence-driven root cause analysis of an incident, recurring defect, failed release, or reliability problem. Use when the user says \"perform root-cause analysis\", \"do a five-whys analysis\", \"why did this happen\", \"analyze this incident systemically\", \"why does this keep recurring\", or \"find broader prevention opportunities\"."
        },
        "name": "root-cause-analysis",
        "plugin_release_skill_id": "pluginrsk_6ad28a85ad10819198e30fd04004893f"
      },
      {
        "description": "Review an engineering issue or specification against repository evidence for ambiguity, missing acceptance criteria, hidden scope, test gaps, and implementation risk. Use when the user says \"review this spec\", \"check issue 123\", \"is this ready to build\", or \"find gaps in this ticket\".",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "spec-review",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "search",
          "short_description": "Review an engineering issue or specification against repository evidence for ambiguity, missing acceptance criteria, hidden scope, test gaps, and implementation risk. Use when the user says \"review this spec\", \"check issue 123\", \"is this ready to build\", or \"find gaps in this ticket\"."
        },
        "name": "spec-review",
        "plugin_release_skill_id": "pluginrsk_6ad28a851b308191817f5cb25fae1d07"
      },
      {
        "description": "Polish an existing UI screen with evidence. Renders it at phone and desktop width, measures what screenshots hide (column alignment, field widths, label placement, tap targets, input font size, contrast, overflow, dead space, distance to the primary action), judges the look against a short polish rubric, fixes the source, then re-measures until the checks pass. Use when the user says \"polish this UI\", \"tighten the details\", \"this form looks off\", \"make this screen feel finished\", \"fix alignment and spacing\", or asks to bring a screen closer to a reference design. For information architecture, value proposition or flow critique, use design-review instead.",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "ui-polish",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "cursor",
          "short_description": "Polish an existing UI screen with evidence. Renders it at phone and desktop width, measures what screenshots hide (column alignment, field widths, label placement, tap targets, input font size, contrast, overflow, dead space, distance to the primary action), judges the look against a short polish rubric, fixes the source, then re-measures until the checks pass. Use when the user says \"polish this UI\", \"tighten the details\", \"this form looks off\", \"make this screen feel finished\", \"fix alignment and spacing\", or asks to bring a screen closer to a reference design. For information architecture, value proposition or flow critique, use design-review instead."
        },
        "name": "ui-polish",
        "plugin_release_skill_id": "pluginrsk_6ad28a882d2081918d2a01005a6a9e93"
      },
      {
        "description": "Usability-test any web page or HTML prototype with AI agents acting as first-time users, then improve it in a measured loop. Tester agents drive the page through a local Playwright harness that shows them only the accessibility tree (or only screenshots, for vision testers); success is verified from page state, never from the tester's claim. Produces a baseline scorecard, stops for approval, then runs design review, fixes and a re-test into a before/after report. Optional extras are a role and task model with a weighted cost score, simulated users from a fast System One model to screen layout hypotheses, and session replays for a visual report. Use when the user says \"usability-test this page\", \"run agent UX tests\", \"can a new user complete these tasks\", \"test this prototype with users\", \"simulate users on this design\", or \"test this UX hypothesis\". For a critique without testing use design-review; for measured visual polish use ui-polish.",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "ux-testing",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "radar",
          "short_description": "Usability-test any web page or HTML prototype with AI agents acting as first-time users, then improve it in a measured loop. Tester agents drive the page through a local Playwright harness that shows them only the accessibility tree (or only screenshots, for vision testers); success is verified from page state, never from the tester's claim. Produces a baseline scorecard, stops for approval, then runs design review, fixes and a re-test into a before/after report. Optional extras are a role and task model with a weighted cost score, simulated users from a fast System One model to screen layout hypotheses, and session replays for a visual report. Use when the user says \"usability-test this page\", \"run agent UX tests\", \"can a new user complete these tasks\", \"test this prototype with users\", \"simulate users on this design\", or \"test this UX hypothesis\". For a critique without testing use design-review; for measured visual polish use ui-polish."
        },
        "name": "ux-testing",
        "plugin_release_skill_id": "pluginrsk_6ad28a86df3481918d5a5efa49a806da"
      }
    ],
    "version": "1.2.0"
  },
  "scope": "GLOBAL",
  "status": "ENABLED"
}

SHA-256 of public snapshot: f6c79c439aa9e6d26638f4024af94a3429eac040042346ae59e577dd157edfc8