fix(ci): use PAT for sync-skills workflow so downstream workflows fire

[mvanhorn]

Closes #355

What

Switches the sync-skills workflow to use a PAT for checkout and the peter-evans/create-pull-request@v6 step, falling back to GITHUB_TOKEN when the secret is not set.

token: ${{ secrets.SYNC_SKILLS_PAT || secrets.GITHUB_TOKEN }}

Why

Per GitHub's docs, events produced by GITHUB_TOKEN pushes / PR creations do NOT trigger new workflow runs (exception: workflow_dispatch and repository_dispatch). Any workflow configured to run on push or pull_request is silently skipped when the sync bot creates the PR.

The issue links the GitHub doc directly.

Activation

To make the fallback route to the real PAT path, create a repo secret:

• Name: SYNC_SKILLS_PAT
• Type: fine-grained PAT scoped to this repository
• Permissions: contents: write, pull-requests: write
• Expiration: whatever your org policy prefers

Until the secret is created, the workflow still uses GITHUB_TOKEN and keeps working exactly as it does today - this PR does not regress anything.

Scope

One-line logic change in .github/workflows/sync-skills.yml, applied to both the checkout and the create-pull-request steps. No other workflow files touched. No secret added by the PR (that's a maintainer action).

Verified

• YAML parses cleanly (ruby -ryaml -e "YAML.load_file(...)").
• Fallback syntax is the same pattern used across peter-evans/create-pull-request documentation.

This contribution was developed with AI assistance (Claude Code).

[matv-stripe]

ty!