How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

woocommerce-dev-cycle - Skill

Name: woocommerce-dev-cycle
Author: woocommerce

Imported from woocommerce/woocommerce (.ai/skills/woocommerce-dev-cycle/SKILL.md). Install upstream with npx skills add woocommerce/woocommerce --skill woocommerce-dev-cycle. Copyright stays with the author.

WooCommerce Development Cycle

This skill provides guidance for the WooCommerce development workflow, including running tests, code quality checks, and troubleshooting.

Instructions

Follow these guidelines for WooCommerce development workflow:

Running tests: See running-tests.md for PHP and JavaScript test commands, test environment setup, and troubleshooting
Code quality: See code-quality.md for linting, code style fixes, and the lockfile procedure for dependency changes
PHP linting patterns: See php-linting-patterns.md for common PHP linting issues and fixes
JS/TS i18n patterns: See js-i18n-patterns.md for translatable string patterns and placeholder usage
Markdown linting: See markdown-linting.md for markdown file linting and formatting

Development Workflow

The standard development workflow:

Make code changes
Run relevant tests: pnpm run test:php:env -- --filter YourTestClass
Run linting: pnpm --filter=@woocommerce/plugin-woocommerce lint:changes:branch (PHP and JS, the command CI's Lint job runs; git add new files first, since untracked files are skipped; for a PR that does not target trunk, append its fetched base, such as origin/release/X.Y)
Fix any issues: PHP with pnpm --filter=@woocommerce/plugin-woocommerce lint:php:fix; there is no branch fixer for JS, so fix JS by hand (see code-quality.md)
Commit changes only after tests pass

Key Principles

Always run tests after making changes to verify functionality
Use specific test filters to run relevant tests during development
Fix linting errors solely for code in your current branch
Test failures provide detailed output showing expected vs actual values
The test environment handles WordPress/WooCommerce setup automatically

Install woocommerce-dev-cycle and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "woocommerce-woocommerce-woocommerce-dev-cycle", "kind": "skill", "name": "woocommerce-dev-cycle", "description": "Run tests, linting, and quality checks for WooCommerce development. Use when running tests, fixing code style, or following the development workflow.", "publisher": "woocommerce", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Run tests, linting, and quality checks for WooCommerce development. Use when running tests, fixing code style, or following the development workflow." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/woocommerce/woocommerce", "path": ".ai/skills/woocommerce-dev-cycle/SKILL.md", "ref": "HEAD", "url": "https://github.com/woocommerce/woocommerce/blob/HEAD/.ai/skills/woocommerce-dev-cycle/SKILL.md", "key": "woocommerce/woocommerce/.ai/skills/woocommerce-dev-cycle/SKILL.md" } }, "instructions": "# WooCommerce Development Cycle\n\nThis skill provides guidance for the WooCommerce development workflow, including running tests, code quality checks, and troubleshooting.\n\n## Instructions\n\nFollow these guidelines for WooCommerce development workflow:\n\n1. **Running tests**: See [running-tests.md](running-tests.md) for PHP and JavaScript test commands, test environment setup, and troubleshooting\n2. **Code quality**: See [code-quality.md](code-quality.md) for linting, code style fixes, and the lockfile procedure for dependency changes\n3. **PHP linting patterns**: See [php-linting-patterns.md](php-linting-patterns.md) for common PHP linting issues and fixes\n4. **JS/TS i18n patterns**: See [js-i18n-patterns.md](js-i18n-patterns.md) for translatable string patterns and placeholder usage\n5. **Markdown linting**: See [markdown-linting.md](markdown-linting.md) for markdown file linting and formatting\n\n## Development Workflow\n\nThe standard development workflow:\n\n1. Make code changes\n2. Run relevant tests: `pnpm run test:php:env -- --filter YourTestClass`\n3. Run linting: `pnpm --filter=@woocommerce/plugin-woocommerce lint:changes:branch` (PHP and JS, the command CI's Lint job runs; `git add` new files first, since untracked files are skipped; for a PR that does not target trunk, append its fetched base, such as `origin/release/X.Y`)\n4. Fix any issues: PHP with `pnpm --filter=@woocommerce/plugin-woocommerce lint:php:fix`; there is no branch fixer for JS, so fix JS by hand (see [code-quality.md](code-quality.md))\n5. Commit changes only after tests pass\n\n## Key Principles\n\n- Always run tests after making changes to verify functionality\n- Use specific test filters to run relevant tests during development\n- Fix linting errors solely for code in your current branch\n- Test failures provide detailed output showing expected vs actual values\n- The test environment handles WordPress/WooCommerce setup automatically", "cost": { "context_tokens": 481 } }

woocommerce-dev-cycle

About

WooCommerce Development Cycle

Instructions

Development Workflow

Key Principles

Install woocommerce-dev-cycle and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews