Repository navigation
Find a pasted Mobbin screen link without saving it first - #1
Merged
Merged
Conversation
mobbin_link.py reads the screen's public page for the app, its tags and its link preview, and prints a search query. The skill searches with it, goes deeper with exclude_screen_ids, and only then falls back to saved screens or asks the user.
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
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 changes for the user
Pasting a Mobbin screen link now just works. Before, the skill could only find the screen if the user had saved it to their Mobbin account first, because the Mobbin MCP has no lookup by ID. Now the agent finds it on its own and says "Found it: ZARA, product detail" before building.
How
scripts/mobbin_link.pyreads the screen's public mobbin.com page (what a link preview shows): app, platform, category, the screen's patterns and UI elements when Mobbin has tagged them, and the preview card, saved so the agent can see the screen. It prints a search query such asZARA product detail screen.SKILL.md: the one-screen step searches with that query (adding a few words from the card when the screen is untagged), looks for the exact ID, and searches deeper withexclude_screen_ids(up to 4 searches). Then it falls back to the user's saved screens, and only after that asks the user.Safeguards
image_url. The page and its card are used to recognise the screen, never as a source.Testing
tests/test_mobbin_link.py(link shapes, tagged and untagged screens, unreadable pages, the card never leaving Mobbin, collection links making no request). 84 pass, ruff clean.--plugin-dir: a pasted link found the screen without it being saved.