Enable live Context7 fetching (snapshot becomes fallback)#7
Open
franco-zalamena-iterable wants to merge 1 commit into
Open
Enable live Context7 fetching (snapshot becomes fallback)#7franco-zalamena-iterable wants to merge 1 commit into
franco-zalamena-iterable wants to merge 1 commit into
Conversation
Iterable's curated library is published and verified on Context7 (/iterable/iterable-sdk-skill — 730 snippets, live). Flip the skill from "snapshot authoritative, don't fetch Context7" to "Context7-first, snapshot as offline fallback." All four coupled spots move together (a partial flip is the known failure mode): - .context7-library-id: replace TODO-PHASE-3 placeholder with the real ID, drop the placeholder status block. - SKILL.md "How to use this skill": Context7 is the authoritative source (read ID → query-docs one doc per slug); snapshot is the offline fallback. - SKILL.md decision-flow step 3 + "start here" pointer: match the new source priority. - README "How it works" + Limitations: fetches live from Context7, snapshot as fallback; remove the "not live yet" limitation. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
What
Turn on live Context7 doc fetching. The skill now treats Context7 as the authoritative documentation source, with the bundled snapshot as an offline fallback (previously it was snapshot-only, with Context7 explicitly disabled).
Why now
Iterable's curated library is published and verified on Context7:
/iterable/iterable-sdk-skill— 730 snippets, ~50k tokens, trust score 9.3, crawled. TheTODO-PHASE-3placeholder that gated this is resolved.Changes (all four coupled spots move together)
A partial flip is the known failure mode here, so everything that referenced the source priority moves in one commit:
iterable-android/.context7-library-id— replace theTODO-PHASE-3/...placeholder with the real ID/iterable/iterable-sdk-skill; drop the placeholder status block.SKILL.md→ "How to use this skill" — Context7 is now the authoritative source (read ID →query-docs, one doc per slug); the snapshot section becomes the offline fallback. The "do not fetch / not published yet" warning is removed.SKILL.md→ decision-flow step 3 + the "start here" pointer — updated to match the new source priority.README.md→ "How it works" + Limitations — now describes live Context7 fetching with the snapshot as fallback; the "Context7 fetch is not live yet" limitation is removed.Validation
pnpm check:allgreen: typecheck, polished schema (14),validate-plugins, snapshot verify (14 match).TODO-PHASE/ "not live" / "dormant" references remain in the skill or README.🤖 Generated with Claude Code