fix(SOL-422): stackone-unified-connectors - update stale StackOne docs links and description

[faisalreza-stackone]

Summary

StackOne moved the connector-building docs, which broke the docs links in the stackone-unified-connectors skill. /guides/connector-engine returns 404, and /guides/connector-engine/cli-reference only works through a redirect. The description also told users to use this skill alongside unified-hris-schema and unified-crm-schema, which are not skills anyone can install. They are examples of schema skills the user creates.

Changes

• Links: the CLI documentation link and the Key URLs table point to the Connector Building pages. The table also gains Defined Output Schemas and the Connector YAML Reference.
• Durable links: appending .md returns a page as markdown. If a URL 404s, the agent searches llms.txt by topic for the current page.
• Description: now says "domain-specific schema skills that you create" instead of naming skills that do not exist. The body already described them as skills to create.
• Field mapping uses action-level fieldConfigs: the skill told agents to put fields inline in the map_fields step and avoid fieldConfigs, claiming it caused schema inference build failures. The Defined Output Schemas checklist uses fieldConfigs, and so do nearly all unified actions in the most recently built connectors (Jenkins, Loom, Statuspage, Keeper and others). The skill and field-mapping-patterns.md now declare fields in fieldConfigs, with map_fields and typecast taking only a dataSource. The schema inference troubleshooting entry is removed.
• Expression context: the skill said fieldConfigs expressions need a step ID prefix ($.get_employees.email). They are evaluated against each record, so they reference fields directly ($.email), as real connectors do.
• Case-insensitive enum matching: ($.status || "").toLowerCase() returns undefined because the expression language has no string methods. Replaced with the documented lower() function in the reference and the troubleshooting section.
• Skill metadata.version bumped from 2.1 to 2.2. The plugin version is left to release-please.

scope-patterns.md and pagination-patterns.md are unchanged. One rule is still being checked with the team: preferring request over paginated_request when the action takes inputs. Many connectors pass $.inputs.* into paginated_request.

Files

File	Change
plugins/integrations/stackone-unified-connectors/skills/stackone-unified-connectors/SKILL.md	Links, fallback, description, fieldConfigs pattern, expression context, version
plugins/integrations/stackone-unified-connectors/skills/stackone-unified-connectors/references/field-mapping-patterns.md	fieldConfigs pattern, lower() for case-insensitive matching, checklist

Test plan

• Every docs.stackone.com URL in the skill returns 200 directly (no redirects) and appears in llms.txt
• The description only references skills that a user can install or create
• Every expression in field-mapping-patterns.md evaluates as intended with @stackone/expressions
• claude plugin validate . passes
• The cursor-pagination-next eval case fails on Claude Sonnet: the skill steers the agent to request instead of the paginated_request docs. Expected to pass once the paginated_request rule above is resolved

Closes SOL-422.

🤖 Generated with Claude Code

---

Summary by cubic

Updates the stackone-unified-connectors skill so its docs links, description, and field mapping guidance match current StackOne behavior.

• Connector Engine links now point to the Connector Building pages; the Key URLs table gains Defined Output Schemas and Connector YAML Reference entries.
• The .md fallback only applies to docs.stackone.com URLs that don't already end in .md; llms.txt is fetched as is.
• If a docs URL 404s or a page doesn't answer the question, the skill tells agents to search llms.txt for the current page and to contact StackOne support rather than invent an answer.
• The description now references "domain-specific schema skills that you create" instead of nonexistent skills.
• map_fields and typecast steps now take only a dataSource; fieldConfigs expressions are relative to each record with no step prefix.
• Enum matching uses lower() instead of unsupported .toLowerCase(); the schema inference troubleshooting entry is removed.
• Skill metadata.version bumped from 2.1 to 2.2; plugin version is left to release-please.

Migration: The request vs. paginated_request rule is unchanged pending team review; the cursor-pagination-next eval case still expects the paginated_request resolution.

^{Written for commit f40e6db. Summary will update on new commits.}

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[cubic-dev-ai]

All reported issues were addressed across 1 file

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

All reported issues were addressed across 2 files (changes from recent commits).

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

All reported issues were addressed across 1 file (changes from recent commits).

<sub>Tip: Review your code locally with the cubic CLI to iterate faster.

Re-trigger cubic</sub>

[cubic-dev-ai]

0 issues found across 1 file (changes from recent commits).

<sub>Requires human review: Auto-approval blocked by 1 unresolved issue from previous reviews.

Re-trigger cubic</sub>

[cubic-dev-ai]

No issues found across 2 files

<sub>Auto-approved: Bounded skill-documentation fix: corrects stale StackOne docs links, rewrites field-mapping/enum guidance to current runtime behavior, and bumps skill version. Changes are confined to markdown in one plugin and covered by validate/link checks.

Re-trigger cubic</sub>