New skills routing#366
Open
itayhewix wants to merge 20 commits into
Open
Conversation
Contributor
❌ EvalForge YAML Gate: Missing CoverageThese changed docs have no covering YAML scenario for their area (scenarios for other areas do not count):
|
Contributor
|
Relocate the 17 per-domain skill-audit.md files (internal TPA-public and redundancy assessments) into the wix-skills-routing-expert skill repo; they must not ship publicly. Drop the audit reference from ecom-load-context.md and rewrite the (still-public) ecommerce skill-graph for the new routing tree. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
…-graph Coupons create/query use the stores/ service prefix (POST stores/v2/coupons), not /v2/coupons — verified against dev.wix.com. Redraw the ecommerce skill-graph with one group per L3 (Tax, Pricing), arrows landing on the group and files stacked vertically under the default dispatcher. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The README index embeds only title + description (not bodies), so a separate category-doc that just links to -default was a dead ReadFullDocsArticle hop. Fold the dispatch block into the README-surfaced ecom-tax.md / ecom-pricing.md and drop both -default files. Repoint the run-a-sale routing note, SKILL.md catalog, and skill-graph. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Catches the mirror up to the new ecommerce routing tree (category-doc + dispatcher merge, removed legacy flat files). Regenerated via npm run sync:plugin; --check now passes. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This reverts commit 8d61f6d.
…ut MCP-callable The run-a-sale orchestrator and tracking-api use manage.wix.com endpoints with no public docs page. They ARE callable via CallWixSiteAPI in the authenticated editor context, so the recipes carry the full request/response spec inline and must not be treated as unavailable. Also drop a stale `layer:` frontmatter key. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
… tree Create the merged ecom-shipping.md category entry + shipping/ folder (renamed ecom-shipping-*), repoint all cross-links (Pricing goal-increase-aov, checkout abandonment goal), and register under the shipping/ paths. Slim every shipping file's frontmatter to name+description. Reduce the cluster 10 -> 7: inline the two guardrails (rate-sanity into free-shipping/optimize-rates, health+intl filter into fix-coverage) and dissolve apply-recommendations per 7.5 (its CRUD is all in the API reference; preserved the singular deliveryRegionId gotcha there). The Shipping Options/Delivery Profiles APIs have no public docs, so ecom-shipping-api.md stays as the inline reference. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Create the merged ecom-checkout.md category entry + checkout/ folder (the 2 existing delivery-step recipes renamed ecom-checkout-*), slim their frontmatter, and repoint the run-a-sale ABANDONED_CART link. Dispatch covers the sheet's checkout intents honestly: 2 recipes, Dashboard routes for the config intents with no TPA-public API (guest checkout, min order, custom fields, upsell), a 7.5 API-doc entry for checkout policies, and flagged gaps (cart-recovery email, agentic/UCP readiness, store-health). Completes all four ecommerce L2 categories. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Author ecom-checkout-recover-email: the Dashboard abandoned-cart automation (timing, content, eligibility, recovery-rate benchmark) plus an agent API path using the TPA-public Abandoned Checkout API (query + redirect-to-checkout for the recovery link). Triggered Emails is PRIVATE/ALPHA so programmatic send stays Dashboard-driven. Wire into the checkout dispatch and make the view-abandoned entry concrete (POST /ecom/v1/abandoned-checkout/query). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Fold discount-conflicts + margin-protection into create-discount-rule (full set) and create-coupon (coupon subset) — the skills they guard — deduping the overlapping %-sanity/margin checks. Delete both guardrail files; repoint the 4 flows + 2 goals to the Create Discount Rule "Guardrails" section (slim their frontmatter, replace inline guardrail steps with pointers). pricing-promotions 15 -> 13 files; guardrails now enforced once at creation, not per-caller. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
…nt tags Add the skills that complete the four ecom L2 categories' sheet-intent coverage: - Checkout: agentic-readiness (catalog data-quality audit + public test-checkout; UCP enablement is Dashboard) and store-health monitor. - Shipping & fulfillment: fulfill-orders (Fulfillments API — mark fulfilled, tracking, partial, bulk) + §7.5 dispatch for find-unshipped / order invoice. - Pricing: pricing-health periodic sweep + competitive-pricing advisory entry. Also strip a stray trailing </content> line accidentally written into the four category entries and several recipe files. Wire all into dispatch, yaml, SKILL.md, and skill-graph. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
PR #366 added the Orders category (entry + cancel-order, registered in documentation.yaml + evals + SKILL.md catalog) but omitted it from skill-graph and the eCommerce routing-note line. Add the Orders subgraph, README arrow, reachability rows, and include Orders in both summaries. Verified the Orders APIs are TPA-public (search / get / cancel). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
…ent) Retitle the 6 tax skills to "Tax: <intent>" so the flat published slug becomes category-first (tax-configure-avalara, tax-switch-calculator, …). Titles drive the dev.wix.com slug; filenames stay ecom-tax-*. Pushing titles first to read the actual portal-assigned slugs before repointing dispatch links. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
…t slugs Now that the retitled tax pages publish at tax-configure-avalara, tax-configure-wix-manual, tax-switch-calculator, tax-audit-setup, tax-calculation-wrong, tax-configure-eu-vat (verified via the PR-aware portal index), point ecom-tax.md's dispatch links at those slugs. Filenames stay ecom-tax-*. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
…shed slugs The published doc slug = slugified title, not the file basename — so every internal link using /skills/ecom-<...> was 404ing. Repoint all 31 ecommerce skill files to the real portal slugs (built from the live PR-aware index): tax-*, shipping-set-up-*, pricing-create-*, checkout-*, abandoned-carts-*, fulfillment-*, orders-*, etc. Filenames unchanged. Eval ymls left as-is (the evalforge-yaml-gate computes expected URLs from the basename — separate issue). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
…gory-first) Across 20 ecom skill files (tax, pricing, shipping, checkout, skill-graph), update frontmatter `name:` to match the registered `title:` in yaml/wix-manage/ecommerce/documentation.yaml. The yaml titles were moved to category-first form in earlier commits on this branch (f6ed716, b48785e) so slugs would be deterministic and category-grouped; without aligning the md `name:` the same skill rendered under two different strings depending on where the agent saw it (README index vs. ReadFullDocsArticle body). All 47 ecom skill yaml titles now match their md `name:` 1:1. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.