SkillHub

uxc-skill-creator

v1.0.0

Create wrapper skills that call remote tools through UXC. Use when defining a new provider skill and you need reusable templates, validation rules, and anti-pattern guidance based on proven UXC skill practices.

Sourced from ClawHub, Authored by jolestar

Installation

Please help me install the skill `uxc-skill-creator` from SkillHub official store. npx skills add jolestar/uxc-skill-creator

UXC Skill Creator

Use this skill to design and standardize provider wrapper skills built on top of uxc.

Prerequisites

  • uxc skill is available as the base execution contract.
  • Target wrapper skill scope is clear (provider endpoint, core operations, auth model, write risk).

Output Contract

A wrapper skill created with this skill should include:

  • SKILL.md
  • agents/openai.yaml
  • references/usage-patterns.md
  • scripts/validate.sh

Optional files are allowed only when they add real reusable value.

Core Workflow

  1. Start from user-provided host input:
  2. record the raw host the user gives
  3. normalize endpoint candidates (scheme/no-scheme, path variants)
  4. Discover protocol and valid path before drafting skill text:
  5. search official docs/repo to confirm endpoint shape and auth model
  6. probe candidates with uxc <endpoint> -h
  7. confirm one working endpoint + protocol as the wrapper target
  8. Detect authentication requirement explicitly:
  9. run host help or a minimal read call and inspect envelope/error code
  10. if auth-protected, record required model (api key or oauth) and scopes
  11. verify local mapping path with uxc auth binding match <endpoint> when OAuth/binding is used
  12. Fix the wrapper interface:
  13. provider endpoint (<host>)
  14. fixed link command name (<provider>-<protocol>-cli)
  15. auth mode (none, api key, oauth)
  16. Write SKILL.md as a thin execution policy:
  17. link-first command flow
  18. help-first discovery flow
  19. JSON envelope parsing and safe-write guardrails
  20. Add provider-specific references/usage-patterns.md:
  21. minimal read and write examples
  22. key=value and bare JSON positional input examples
  23. Add scripts/validate.sh with strict checks:
  24. required files
  25. frontmatter fields
  26. command style constraints
  27. banned legacy patterns
  28. Add agents/openai.yaml for skill UI metadata.
  29. Run validation and iterate until clean.

Hard Rules

  • Default to link-first (command -v <link_name> then uxc link <link_name> <host>).
  • Default to help-first (<link_name> -h, <link_name> <operation> -h).
  • Use protocol-aware link naming:
  • format: <provider>-<protocol>-cli
  • examples: notion-mcp-cli, github-openapi-cli
  • Prefer key=value; allow bare JSON positional payload.
  • Keep JSON output as automation path; do not rely on --text.
  • Do not use legacy default examples (list/describe/call/removed flags).
  • Do not use dynamic link renaming at runtime.
  • Do not assume protocol/path/auth from host string alone; verify by search + probe.

References

  • Step-by-step implementation flow:
  • references/workflow.md
  • Copy-ready templates:
  • references/templates.md
  • Validation checklist and banned patterns:
  • references/validation-rules.md
  • Observed pitfalls and better defaults:
  • references/anti-patterns.md

See Also

  • Base execution and protocol/auth guidance:
  • skills/uxc/SKILL.md