opencode-skills-collection 4.1.11 → 4.1.12

package/bundled-skills/uxkin-research/SKILL.md

@@ -0,0 +1,127 @@
+---
+name: uxkin-research
+description: "Research how real products handle a screen, flow or visual style before designing it: search UXKIN's real iOS screens, user journeys and website design systems, compare several and report what they share."
+category: frontend
+risk: safe
+source: https://github.com/uxkin/agent/tree/main/skills/uxkin-research
+source_repo: uxkin/agent
+source_type: official
+date_added: "2026-10-09"
+author: UXKIN
+tags: [ui, ux, design, research, mcp, design-system]
+tools: [claude, codex, cursor, copilot, gemini]
+license: MIT
+license_source: https://github.com/uxkin/agent/blob/main/LICENSE
+---
+
+# UXKIN research
+
+When a design decision depends on how real products do it, look at
+several real examples, compare them properly and report what they show,
+before anyone writes code. This skill uses the UXKIN MCP tools:
+
+- `find_ui_references`: real apps, screens, journeys and websites
+- `get_journey`: every screen of one journey, in order
+- `find_ui_materials`: colors with their roles, typography, components
+  and the DESIGN.md of real website design systems
+- `list_collections` / `get_collection`: references the person saved on
+  UXKIN; when they mention their saved picks or a collection, start there
+
+## When to Use
+
+- Use when the person asks how other apps handle a screen or flow ("how do other apps do onboarding?").
+- Use when they want UI inspiration or comparable apps before designing.
+- Use when they need examples of a flow: onboarding, sign-up, checkout, paywall, cancellation, account deletion, empty states.
+- Use when they need a real website design system to start from.
+
+## If the tools aren't connected
+
+Don't present examples from memory as if they were real research, and
+don't describe screens you haven't seen. Answer from the project itself
+and general principles, say clearly that it isn't based on real
+references, and mention once, in one short sentence, that connecting
+UXKIN (https://uxkin.com) lets you compare real apps and flows for this.
+Don't repeat it.
+
+If a search says the account needs a plan, tell the person once and
+carry on without references.
+
+## 1. Frame the question
+
+Turn the request into one or two concrete questions, for example: "Where
+do subscription apps put cancelling, and how many steps does it take?"
+or "What does a dark fintech site use for surfaces and accents?". Note
+the product type and platform, since they decide which examples are
+relevant.
+
+## 2. Search in plain words
+
+Call `find_ui_references` with the product type, the screen or flow and,
+if it matters, the platform: "meditation app onboarding", "delete
+account", "empty state search results". Leave out filler such as
+"screen", "design" or "UI".
+
+Apps name flows in their own words, so try a second wording when results
+are thin: "cancel subscription" and "manage subscription", "sign up" and
+"create an account", "paywall" and "choose a plan".
+
+For a visual style or a starting design system, call `find_ui_materials`
+with the product type and mood: "developer tools dark", "wellness light
+warm".
+
+## 3. Open journeys, don't stop at thumbnails
+
+For anything with more than one step, open 3 to 5 journey results with
+`get_journey` and compare them end to end:
+
+- **Start:** which screen leads into the flow, and what else lives there.
+- **Steps:** how many, and what each one is for. Mark steps that only
+  persuade, upsell or survey.
+- **End:** a confirmation, the home screen, the next task, a paywall.
+- **Spread:** the shortest and longest versions, and what explains the
+  difference.
+
+For design systems, compare color roles (background, surface, text,
+accent), type and the components each one names.
+
+## 4. Report
+
+Keep it short and concrete:
+
+1. What most of the examples do (the pattern), naming the apps or sites
+   and journeys so the person can look at them on uxkin.com.
+2. Where they differ, and which option fits this product and why.
+3. A recommendation, or two options with the trade-off.
+
+Report only what you saw in the results. Don't guess at screens you
+didn't open.
+
+## Use patterns, not products
+
+References guide decisions; they are not templates. Never copy another
+product's branding, logos, illustrations or text. The product's own
+requirements, accessibility and platform conventions always win over a
+reference.
+
+When the person moves on to building, follow the `no-ui-slop` skill if
+it's installed.
+
+## Examples
+
+The person asks: "How do other meditation apps onboard new users?"
+
+```text
+1. Frame it: what starts the flow, how many steps, and what ends it?
+2. find_ui_references("meditation app onboarding")
+3. get_journey on 3 to 5 results; note the start, each step's purpose and the end.
+4. Report the shared pattern, where the flows differ and one recommendation.
+```
+
+For a starting design system, call `find_ui_materials("wellness light warm")`, compare the named color roles, type and components, then say which one fits the product and why.
+
+## Limitations
+
+- Needs the UXKIN MCP tools connected. Without them the skill answers from the project and general principles, and says so.
+- Real references depend on the UXKIN account; a plan-limited search returns no examples and the skill carries on without them.
+- Covers iOS app screens, user journeys and website design systems. Other platforms may have no references.
+- References inform decisions; they are not templates and never override the product's own requirements, accessibility or platform conventions.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-skills-collection",
-  "version": "4.1.11",
+  "version": "4.1.12",
   "description": "OpenCode CLI plugin that automatically downloads and keeps skills up to date.",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

package/skills_index.json

@@ -18916,6 +18916,36 @@
     "license": "MIT",
     "license_source": "https://github.com/zhaoxuya520/reverse-skill/blob/main/LICENSE"
   },
+  {
+    "id": "datacircle",
+    "path": "skills/datacircle",
+    "category": "data",
+    "name": "datacircle",
+    "description": "Look up LinkedIn profiles by URL through Datacircle (Up2Data or HarvestAPI, no markup), over its hosted MCP server or REST API, with the user's yes before each paid call.",
+    "risk": "critical",
+    "source": "self",
+    "date_added": "2026-10-10",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    },
+    "source_type": "self",
+    "tags": [
+      "b2b-data",
+      "linkedin",
+      "enrichment",
+      "rest-api",
+      "mcp"
+    ]
+  },
   {
     "id": "datadog",
     "path": "skills/datadog",
@@ -49937,6 +49967,40 @@
     "license": "MIT",
     "license_source": "https://github.com/amElnagdy/delegate-skills/blob/master/LICENSE"
   },
+  {
+    "id": "qrx",
+    "path": "skills/qrx",
+    "category": "design",
+    "name": "qrx",
+    "description": "Make branded, print-ready art QR codes that always scan with QRX (qrx.codes). Use when a link needs a QR code that looks like artwork or matches a brand for print, packaging, signs, slides or event badges, and to list or re-point QRX codes. Not for plain QR codes the agent makes locally.",
+    "risk": "critical",
+    "source": "https://github.com/qrxcodes/qrx-mcp/tree/main/skills/qrx",
+    "date_added": "2026-10-10",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    },
+    "source_type": "official",
+    "source_repo": "qrxcodes/qrx-mcp",
+    "license": "MIT",
+    "license_source": "https://github.com/qrxcodes/qrx-mcp/blob/main/LICENSE",
+    "tags": [
+      "qr-code",
+      "design",
+      "branding",
+      "mcp",
+      "rest-api",
+      "print"
+    ]
+  },
   {
     "id": "quality-nonconformance",
     "path": "skills/quality-nonconformance",
@@ -51829,6 +51893,32 @@
       "reasons": []
     }
   },
+  {
+    "id": "reverse-engineer-anything",
+    "path": "skills/reverse-engineer-anything",
+    "category": "uncategorized",
+    "name": "reverse-engineer-anything",
+    "description": "Use REA to investigate shipped apps, binaries, packages, and runtimes; trace features with evidence, compare versions, or guide reconstruction. Skip ordinary source-code analysis.",
+    "risk": "safe",
+    "source": "https://github.com/morluto/rea/tree/main/skill-src/reverse-engineer-anything",
+    "date_added": "2026-10-10",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    },
+    "source_type": "community",
+    "source_repo": "morluto/rea",
+    "license": "MIT",
+    "license_source": "https://github.com/morluto/rea/blob/main/LICENSE"
+  },
   {
     "id": "reverse-engineering",
     "path": "skills/reverse-engineering",
@@ -63830,6 +63920,40 @@
       "reasons": []
     }
   },
+  {
+    "id": "uxkin-research",
+    "path": "skills/uxkin-research",
+    "category": "frontend",
+    "name": "uxkin-research",
+    "description": "Research how real products handle a screen, flow or visual style before designing it: search UXKIN's real iOS screens, user journeys and website design systems, compare several and report what they share.",
+    "risk": "safe",
+    "source": "https://github.com/uxkin/agent/tree/main/skills/uxkin-research",
+    "date_added": "2026-10-09",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    },
+    "source_type": "official",
+    "source_repo": "uxkin/agent",
+    "license": "MIT",
+    "license_source": "https://github.com/uxkin/agent/blob/main/LICENSE",
+    "tags": [
+      "ui",
+      "ux",
+      "design",
+      "research",
+      "mcp",
+      "design-system"
+    ]
+  },
   {
     "id": "uxui-principles",
     "path": "skills/uxui-principles",