Repository navigation
Add a public-documentation fallback for uncovered questions - #12
Closed
amitl-levi wants to merge 1 commit into
Closed
amitl-levi wants to merge 1 commit into
amitl-levi wants to merge 1 commit into
Conversation
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>
This was referenced Aug 27, 2026
Closed
Closed
This was referenced Aug 27, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part 2 of the split of former PR #9, per review feedback there. One feature per PR; this one is the
web-fallbackskill: 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.Stack: based on
support-skill(PR #8) so the diff shows only this feature. Merge #8 first; this PR retargets automatically when the base branch is deleted on merge.🤖 Generated with Claude Code