Skip to content

Add a public-documentation fallback for uncovered questions - #15

Merged
amitl-levi merged 1 commit into
mainfrom
web-fallback
Aug 30, 2026
Merged

amitl-levi merged 1 commit into
mainfrom
web-fallback

Conversation

@amitl-levi

Copy link
Copy Markdown
Collaborator

Part 2 of the split of former PR #9 (replaces #12, which GitHub closed when its temporary base branch was deleted after #8 merged — same content, now based directly on main).

The web-fallback skill: answers in-scope questions the knowledge base doesn't cover from Taboola's public advertiser help documentation (realize.com/help/ only), flagged as found online, always yielding to the plugin's own guidance on conflict.

Merge order: this → #13 (conversion rules) → #14 (marketplace) → #11 (pixel diagnosis). After merging, delete the web-fallback branch via the button on this PR — that's what re-points #13 at main automatically.

🤖 Generated with Claude Code

Comment thread INSTALL.md Outdated
The knowledge base is 12 topic files; advertisers ask hundreds of
reasonable "how do I..." questions that land just outside them. Those
got a thin answer from model priors or a shrug. Closes the P0
"Help Center connection" gap from the 2026-07-06 capability audit.

The new web-fallback skill searches Taboola's public advertiser help
documentation and answers with a "here's what I found online" framing.
It is a fallback, never a supplement: it fires only on a real miss,
judged per question rather than per topic, and when a web source
contradicts a knowledge file the knowledge file wins silently.

Scoped to realize.com/help/ only. A domain allowlist alone is not
enough - /marketing-hub/ is promotional copy on the same host and
supplied 3 of 10 results in one live test search and 7 of 10 in
another, carrying the guaranteed-outcome framing brand-check bans.
Search results are treated as a link index, never as an answer: the
tool synthesizes prose across every hit before the URL list is
visible, and a correctly domain-restricted query returned a summary
that recommended a competitor's browser extension.

The absolute ban on a "Sources:" footer is rescoped to plugin
internals, with an explicit exception for a public URL the user asked
for. Left absolute, it either blocked the citation-on-request
behaviour or left the model resolving a contradiction at runtime,
which is how a capability quietly stops firing.

Taboola's developer documentation is deliberately excluded: its API
reference covers the API the MCP already wraps and the plugin does not
emit endpoint paths or client code, half its sections are
publisher-side, and its one advertiser-relevant area is better covered
by the help center for a non-developer reader.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@amitl-levi

Copy link
Copy Markdown
Collaborator Author

Fixed — promoted to ## so it's no longer nested under the Optional section (the sibling "pixel-diagnosis page fetch" section in #11 got the same fix). Ready for re-review.

@yanush88
yanush88 self-requested a review August 30, 2026 11:03
@amitl-levi
amitl-levi merged commit ea68bdd into main Aug 30, 2026
1 check passed
@amitl-levi
amitl-levi deleted the web-fallback branch August 30, 2026 15:15
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.

2 participants