Skip to content

Adonis0123/adonis-skills / skills/uxc-facade

uxc-facade

Flagged

This skill should be used when the user invokes /uxc-facade or asks to package, harden, or reuse an MCP, OpenAPI, GraphQL, gRPC, or JSON-RPC interface through UXC; create or maintain a stable uxc link; reuse a daemon-backed stdio child; pin UXC for automation; or design a deterministic JSON CLI facade for another skill. Apply the facade contract without replacing service-specific identity checks. Do not use for ordinary one-off API calls, and hand Chrome DevTools-specific work to chrome-dev-mcp.

FileKindSize
SKILL.mdskill md11.0 KB
evals/evals.jsonconfig6.0 KB
evals/trigger-eval.jsonconfig2.8 KB
references/facade-contract.mdmarkdown2.3 KB
references/ownership-gates.mdmarkdown1.9 KB

evals/evals.json

View on GitHub
{
  "skill_name": "uxc-facade",
  "evals": [
    {
      "id": 1,
      "name": "explicit-method-contract",
      "prompt": "/uxc-facade",
      "expected_output": "Returns the reusable UXC Facade Contract without installing UXC, creating links, importing configuration, or mutating files.",
      "files": [],
      "expectations": [
        "Treats the explicit invocation as a request for the generic method",
        "Returns the contract fields needed to scope a target",
        "Does not mutate state without a concrete target"
      ]
    },
    {
      "id": 2,
      "name": "mcp-stdio-packaging",
      "prompt": "用 UXC 把一个已有的 MCP stdio wrapper 包成可复用 CLI。保留原生宿主注册,子进程很贵,需要证明 daemon 复用,并且 readiness 不能泄露工具结果。",
      "expected_output": "Defines native and service ownership, a fixed managed link, pinned provenance, finite idle retention, sanitized two-call reuse proof, and separate task and native-host acceptance.",
      "files": [],
      "expectations": [
        "Keeps native host registration authoritative",
        "Uses a fixed owned link and pinned official UXC provenance",
        "Names the binary owner as the sole installer and updater while the service skill owns link and readiness helpers",
        "Defines a two-call daemon reuse proof using sanitized metadata rather than timing, and keeps reuse UNVERIFIED until it runs",
        "Keeps runtime readiness statuses UNVERIFIED when no ownership gates or calls were executed",
        "Separates UXC transport from task acceptance and native-host acceptance"
      ]
    },
    {
      "id": 3,
      "name": "openapi-link-packaging",
      "prompt": "我们会反复调用一个有 schema 的 OpenAPI 服务。请用 UXC 设计固定 JSON CLI,但这个服务没有需要常驻复用的子进程。",
      "expected_output": "Uses UXC discovery and a fixed managed link, keeps auth external, omits daemon exclusivity without shared mutable state, and defines a safe readiness operation.",
      "files": [],
      "expectations": [
        "Inspects the schema and operation before linking",
        "Does not add daemon exclusivity without measured shared state",
        "Keeps credentials outside skill content and output"
      ]
    },
    {
      "id": 4,
      "name": "one-off-api-near-miss",
      "prompt": "用 UXC 调一次公开 API,拿到结果就结束,不需要固定命令、daemon 或自动化维护。",
      "expected_output": "Uses the ordinary UXC discovery and execution workflow directly instead of creating a facade contract, installer, or persistent link.",
      "files": [],
      "expectations": [
        "Recognizes that a reusable facade is unnecessary",
        "Does not create a persistent link or packaging layer"
      ]
    },
    {
      "id": 5,
      "name": "chrome-devtools-handoff",
      "prompt": "用 UXC 包装 Chrome DevTools MCP,并确认连的是正确 Chrome,最后真实调用 list_pages。",
      "expected_output": "Hands Chrome identity, recovery, shared list_pages acceptance, and explicit native compatibility policy to chrome-dev-mcp while applying the generic facade contract only to the UXC adapter layer.",
      "files": [],
      "expectations": [
        "Routes the task to chrome-dev-mcp",
        "Does not treat schema discovery alone as correct-Chrome proof",
        "Uses the shared list_pages call as default acceptance and native only as explicit compatibility"
      ]
    },
    {
      "id": 6,
      "name": "binary-pin-conflict",
      "prompt": "两个业务 skill 都想安装 UXC:一个 pin 0.17,另一个需要不同版本,而且它们现在会写同一个 uxc 路径。请按通用方法决定怎么包装;不要为了复用而新建共享 installer。",
      "expected_output": "Explains that a private install root isolates only the binary while the daemon, schema cache, and credentials under $HOME/.uxc are shared per user, so it names one binary owner and one pinned UXC version per user, requires uxc daemon status version_mismatch=false, fails closed on a foreign or mismatched binary, and keeps executable scripts in each owner skill.",
      "files": [],
      "expectations": [
        "Does not allow two owner skills to overwrite one shared binary",
        "States that two UXC versions on one user share one daemon and resolves to one pinned version with a named binary owner",
        "Fails closed on a foreign owner, digest mismatch, or version conflict",
        "Does not create a shared installer or shared runtime script dependency"
      ]
    },
    {
      "id": 7,
      "name": "multi-protocol-packaging",
      "prompt": "我们有 GraphQL、gRPC 和 JSON-RPC 接口需要统一给 agent 使用。请说明怎样用 UXC facade 复用同一方法,同时保留每个服务自己的 auth、readiness 和验收。",
      "expected_output": "Applies one discovery, ownership, link, and layered-evidence contract across supported protocols while leaving credentials, readiness operations, pins, and native acceptance with each owning skill.",
      "files": [],
      "expectations": [
        "Uses the same facade method without pretending the protocols are identical",
        "Keeps authentication and acceptance service-specific",
        "Does not introduce a shared service runtime"
      ]
    },
    {
      "id": 8,
      "name": "reuse-proof-by-metadata",
      "prompt": "我们的 uxc link 第二次 readiness 调用明显变快了,可以把 SESSION_REUSED 标成已证明吗?",
      "expected_output": "Keeps SESSION_REUSED as UNVERIFIED and names the metadata proof: run the readiness call twice, then check uxc daemon sessions for one reuse-eligible stdio session and uxc daemon status for an increased mcp_reuse_hits with unchanged mcp_stdio_sessions.",
      "files": [],
      "expectations": [
        "Rejects timing as reuse evidence",
        "Names uxc daemon sessions and mcp_reuse_hits as the proof",
        "Keeps SESSION_REUSED UNVERIFIED until that metadata is checked and names the next action"
      ]
    }
  ]
}
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall