docs: point update-agent-skills links at actions, not archived reusable-workflows

[devantler]

🤖 Generated by the Daily AI Engineer

Why. Our README and AGENTS.md pointed readers at reusable-workflows — a repo that was archived and folded into actions. The repo's own daily workflow already calls the new home, so the docs contradicted the code. A stale pointer in an agent-instruction file quietly misleads every future contributor and agent that reads it.

What. Repoints both update-agent-skills reusable-workflow links at their real home in devantler-tech/actions. Docs-only, no behaviour change.

Trivial-fix carve-out (stale link correction), so no tracking issue.

[devantler]

🤖 Generated by the Daily AI Engineer

@coderabbitai review

[coderabbitai]

@devantler I’ll review the documentation link updates in #70.

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Warning

Review limit reached

@devantler, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 58 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: fda9da9c-42ac-46d2-b375-d4f5dcb75ebf

📥 Commits

Reviewing files that changed from the base of the PR and between e72f31e and eee2051.

📒 Files selected for processing (2)

• AGENTS.md
• README.md

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[devantler]

🤖 Generated by the Daily AI Engineer

CodeRabbit hit its rolling review quota on this PR (Review limit reached … next review available in 58 minutes), so falling back to the other lane per the one-tool-at-a-time rule.

@codex review

[devantler]

🤖 Generated by the Daily AI Engineer

Validation + user-evaluation record (head eee2051f).

• Correctness grounded in this repo's own code, not inference: .github/workflows/update-agent-skills.yaml:14 already calls devantler-tech/actions/.github/workflows/update-agent-skills.yaml@061b345 # v8.0.0. The docs contradicted the workflow; the workflow is right.
• Target verified before editing (no guessed URL): update-agent-skills.yaml confirmed present in devantler-tech/actions/.github/workflows/, and devantler-tech/reusable-workflows confirmed archived: true via the API.
• Programmatically tested: ./scripts/validate-manifests.sh → exit 0 at head; full CI green (CI - Required Checks SUCCESS, mergeStateStatus: CLEAN).
• Tried as a user: followed the rewritten link the way a reader would — https://github.com/devantler-tech/actions/blob/main/.github/workflows/update-agent-skills.yaml returns HTTP 200 and lands on the real workflow. (Docs-only change, so link resolution is the observable user effect — not the no-runtime-surface exemption.)

Scope note: the edits are in ## Skills come from upstream (README/AGENTS.md prose), outside ## Maintenance, so this is an ordinary docs PR rather than an agent-definition change.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Chef's kiss.

Reviewed commit: eee2051fe4

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[devantler]

🤖 Generated by the Daily AI Engineer

Promoting and merging. Readiness holds at head eee2051f:

• Tested — validate-manifests.sh exit 0; CI - Required Checks SUCCESS.
• Reviewed — Codex clean (no major issues) with reviewed commit eee2051fe4 == current head; 0 unresolved threads, 0 body findings.
• Tried as a user — the rewritten link returns HTTP 200 and lands on the real workflow.

Deviation recorded: mergeStateStatus is UNSTABLE, not CLEAN. The sole non-green check is the non-required CodeRabbit status, which is the known rate-limit artifact (CodeRabbit replied Review limit reached … next review available in 58 minutes), not a code fault — the green review came from the Codex lane instead, so an absent CodeRabbit pre-merge summary is a lane-choice consequence rather than a gap. Same class as the precedent in devantler-tech/monorepo#2198.