Skip to content

fix(router): drop tooling reference from integrate intent#156

Open
sanchitmehtagit wants to merge 2 commits into
mainfrom
flywheel/router-drop-tooling-from-integrate
Open

fix(router): drop tooling reference from integrate intent#156
sanchitmehtagit wants to merge 2 commits into
mainfrom
flywheel/router-drop-tooling-from-integrate

Conversation

@sanchitmehtagit

@sanchitmehtagit sanchitmehtagit commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Summary

The integrate intent unconditionally co-loaded tooling-{tooling}.md (tooling-cli by default) alongside the framework reference on every quickstart-style integration —

 ### integrate
 Read: references/framework-{framework}.md
-Read: references/tooling-{tooling}.md
 Follow the integration workflow in framework-{framework}.md.
-Use tooling-{tooling}.md for all Auth0 tenant configuration steps.

Why

Quickstart integrations don't need the CLI tooling reference — the framework reference already carries the full integration workflow and cli config both. Loading tooling-cli.md anyway just adds context noise, and lower-capability models hallucinate from that extra surface (e.g. inventing Management API /api/v2/users/... calls ). This issue was observed with Haiku 4.5 and This change fixed that.

tooling-{tooling}.md stays routable from the feature:* and migrate intents that genuinely provision tenant config, so nothing that needs it loses access. Router reachability check passes (check_router_reachability.py: all references routable).

This has following downsides:

  • Context bloat: Extra content hurts performance, especially on smaller models like Claude Haiku, which are more prone to hallucinations.
  • More context compaction: Loading unnecessary content increases compaction, making responses less deterministic.
  • Higher token usage: End customers end up consuming more tokens than necessary.

Prior Skill consolidation this was not the case

Relationship to #152

#152 takes the conditional approach — gate the tooling load on a tenant-config need. This PR is the simpler cut for the integrate path specifically: quickstart integrations don't provision tenant config as part of the task, so the reference is just dropped rather than gated. If #152 lands first, this becomes a no-op simplification of the same block; happy to reconcile.

Validation

  • check_router_reachability.py — PASS (all references routable, no broken routes, no second-hop references)
  • Change is 2 deletions to the integrate block only; no other intents touched

Summary by CodeRabbit

  • Documentation
    • Updated Auth0 integration guidance to follow the framework-specific workflow.
    • Simplified instructions for tenant configuration during integration.

The `integrate` intent unconditionally co-loaded `tooling-{tooling}.md`
(tooling-cli by default) alongside the framework reference on every
quickstart-style integration — even tasks that only add login and never
touch tenant configuration.

Quickstart integrations don't need the CLI tooling reference: the framework
reference already carries the full integration workflow. Loading tooling-cli
anyway adds context noise that lower-capability models hallucinate from
(e.g. inventing Management API calls that no reference actually teaches).

Remove the unconditional tooling load from `integrate` so the intent reads
only the framework reference. tooling-{tooling}.md remains routable from the
feature/migrate intents that genuinely provision tenant config.
@coderabbitai

coderabbitai Bot commented Jul 22, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

The Auth0 integrate instructions now direct agents to follow framework-{framework}.md and no longer explicitly require loading or using tooling-{tooling}.md for tenant configuration.

Changes

Auth0 integration guidance

Layer / File(s) Summary
Update integrate workflow instructions
plugins/auth0/skills/auth0/SKILL.md
The integrate workflow now references the framework-specific workflow and removes explicit tooling reference loading and usage instructions.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main change: removing the tooling reference from the integrate intent.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch flywheel/router-drop-tooling-from-integrate

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

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

@github-actions

Copy link
Copy Markdown

✅ skillsaw — All checks passed

Full report
skillsaw 0.16.0
Linting: /home/runner/work/agent-skills/agent-skills


Scanned:
  Repo type: agentskills, coderabbit, marketplace
  Plugins:   1
  Skills:    1
  Rules run: 51
  Took:      2.2s

Summary:
  Errors:   0
  Warnings: 0
  Grade:    A (1.36 weighted violations per 10k tokens)
  316 info-level violation(s) count toward the grade — run with -v to see them

✓ All checks passed!

skillsaw 0.16.0 · config · custom rules · run

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant