" --from-file cards.tsv --dry-run --json ``` `--dry-run` exists on `deck create`, `card add` and `import`, and runs that command's own parser. Read `image_advice` in the result and fix what it names. 7. **Publish:** ```shell loopky deck create --title "<Title>" --tag <topic> --from-file cards.tsv --json ``` Add `--id <word> --if-not-exists` when a retry must not publish a second deck. 8. **Verify from what was stored, not what was sent:** `loopky deck show <deckId> --json` and `loopky card list <deckId> --json`. Results sit under `data`; a card's `front` is an object with `.text` and `.image`, not a string. Tell the user the deck is on their phone under the title. 9. **If the CLI or this skill got in the way, ask whether to report it**, once, at the end, as the last section describes. Nothing is gathered before a yes, and nothing is sent until the user approves the exact text. **Several commands in a row belong in `loopky batch`.** Each invocation pays ~2s of start-up and a session round trip; a batch pays once. One JSON line per operation: `{"argv": ["card", "add", "<deckId>", "--front", "…", "--back", "…"]}`, run with `loopky batch ops.ndjson --json`. Its output is one JSON line per operation, as each one runs, then a summary line last: read it line by line, since parsing it as one document fails. It is not transactional: on failure, fix the cause and re-run the same file — `card add`, `card edit --from-file` and `deck create --id --if-not-exists` skip what already landed. **A card in the wrong place moves with `loopky card mv <deckId> <cardId> --after <cardId>`**, or `--to <position>`, counting from 1 as `card list` prints them. Never delete and re-add a card to move it: the new card has a new id, and everyone studying the deck loses their progress on it. A move keeps it. Put several moves in one `loopky batch`: each `card mv` reads the whole deck before its one write, and only a batch pays for that read once. A card already in place writes nothing, so the file can be re-run. Keep `card mv` to a few cards. **Many cards out of place, reorder the whole deck from a file.** `loopky card list <deckId>` prints one card a line with its id first; put those lines in the order wanted and run `loopky card reorder <deckId> --from-file order.txt --dry-run`, then without `--dry-run`. Only the first column is read, and the file has to name every card exactly once, or nothing is written. Every card keeps its id, so nobody studying the deck loses progress. If it fails partway (exit 4, 5 or 12), run the same command again with the same file: that finishes it, and until then the deck still has every card but refuses card writes with exit 9. If the file is lost, the output of `card list` works as the file. **Already have an Anki deck?** `loopky import deck.apkg --dry-run --json` first — check which fields became front and back (`--front-field`/`--back-field` override it) and `images.bytes`, since an `.apkg` is the one import that uploads pictures against a 1 GB quota. Then `loopky import deck.apkg --title "<Title>"`. ## Exit codes Branch on the exit code (or `error.code` in the JSON) before reading the message. | Exit | Name | What to do | | --- | --- | --- | | 0 | ok | Carry on. | | 1 | internal | Report it as a bug; do not loop on it. | | 2 | usage | Fix the command line with `loopky <command> --help`. Never retry unchanged. | | 3 | not_signed_in | Run `loopky login` with the user. | | 4 | session_expired | Stop and ask the user to approve a new `loopky login`, then re-run what failed. Writes die after about an hour while reads still work. | | 5 | network | Retry as-is, a few times with a pause. | | 6 | not_found | Check the id with `loopky deck list --json`. | | 7 | storage_full | Terminal: the account is out of quota. Never retry; tell the user. | | 8 | environment_mismatch | The session belongs to the other network; re-run with the matching `--env`. | | 9 | bad_input | Fix the file or operand the message names. Never retry unchanged. | | 10 | unsupported_host | No build for this OS/architecture. Nothing to retry. | | 11 | update_unsupported | `loopky update` refused and **nothing was updated**; run the command its message names (brew, dpkg…). | | 12 | server_error | Homeserver 5xx; the write may have landed. Retry — the idempotent commands skip what did. | | 13 | timeout | Nobody approved the login in time; run `loopky login` again. | | 14 | proxy_refused | Allowlist problem. Back to `loopky doctor` and hand the user its host list. Retrying will not help. | | 15 | tls_untrusted | A proxy is re-signing TLS. Back to `loopky doctor`; the user must exempt the hosts or name the CA with `SSL_CERT_FILE`. | | 16 | homeserver_unresolved | Transient name lookup failure; retry. Not an allowlist problem. | ## Writing good cards - **One fact per card.** A back that needs "and" is two cards, and so is one with alternatives (`vegetariano / vegetariana`): split it, or keep one form. Short fronts, short backs. - **Fix a card before showing the list, never annotate it.** If you notice a card breaks a rule here, rewrite it; the user reviews cards, not caveats about them. - **Parenthesized asides are notes, not answers.** `hola (informal)`, `猫（ねこ）`: the card shows the note, but typing and Speak grade only `hola`/`猫`. Unbracketed, the note becomes part of the expected answer. - **Language decks declare their pair.** `--front-lang en-US --back-lang es-ES` (BCP-47) is what makes `--listen` and `--speak` work, and it also tags the deck `language` and `spanish` so learners find it. Without the pair the phone reads Spanish in an English voice, so both switches stay off. `--type` (typed answers) and `--reverse` (ask both directions) need no pair. - **Pictures are `https` URLs, never uploads.** SVG, TIFF, WebM and STL do not render on either phone, whatever the host: use a JPEG, PNG or WebP. Add `--check-images` to the dry-run when the URLs came from anywhere you have not fetched. Which source to take them from is the next section. - **Tags are public** and indexed network-wide. Use a few honest topic words; never copy an Anki deck's tags or description without reading them. - **Do not pad.** Make the cards the user asked for, at the count they asked for. ## Where to find pictures A picture is a prompt, so it goes on the side that asks: the thing on the front, its name on the back. Every deck is public and a card has no room for a credit line, so the licence decides the source as much as the topic does. **Try the sources in this order, and move to the next when one has no picture that shows exactly the card's fact, its host is blocked (`loopky doctor` lists them under `recommended`), or the picture's licence is not one of those below.** When none has one, leave the card without a picture: a near miss teaches the wrong thing. 1. **A source made for the topic**, when there is one. All public domain, nothing to credit. | Topic | Find it | The URL that goes on the card | | --- | --- | --- | | Country flags | the ISO 3166 code, no lookup | `https://flagcdn.com/w640/<code>.png`. Widths double from `w20` to `w2560`; anything else 404s. | | Space, astronomy, NASA missions | `images-api.nasa.gov/search?q=…&media_type=image` | `https://images-assets.nasa.gov/image/<nasa_id>/<nasa_id>~medium.jpg`, or another size `images-api.nasa.gov/asset/<nasa_id>` lists. Only items credited to NASA: a `photographer` or `secondary_creator` from outside NASA, or a © in the description, is someone else's copyright. | | Paintings, artefacts | `api.artic.edu/api/v1/artworks/search?q=…&fields=id,title,image_id,is_public_domain` | `https://www.artic.edu/iiif/2/<image_id>/full/843,/0/default.jpg`, only where `is_public_domain` is true. | | Paintings, artefacts | `collectionapi.metmuseum.org/public/collection/v1/search?hasImages=true&q=…`, then `…/objects/<id>` | The object's `primaryImageSmall`, only where `isPublicDomain` is true. | 2. **Wikimedia Commons**, for anything with a name. Read the licence before using a file: `commons.wikimedia.org/w/api.php?action=query&format=json&titles=File:<name>&prop=imageinfo&iiprop=url|extmetadata&iiurlwidth=500` gives `thumburl` and `extmetadata.LicenseShortName`. Take only addresses under `upload.wikimedia.org/wikipedia/commons/`: `/wikipedia/en/` and other per-language paths hold non-free files a Wikipedia article may use and a deck may not. Thumbnails exist only at 120, 250, 330, 500, 960, 1280 and 1920 px; any other `NNNpx-` width is a blank card. For an SVG use its `/thumb/…/500px-….svg.png` render, since the original never renders. 3. **Openverse**, which searches Flickr, museums and other open collections, with no key: `api.openverse.org/v1/images/?q=…&license=cc0,pdm` keeps to pictures that need no credit (add `,by,by-sa` only when the credit fits, below). Each result's `url` goes on the card; its `license` and `attribution` say what to credit. For an everyday object, add `&source=stocksnap,rawpixel`: unfiltered results run to old scans, product shots and unrelated photos. Anonymous use allows 20 requests a minute and 200 a day. 4. **Unsplash**, for an everyday object or scene nothing above shows: the photo's `https://images.unsplash.com/photo-…?w=1080&fm=jpg` address, never the web page's and never `plus.unsplash.com`, which is paid and licensed separately. The Unsplash Licence needs no credit. Searching Unsplash needs an API key; without one the site answers with a bot check, which is not something to work around, so use an address the user gives you or move on. **Choosing pictures for many cards, look at them on contact sheets.** Paste a few candidates per card, a handful of cards per sheet, into one image and pick from that: it costs far less than opening pictures one by one and still catches near misses. Reject a single thing for a plural word, a part standing for the whole, a brand or mascot, and alcohol on a children's deck. Fetch from one host a few at a time; Wikimedia's thumbnails answer 429 at eight parallel requests. **Licences.** Public domain, PDM and CC0 need nothing. CC BY and CC BY-SA need a credit, and the deck's `--description` is the only place for one: `Pictures: <author>, <licence>, via <source>`, per picture, within the description's 500 characters. When the credits will not fit, use a public-domain picture for those cards or leave them without one. Never use a picture marked NC, ND, "fair use", "all rights reserved" or with no licence at all, and never take an address from a search engine's results, Pinterest, Instagram, or a host that forbids hotlinking (Pixabay does): the phone fetches each picture from where it is hosted, for every learner, for as long as the deck exists. A host the sandbox cannot reach can still be right, because the phone fetches the picture, not you. `--check-images` cannot vouch for those, so tell the user which URLs went unchecked. ## Decks from a TV series "A deck from SpongeBob season 1" is a language deck: the goal is to understand the show in the language the user watches it in, so every card comes from the show's own dialogue. **Propose one deck per season before writing anything**, titled with the zero-padded season first, then the show and language (`S01 · SpongeBob · Spanish`), so the deck list sorts in season order. A season is a few hundred cards, and a deck per season lets the user stop, or start at the season they are watching. Ask which language they watch it in and which dub: a Latin-American and a Castilian dub use different words, and the deck's `--back-lang` (`es-MX`, `es-ES`) has to match the one they hear. Create each deck with `--id <show>-s<n> --if-not-exists`, so re-running the creates is safe. **Say how many cards per episode before building, and that it is a selection**, in one sentence such as "about 20 cards per episode, chosen for reuse, not the whole transcript". Users expect every line otherwise. Settle the number then: `card add` appends, so a second round lands after the whole season, and the deck walks it twice instead of episode by episode. If a later round is added anyway, put it with its episodes with one `card reorder` (above): sort the `card list` lines by the episode aside, keeping each episode's own order. Around 30 per episode is still a selection for an 11-minute segment. **Get the dialogue from subtitles in the dub's language, never from memory.** Use the user's own `.srt` files when they have them, then try, in order: | Source | Good for | How | | --- | --- | --- | | OpenSubtitles | Most shows, most languages | `rest.opensubtitles.org/search/episode-<n>/query-<show>/season-<n>/sublanguageid-<spa\|por\|fre\|ger\|jpn…>` with the header `User-Agent: TemporaryUserAgent`, no key; path segments stay in that alphabetical order, and dropping `episode-<n>` lists the season. Each result's `SubDownloadLink` (on `dl.opensubtitles.org`) is a gzipped `.srt`, often Latin-1 rather than UTF-8. Downloads stop at about 200 files a day and answer 404 past that; searches keep working, so the episode and segment list is still there. | | The show's fan wiki | Shows whose wiki is in the dub's language | Transcript pages (often `<Segment title>/transcript`) over the wiki's MediaWiki API: `<wiki>/api.php?action=query&format=json&prop=revisions&rvprop=content&rvslots=main&titles=<A>\|<B>`, several titles per request, no quota. What the voices say, not a translation. The host differs per show, so `loopky doctor` cannot list it; a wiki that answers with a bot check is not usable. | | Addic7ed | TV episodes, mostly English | `www.addic7ed.com/search.php?search=<show>` lists `serie/<Show>/<season>/<episode>/<Title>` pages; each subtitle's `/original/…` or `/updated/…` link downloads with that page as the `Referer`. | | Jimaku — `jimaku.cc` | Anime in Japanese | Each `jimaku.cc/entry/<id>` page links its files under `/entry/<id>/download/…`, no key. | | Kitsunekko — `kitsunekko.net` | Anime in Japanese | `kitsunekko.net/dirlist.php?dir=subtitles%2Fjapanese%2F` lists shows; files are `.ass` or `.srt`, sometimes zipped. | Coverage is uneven — OpenSubtitles had Spanish for three of SpongeBob's first-season segments — so search each episode, and say which ones had nothing. For a whole show, one source for every season beats a patchwork. Prefer a subtitle marked as the dub's own transcript (often "SDH" or "for the hearing impaired") over a translation of the original: a translated subtitle does not say what the voices say. Check the episode list (season, episode number, segment title) against the show's episode guide so episode 3 really is episode 3 — many cartoons split an episode into segments (`s1e01c - Tea at the Treedome`), so match on the segment title. Sources spell titles differently, so compare them normalised (lowercase, letters and digits only) and require equality: word overlap and a search's first hit both pick the wrong episode, and keep a short hand-made list for segments known under two titles. Say which guide the numbering follows, list its gaps, and tell the user which files you used. `loopky doctor` lists the fixed hosts above under `recommended`; when the one you need is blocked, ask the user to allow it, as for the required hosts. If no source is reachable or none matches the dub, stop and ask for the files: a deck built from the wrong subtitle teaches lines the show never says. **Clean the lines before choosing from them.** Drop timing, speaker labels, `[sound cues]`, cues the uploader added (an episode title card, a credit, an advertisement for a website), `♪` song lyrics, the opening and closing theme, and character and place names on their own. Join a sentence split across two subtitle cues. Four traps: - **Many subtitle files are ALL CAPS** (close to half, on one show). Detect it per file and lower-case it, restoring names and "I" when you write the card; anything that finds speaker labels by their capitals, or keeps only lines with lowercase, silently drops those episodes. - **Abbreviations split sentences.** Protect `Mr.`, `Mrs.`, `Dr.` and their kind before splitting on punctuation. - **The opening theme is not always marked with `♪`.** Cut by time: find the theme's first cue and drop everything up to about 35 seconds after it. - **Count the cleaned lines per episode.** A season with a few dozen lines is a broken cleaner, not a quiet season. **Pick what is worth learning, not the transcript.** Every deck is public, so a season's dialogue published in order is the show's script republished. Take each episode's useful words and phrases — the ones a learner needs to follow it and would hear again — and leave the rest. Cards go from the user's language to the one they are learning: the front is the meaning in their language, translated for that scene, and the back is the line or word exactly as the show says it (`--front-lang en-US --back-lang es-MX`). The user recalls the show's words, and Speak and typing grade them. A back may drop a leading filler or name (`Oh,`, `<Name>,`), since what is left is still a piece of the spoken line. Nothing from outside the show: no invented example sentences, no "related" vocabulary, and a word gets a card only in a form the episode uses. **If the user asks for the theme song,** do not card its verses, which republishes the lyrics: card its ordinary single words as vocabulary, with an aside such as `(theme)`. **Order the file by episode, and never repeat.** Cards are studied new-first in file order, so episode 1's cards come first, then episode 2's, and the user meets each episode's language before they watch it. Within an episode, a word before the phrases that use it. A line or word already carded in an earlier episode or an earlier season's deck is not carded again; compare ignoring case, punctuation and `...`. The published decks are the record of what is carded, and `loopky card list <deckId>` prints one card a line, `id<TAB>front<TAB>back` (a picture adds ` [img:…]` to its side), so it covers every season even after your working files are gone. Put the episode on the front as an aside, `I'm ready! (S1E1) → ¡Estoy listo!`: the reader sees where it comes from, and nothing grades it. Publish the first episodes with `deck create`, and add later ones in order with `card add <deckId> --from-file`, which appends. **A whole show is a pipeline: filter, brief, check, then de-duplicate.** 1. **Filter before any model reads anything.** Keep complete sentences of one to seven words, de-duplicated per episode, minus pure interjections and everything already published. That leaves about 100–250 candidates an episode; the full dialogue stays available for context. 2. **One agent per season, in parallel, with a written brief:** what to pick and skip, the exact file format, the per-episode count, whether a back may drop a leading filler, and to report a checker that looks wrong rather than bend a card to fit it. 3. **Give them a checker script, and make "prints OK" the exit condition.** It confirms that every back appears in that episode's dialogue ignoring case and punctuation, the episode aside is well formed, no back holds brackets or slashes, nothing repeats in the season or is already published, and the count is in range, with a lower bound that lets a thin episode come in short rather than padded. This is what makes "nothing from outside the show" enforceable. Test it on lines you know are genuine first: turn newlines and punctuation into a space, never into nothing, or `was...just` glues into one word and a real line fails. 4. **De-duplicate across seasons afterwards, in season order.** Parallel agents cannot see each other's output, so later seasons shrink; with the published backs filtered out in step 1 the repeats are few, without it about a third. Tell the user to expect smaller later seasons. **Pictures from the episode only when their licence allows it, which is rarely.** Stills, frames and screenshots of a commercial show are the studio's copyright, and fan wikis host them as fair use, which the licence rules above exclude; a frame from the user's own copy would be an upload, and Loopky takes only URLs. So an episode picture is limited to shows whose frames are public domain or freely licensed on Wikimedia Commons (some early cartoons). Otherwise picture what a word card names — an object, an animal, a place — from the usual sources, or leave it without one; phrase cards stay bare. Real-life counterparts of the show's world (the animals and objects it is built on) make good covers. Tell the user which it was. To add pictures to cards already published, read `loopky card list <deckId> --json --missing-image` once, match each card on its back text, and send the pictures in one JSONL `card edit --from-file`, each line naming the card's `id` and its `front_image_url`. Add the same URLs to your card file: `card add` tells cards apart by text and picture, so re-running a file without them adds those cards a second time. **Tags and settings.** Add the show's name (lowercase, no spaces, at most 20 characters: `spongebob`), and `tv-series` or `anime`, plus `cartoon` where it is one. A show made for children also gets `kids`. The language pair adds the language tags on its own. Turn on `--listen` and `--speak`, so the user hears and says the lines, and `--type` when they want to spell them; a listening deck for a child who cannot spell yet works best with `--reverse` on and `--type` off. A children's description reads well as a hook line, two lines about the season, then how to study, each on its own line with an emoji. ## Limits worth knowing - The session can write only Loopky's own data (`/pub/loopky/`). It cannot post, follow or edit a profile, and widening that is not an option. - Published decks are public. There are no private decks. - A headless box with nobody at a phone can use `LOOPKY_SESSION`, minted with `loopky login --export` on a machine where the user can approve. It is a bearer token: never echo it, log it or commit it. ## Reporting friction to Loopky Loopky improves from what agents trip over, and only the user can decide to tell the project. So when the work is done, and only if this session hit **real friction in `loopky` or this skill**, ask once whether to open a GitHub issue on `jvsena42/loopky`. Friction is: an error or exit code that misled you, a step here that was wrong or missing, a flag or command you needed and the binary did not have, a workaround you had to invent, or output you could not parse. It is **not** the user's own network allowlist, a session expiring after its hour, a picture source with nothing fitting, or anything the exit-code table already says how to handle. No real friction, no question. 1. **Ask only at the end, and collect nothing until the user says yes.** Never mid-task, not even right after the friction happens: finish what the user asked, verify it, and make this the last thing in your final message. In one short question, name the problem in general words ("`card add` failed on a newline"), say it would become a public issue on `jvsena42/loopky`, and ask whether they want one. Leave the rest for after a yes. Until they say yes, run nothing for it, check no GitHub account, and write no draft. A no, or no answer, ends it for the rest of the session. 2. **After a yes, gather only what reproduces the problem:** `loopky --version`, the OS and architecture, the command's shape with every operand replaced by a placeholder, the exit code and `error.code`, what you expected, what happened, and the workaround if there was one. 3. **Keep the user's data out.** The issue is public, so it never carries card or deck content, titles, descriptions or tags, deck or card ids, public keys, `pubky://` addresses, image or homeserver URLs, file or directory names, user, host or machine names, IP addresses, the `auth_url`, `LOOPKY_SESSION` or any other token, environment variables, or anything the user said about themselves. Describe error messages in your own words rather than pasting them, since they can carry ids and paths. Re-read the draft against this list before showing it. If the problem cannot be explained without one of these, leave it out and say so. 4. **Show the draft, title and body, and file it only after the user approves that text.** If the session has a signed-in GitHub tool (`gh auth status` succeeds, or a GitHub connector is available), use it, searching the repository's open issues first and adding to a matching one rather than opening a duplicate: ```shell gh issue create --repo jvsena42/loopky --title "<title>" --body-file <draft file> ``` The draft file is a temporary one; delete it afterwards. Otherwise, or if they prefer, give them the link to file it themselves, `https://github.com/jvsena42/loopky/issues/new`, with the draft to paste. Issues are public, and are filed from the user's own account. 22:o831,11:[["$","script",null,{"type":"application/ld+json","dangerouslySetInnerHTML":{"__html":"{\"@context\":\"https://schema.org\",\"@type\":\"SoftwareApplication\",\"name\":\"Loopky flashcards\",\"description\":\"Anki-style spaced-repetition flashcards from Claude: build a deck from any topic, import an Anki .apkg or a TSV, add pictures and a language pair for listening and speaking practice, then study it in the free Loopky app on Android and iOS.\",\"applicationCategory\":\"Learning & teaching\",\"operatingSystem\":\"Claude\",\"url\":\"https://agentready.co/connectors/loopky-flashcards\",\"sameAs\":[],\"publisher\":{\"@type\":\"Organization\",\"name\":\"jvsena42\",\"url\":\"https://github.com\"}}"}}],["$","div",null,{"className":"wrap","children":[["$","div",null,{"className":"pp-head","children":[["$","$L23",null,{"name":"Loopky flashcards","url":null,"size":56}],["$","div",null,{"children":[["$","div",null,{"className":"crumbs","children":[["$","$L5",null,{"href":"/","children":"Connectors"}],[" / ",["$","$L5",null,{"href":"/categories/learning","children":"Learning & teaching"}]]]}],["$","h1",null,{"children":["Loopky flashcards",null]}]]}]]}],["$","div",null,{"className":"pp","children":[["$","div",null,{"className":"ca","children":[["$","p",null,{"className":"tag","children":"Anki-style spaced-repetition flashcards from your AI: build a deck from any topic, import an Anki .apkg or a TSV, add pictures and a language pair for listening and speaking practice, then study it in the free Loopky app on Android and iOS."}],null,["$","$L24",null,{"examples":[],"tools":[],"prefix":"","server":null,"instructions":[],"skills":[{"name":"loopky","label":"loopky","gist":"Build and manage Loopky flashcard decks with the `loopky` CLI - make Anki-style spaced-repetition cards from any topic, import an Anki .apkg or a TSV, add, edit or illustrate cards, publish a language","source":"https://github.com/jvsena42/loopky/blob/224c7c8b8b4aafa28b3ccd32b25a2037b21f6125/plugins/loopky/skills/loopky/SKILL.md","raw":"$25"}],"skillNote":"1 in the Claude listing"}],null]}],"$L26"]}]]}]] 22:oa62,1b:[["$","title","0",{"children":"Loopky flashcards by jvsena42: AI connector · Agent Ready"}],["$","meta","1",{"name":"description","content":"Anki-style spaced-repetition flashcards from Claude: build a deck from any topic, import an Anki .apkg or a TSV, add pictures and a language pair for…"}],["$","link","2",{"rel":"manifest","href":"/manifest.webmanifest","crossOrigin":"$undefined"}],["$","link","3",{"rel":"canonical","href":"https://agentready.co/connectors/loopky-flashcards"}],["$","meta","4",{"property":"og:title","content":"Loopky flashcards by jvsena42: AI connector"}],["$","meta","5",{"property":"og:description","content":"Anki-style spaced-repetition flashcards from Claude: build a deck from any topic, import an Anki .apkg or a TSV, add pictures and a language pair for…"}],["$","meta","6",{"property":"og:url","content":"https://agentready.co/connectors/loopky-flashcards"}],["$","meta","7",{"property":"og:site_name","content":"Agent Ready"}],["$","meta","8",{"property":"og:image","content":"https://agentready.co/connectors/loopky-flashcards/opengraph-image?3b61e23efdbb5225"}],["$","meta","9",{"property":"og:image:type","content":"image/png"}],["$","meta","10",{"property":"og:image:width","content":"1200"}],["$","meta","11",{"property":"og:image:height","content":"630"}],["$","meta","12",{"property":"og:image:alt","content":"AI connector on Agent Ready"}],["$","meta","13",{"property":"og:type","content":"website"}],["$","meta","14",{"name":"twitter:card","content":"summary_large_image"}],["$","meta","15",{"name":"twitter:title","content":"Loopky flashcards by jvsena42: AI connector"}],["$","meta","16",{"name":"twitter:description","content":"Anki-style spaced-repetition flashcards from Claude: build a deck from any topic, import an Anki .apkg or a TSV, add pictures and a language pair for…"}],["$","meta","17",{"name":"twitter:image","content":"https://agentready.co/connectors/loopky-flashcards/opengraph-image?3b61e23efdbb5225"}],["$","meta","18",{"name":"twitter:image:alt","content":"AI connector on Agent Ready"}],["$","meta","19",{"name":"twitter:image:type","content":"image/png"}],["$","meta","20",{"name":"twitter:image:width","content":"1200"}],["$","meta","21",{"name":"twitter:image:height","content":"630"}],["$","link","22",{"rel":"icon","href":"/favicon.ico?favicon.3iymezf4ycw3e.ico","sizes":"64x64","type":"image/x-icon"}],["$","link","23",{"rel":"icon","href":"/icon.svg?icon.1m07wgr9jqhm5.svg","sizes":"any","type":"image/svg+xml"}],["$","link","24",{"rel":"apple-touch-icon","href":"/apple-icon.png?apple-icon.3q8qrgufoflqu.png","sizes":"180x180","type":"image/png"}],["$","$L27","25",{}]] 22:o10,1c:null 22:null 22:o22,:HL["/stores/claude.png","image"] 22:o130c,26:["$","aside",null,{"className":"side","children":[["$","div",null,{"className":"card","children":[["$","h2",null,{"children":"Stores"}],["$","div",null,{"className":"st","children":[["$","div","claude",{"style":{"display":"contents"},"children":[["$","span",null,{"className":"s","children":[["$","img",null,{"className":"sm","src":"/stores/claude.png","alt":"","width":16,"height":16}],["$","b",null,{"children":"Claude"}],["$","a",null,{"className":"src","href":"https://github.com/jvsena42/loopky","target":"_blank","rel":"noopener nofollow","children":"Source ↗"}]]}],["$","span",null,{"className":"rk2","children":[["$","small",null,{"children":"Listed, not ranked"}],null]}]]}]]}]]}],["$","div",null,{"className":"card","children":[["$","h2",null,{"children":"Details"}],["$","dl",null,{"className":"kv","children":[[["$","dt",null,{"children":"Company"}],["$","dd",null,{"children":"jvsena42"}]],[["$","dt",null,{"children":"Publisher"}],["$","dd",null,{"children":"Community"}]],["$","dt",null,{"children":"Category"}],["$","dd",null,{"children":["$","$L5",null,{"href":"/categories/learning","children":"Learning & teaching"}]}],[["$","dt",null,{"children":"Audience"}],["$","dd",null,{"children":"For consumers"}]],null,["$","dt",null,{"children":"Sign-in"}],["$","dd",null,{"children":"None needed"}],["$","dt",null,{"children":"Interactive UI"}],["$","dd",null,{"children":"No"}],[["$","dt",null,{"children":"Checked"}],["$","dd",null,{"children":"Oct 27, 2026"}]],null]}]]}],["$","div",null,{"className":"card","children":[["$","h2",null,{"children":["More in ","Learning & teaching"]}],["$","ul",null,{"className":"sim","children":[["$","li","14979",{"children":["$","$L5",null,{"href":"/connectors/ahamotion","prefetch":false,"children":[["$","$L23",null,{"name":"AhaMotion","url":"https://bodgzvrssuydrdmsrqsh.supabase.co/storage/v1/object/public/listing-media/v/ee/ee251ed77c14960827746e164927a4f54438f011dbe9fb6b45a178c9e5651d9f-64.webp","size":24}],["$","b",null,{"children":"AhaMotion"}],["$","small",null,{"children":"#164"}]]}]}],["$","li","4305",{"children":["$","$L5",null,{"href":"/connectors/coursera","prefetch":false,"children":[["$","$L23",null,{"name":"Coursera","url":"https://bodgzvrssuydrdmsrqsh.supabase.co/storage/v1/object/public/listing-media/v/db/dbf38707899973debd8ae7084c4f123c496e92d2aeea05c96f03cb7365fb6bb0-64.webp","size":24}],["$","b",null,{"children":"Coursera"}],["$","small",null,{"children":"#147"}]]}]}],["$","li","4727",{"children":["$","$L5",null,{"href":"/connectors/kahoot","prefetch":false,"children":[["$","$L23",null,{"name":"Kahoot!","url":"https://bodgzvrssuydrdmsrqsh.supabase.co/storage/v1/object/public/listing-media/v/03/034844173668986e8dd3c3df114ea63e9afc07ff90595b86dedf816d462080a3-64.webp","size":24}],["$","b",null,{"children":"Kahoot!"}],["$","small",null,{"children":"#515"}]]}]}],["$","li","14952",{"children":["$","$L5",null,{"href":"/connectors/quizlet","prefetch":false,"children":[["$","$L23",null,{"name":"Quizlet","url":"https://bodgzvrssuydrdmsrqsh.supabase.co/storage/v1/object/public/listing-media/v/b8/b86199a994e55145d0146787685cccb43f5568b2941b84be8549eff8e8f9bc76-64.webp","size":24}],["$","b",null,{"children":"Quizlet"}],["$","small",null,{"children":"#2,339"}]]}]}],["$","li","4317",{"children":["$","$L5",null,{"href":"/connectors/learning-commons","prefetch":false,"children":[["$","$L23",null,{"name":"Learning Commons","url":"https://bodgzvrssuydrdmsrqsh.supabase.co/storage/v1/object/public/listing-media/v/a0/a0b7e829783a839e85fedf28d175a4dffbfceba97791e0ed6446ece36d44da5f-64.webp","size":24}],["$","b",null,{"children":"Learning Commons"}],["$","small",null,{"children":"#161"}]]}]}],["$","li","14993",{"children":["$","$L5",null,{"href":"/connectors/wayground","prefetch":false,"children":[["$","$L23",null,{"name":"Wayground","url":"https://bodgzvrssuydrdmsrqsh.supabase.co/storage/v1/object/public/listing-media/v/44/44081a943fb0498f417826d3431f69e680fc6a61b7b8236ccfd771bb715e09a0-64.webp","size":24}],["$","b",null,{"children":"Wayground"}],["$","small",null,{"children":"#204"}]]}]}],["$","li","15104",{"children":["$","$L5",null,{"href":"/connectors/sketchy-medical","prefetch":false,"children":[["$","$L23",null,{"name":"Sketchy Medical","url":"https://bodgzvrssuydrdmsrqsh.supabase.co/storage/v1/object/public/listing-media/v/24/24a33a07be7c55c7c45bafa8060bf20186e05b2bed57b4f4fef6a6577a51d7a0-64.webp","size":24}],["$","b",null,{"children":"Sketchy Medical"}],["$","small",null,{"children":"#1,492"}]]}]}],["$","li","4325",{"children":["$","$L5",null,{"href":"/connectors/udemy-business","prefetch":false,"children":[["$","$L23",null,{"name":"Udemy Business","url":"https://bodgzvrssuydrdmsrqsh.supabase.co/storage/v1/object/public/listing-media/v/65/6588360147a197fc6b2733bea6df87ef7ad3444e4c58ef1994029dd4666e7f26-64.webp","size":24}],"$L28","$L29"]}]}]]}]]}]]}] 22:o5a,28:["$","b",null,{"children":"Udemy Business"}] 29:["$","small",null,{"children":"#190"}] 22:o11,20:false 1f:7037 22:o17,1e:C 1d:C 1:C 15:C b:C 22:C </article></body></html>

22:o1,#22:o64d,2:"$Sreact.fragment" 3:"/_next/static/immutable/chunks/12yk9g49l7-7r.js" 4:"/_next/static/immutable/chunks/2jrhxdtf12-uf.js" 5:I[7575,["$3","$4"],""] 6:I[10291,["$3"],"default"] 7:I[2968,["$3"],"default"] 8:I[4098,["$3"],"WebMCP"] 9:I[57507,["$3"],"ExternalLinks"] a:I[93137,["$3"],"Analytics"] 10:"$Sreact.suspense" 16:"ViewportBoundary" 17:I[82520,["$3"],"$16"] 19:"MetadataBoundary" 1a:I[82520,["$3"],"$19"] :HL["/_next/static/immutable/chunks/3g2_9hnyt6p64.css","style"] 1:X b:X d:X 15:X f:[["children",{"s":"__PAGE__","h":49314,"d":{"r":["$","$2","c",{"children":[["$","$10",null,{"fallback":["$","div",null,{"className":"wrap","style":{"minHeight":"60vh"}}],"children":"$L11"}],["$L12","$L13"],"$L14"]}],"p":false,"v":"$15"}}]] e:[["children",{"s":{"n":"slug","t":"d","k":"loopky-flashcards","s":[]},"h":49250,"d":{"r":["$","$2","c",{"children":[null,["$","$L6",null,{"parallelRouterKey":"children","error":"$undefined","errorStyles":"$undefined","errorScripts":"$undefined","template":["$","$L7",null,{}],"templateStyles":"$undefined","templateScripts":"$undefined","notFound":"$undefined","forbidden":"$undefined","unauthorized":"$undefined"}]]}],"p":false,"v":"$d"},"c":"$Qf"}]] c:[["children",{"s":"connectors","h":49250,"d":{"r":["$","$2","c",{"children":[null,["$","$L6",null,{"parallelRouterKey":"children","error":"$undefined","errorStyles":"$undefined","errorScripts":"$undefined","template":["$","$L7",null,{}],"templateStyles":"$undefined","templateScripts":"$undefined","notFound":"$undefined","forbidden":"$undefined","unauthorized":"$undefined"}]]}],"p":false,"v":"$d"},"c":"$Qe"}]] 1d:X 1e:X 22:o1232,0:{"q":"","i":false,"S":true,"r":"$1","t":{"t":{"s":"","h":49234,"d":{"r":["$","$2","c",{"children":[[["$","link","0",{"rel":"stylesheet","href":"/_next/static/immutable/chunks/3g2_9hnyt6p64.css","precedence":"next","crossOrigin":"$undefined","nonce":"$undefined"}],["$","script","script-0",{"src":"/_next/static/immutable/chunks/12yk9g49l7-7r.js","async":true,"nonce":"$undefined"}]],["$","html",null,{"lang":"en","className":"ec5Qua_variable","children":["$","body",null,{"children":[["$","script",null,{"type":"application/ld+json","dangerouslySetInnerHTML":{"__html":"{\"@context\":\"https://schema.org\",\"@graph\":[{\"@type\":\"Organization\",\"@id\":\"https://agentready.co/#org\",\"name\":\"Agent Ready\",\"url\":\"https://agentready.co/\",\"logo\":\"https://agentready.co/icon-512.png\"},{\"@type\":\"WebSite\",\"@id\":\"https://agentready.co/#site\",\"name\":\"Agent Ready\",\"url\":\"https://agentready.co/\",\"publisher\":{\"@id\":\"https://agentready.co/#org\"}}]}"}}],["$","header",null,{"className":"site","children":["$","div",null,{"className":"wrap","children":[["$","$L5",null,{"href":"/","className":"brand","children":[["$","svg",null,{"className":"brand-mark","viewBox":"0 0 64 64","aria-hidden":"true","children":[["$","defs",null,{"children":["$","linearGradient",null,{"id":"arg","x1":"0","y1":"1","x2":"1","y2":"0","children":[["$","stop",null,{"offset":"0","stopColor":"#2563EB"}],["$","stop",null,{"offset":"1","stopColor":"#06B6D4"}]]}]}],["$","path",null,{"d":"M9 55 L32 9 L55 55","fill":"none","stroke":"url(#arg)","strokeWidth":"11","strokeLinecap":"round","strokeLinejoin":"round"}],["$","circle",null,{"cx":"32","cy":"45","r":"7","fill":"#FACC15"}]]}],"Agent Ready"]}],["$","nav",null,{"aria-label":"Main","children":[["$","$L5",null,{"href":"/","children":"Connectors"}],["$","$L5",null,{"href":"/categories","className":"nv-x","children":"Categories"}],["$","$L5",null,{"href":"/blog","children":"Blog"}],["$","$L5",null,{"href":"/mcp-plugin-usage","className":"nv-x","children":"Usage"}],["$","$L5",null,{"href":"/methodology","className":"nv-x","children":"Methodology"}],["$","$L5",null,{"href":"/work-with-us","className":"nv-cta","children":"Work with us"}]]}]]}]}],["$","main",null,{"children":["$","$L6",null,{"parallelRouterKey":"children","error":"$undefined","errorStyles":"$undefined","errorScripts":"$undefined","template":["$","$L7",null,{}],"templateStyles":"$undefined","templateScripts":"$undefined","notFound":[[["$","title",null,{"children":"404: This page could not be found."}],["$","div",null,{"style":{"fontFamily":"system-ui,\"Segoe UI\",Roboto,Helvetica,Arial,sans-serif,\"Apple Color Emoji\",\"Segoe UI Emoji\"","height":"100vh","textAlign":"center","display":"flex","flexDirection":"column","alignItems":"center","justifyContent":"center"},"children":["$","div",null,{"children":[["$","style",null,{"dangerouslySetInnerHTML":{"__html":"body{color:#000;background:#fff;margin:0}.next-error-h1{border-right:1px solid rgba(0,0,0,.3)}@media (prefers-color-scheme:dark){body{color:#fff;background:#000}.next-error-h1{border-right:1px solid rgba(255,255,255,.3)}}"}}],["$","h1",null,{"className":"next-error-h1","style":{"display":"inline-block","margin":"0 20px 0 0","padding":"0 23px 0 0","fontSize":24,"fontWeight":500,"verticalAlign":"top","lineHeight":"49px"},"children":404}],["$","div",null,{"style":{"display":"inline-block"},"children":["$","h2",null,{"style":{"fontSize":14,"fontWeight":400,"lineHeight":"49px","margin":0},"children":"This page could not be found."}]}]]}]}]],[]],"forbidden":"$undefined","unauthorized":"$undefined"}]}],["$","$L8",null,{}],["$","$L9",null,{}],["$","$La",null,{}],["$","footer",null,{"className":"foot","children":["$","div",null,{"className":"wrap","children":[["$","span",null,{"children":"Agent Ready"}],["$","nav",null,{"aria-label":"Footer","children":[["$","$L5",null,{"href":"/blog","children":"Blog"}],["$","$L5",null,{"href":"/mcp-plugin-usage","children":"Usage"}],["$","$L5",null,{"href":"/methodology","children":"Methodology"}],["$","$L5",null,{"href":"/categories","children":"Categories"}],["$","a",null,{"href":"/llms.txt","children":"llms.txt"}],["$","a",null,{"href":"/sitemap.xml","children":"Sitemap"}],["$","$L5",null,{"href":"/work-with-us","children":"Work with us"}]]}]]}]}]]}]}]]}],"p":false,"v":"$b"},"c":"$Qc"},"h":{"r":["$","$2","h",{"children":[null,["$","$L17","AW8u3Cu4ifG5nk4GhBCzkv",{"children":"$L18"}],["$","$L1a","AW8u3Cu4ifG5nk4GhBCzkm",{"children":[["$","div",null,{"hidden":true,"children":["$","$10",null,{"name":"Next.Metadata","children":"$L1b"}]}],"$L1c"]}]]}],"p":false,"v":"$1d"}},"s":"$1e","a":"$@1f","w":"$@20"} 22:o1b1,21:I[82520,["$3"],"OutletBoundary"] :HL["/_next/static/immutable/chunks/2lo4itc7piqdu.css","style"] d:C 12:["$","link","0",{"rel":"stylesheet","href":"/_next/static/immutable/chunks/2lo4itc7piqdu.css","precedence":"next","crossOrigin":"$undefined","nonce":"$undefined"}] 13:["$","script","script-0",{"src":"/_next/static/immutable/chunks/2jrhxdtf12-uf.js","async":true,"nonce":"$undefined"}] 14:["$","$L21",null,{"children":"$@22"}] 22:o14d,1e:300 18:[["$","meta","0",{"charSet":"utf-8"}],["$","meta","1",{"name":"viewport","content":"width=device-width, initial-scale=1"}],["$","meta","2",{"name":"theme-color","content":"#ffffff","media":"(prefers-color-scheme: light)"}],["$","meta","3",{"name":"theme-color","content":"#0d0d0f","media":"(prefers-color-scheme: dark)"}]] 22:o25,1d:0 15:0 15:T4,slug1d:T4,slug1e:300 22:o68,23:I[37521,["$3","$4"],"Logo"] 24:I[53913,["$3","$4"],"Explore"] 27:I[60329,["$3"],"IconMark"] 25:T6f29,22:o6f29,--- name: loopky description: Build and manage Loopky flashcard decks with the `loopky` CLI - make Anki-style spaced-repetition cards from any topic, import an Anki .apkg or a TSV, add, edit or illustrate cards, publish a language deck with Listen/Speak, or learn a language from a TV series' episodes. Use whenever the user asks for flashcards, Anki cards, a study, vocabulary or exam deck, spaced repetition, or mentions Loopky, even if they do not name the CLI. --- # Loopky flashcards through the `loopky` CLI Loopky is a free spaced-repetition flashcards app (Android, iOS). `loopky` is its headless client: it writes decks to the user's own account, and they study them on their phone. It manages decks and cards; it does not study. **If the user needs a file for Anki itself** (an `.apkg` to open in Anki), Loopky is not that: say so, and offer Loopky as the option rather than substituting it. Loopky *imports* Anki decks; it does not export them. **The binary is the reference, this file is the workflow.** Flags, operands, result shapes and exit codes come from `loopky commands --json` and `loopky --help`. Read them rather than guessing, and trust them over anything here. ## Workflow 1. **Check the CLI is there:** `loopky --version`. If it fails, **stop** and ask the user to install `loopky`, pointing them at (Homebrew, a `.deb`, or the release installer for Linux, macOS and Windows). Do not download or install it yourself — this plugin runs only code that was reviewed with it. In a cloud session, suggest installing it in the environment's setup script so the next session has it. Once they have, run `loopky --version` again; if the shell cannot find it, it is usually in `~/.local/bin` (Windows: `%LOCALAPPDATA%\Programs\loopky`), which has to be on `PATH`. 2. **Read the surface:** `loopky commands --json`. No session, no network. 3. **Check the network:** `loopky doctor --json`. On exit 14 or 15, **stop**: the sandbox's allowlist blocks hosts Loopky needs, and only the user can change it. Show them `data.next_step` and `data.allowlist` verbatim — the hosts, and where their product keeps that setting. No package, script or retry can add a host for them. 4. **Sign in:** `loopky login --json --timeout 300`. The user approves with Pubky Ring on their phone. Show them the QR code **and** the `auth_url` from the output in a code block — on the device they chat from, they may open the link instead of scanning. The link is a login secret until approved: show it only to them, nowhere else. Exit 13 means nobody approved in time; run `login` again for a fresh code. A session lasts about an hour. 5. **Write the cards to a file** (TSV: `frontback`, optionally two more columns of `https` image URLs, one per side; JSONL when a side holds a tab or a newline). Show the user the list before publishing anything. Keep working files (card files, downloaded sources, your scripts) in the user's working directory or one they name, not the system's temporary directory, which a long session can lose with everything in it. 6. **Dry-run every write first:** ```shell loopky deck create --title "" --from-file cards.tsv --dry-run --json ``` `--dry-run` exists on `deck create`, `card add` and `import`, and runs that command's own parser. Read `image_advice` in the result and fix what it names. 7. **Publish:** ```shell loopky deck create --title "<Title>" --tag <topic> --from-file cards.tsv --json ``` Add `--id <word> --if-not-exists` when a retry must not publish a second deck. 8. **Verify from what was stored, not what was sent:** `loopky deck show <deckId> --json` and `loopky card list <deckId> --json`. Results sit under `data`; a card's `front` is an object with `.text` and `.image`, not a string. Tell the user the deck is on their phone under the title. 9. **If the CLI or this skill got in the way, ask whether to report it**, once, at the end, as the last section describes. Nothing is gathered before a yes, and nothing is sent until the user approves the exact text. **Several commands in a row belong in `loopky batch`.** Each invocation pays ~2s of start-up and a session round trip; a batch pays once. One JSON line per operation: `{"argv": ["card", "add", "<deckId>", "--front", "…", "--back", "…"]}`, run with `loopky batch ops.ndjson --json`. Its output is one JSON line per operation, as each one runs, then a summary line last: read it line by line, since parsing it as one document fails. It is not transactional: on failure, fix the cause and re-run the same file — `card add`, `card edit --from-file` and `deck create --id --if-not-exists` skip what already landed. **A card in the wrong place moves with `loopky card mv <deckId> <cardId> --after <cardId>`**, or `--to <position>`, counting from 1 as `card list` prints them. Never delete and re-add a card to move it: the new card has a new id, and everyone studying the deck loses their progress on it. A move keeps it. Put several moves in one `loopky batch`: each `card mv` reads the whole deck before its one write, and only a batch pays for that read once. A card already in place writes nothing, so the file can be re-run. Keep `card mv` to a few cards. **Many cards out of place, reorder the whole deck from a file.** `loopky card list <deckId>` prints one card a line with its id first; put those lines in the order wanted and run `loopky card reorder <deckId> --from-file order.txt --dry-run`, then without `--dry-run`. Only the first column is read, and the file has to name every card exactly once, or nothing is written. Every card keeps its id, so nobody studying the deck loses progress. If it fails partway (exit 4, 5 or 12), run the same command again with the same file: that finishes it, and until then the deck still has every card but refuses card writes with exit 9. If the file is lost, the output of `card list` works as the file. **Already have an Anki deck?** `loopky import deck.apkg --dry-run --json` first — check which fields became front and back (`--front-field`/`--back-field` override it) and `images.bytes`, since an `.apkg` is the one import that uploads pictures against a 1 GB quota. Then `loopky import deck.apkg --title "<Title>"`. ## Exit codes Branch on the exit code (or `error.code` in the JSON) before reading the message. | Exit | Name | What to do | | --- | --- | --- | | 0 | ok | Carry on. | | 1 | internal | Report it as a bug; do not loop on it. | | 2 | usage | Fix the command line with `loopky <command> --help`. Never retry unchanged. | | 3 | not_signed_in | Run `loopky login` with the user. | | 4 | session_expired | Stop and ask the user to approve a new `loopky login`, then re-run what failed. Writes die after about an hour while reads still work. | | 5 | network | Retry as-is, a few times with a pause. | | 6 | not_found | Check the id with `loopky deck list --json`. | | 7 | storage_full | Terminal: the account is out of quota. Never retry; tell the user. | | 8 | environment_mismatch | The session belongs to the other network; re-run with the matching `--env`. | | 9 | bad_input | Fix the file or operand the message names. Never retry unchanged. | | 10 | unsupported_host | No build for this OS/architecture. Nothing to retry. | | 11 | update_unsupported | `loopky update` refused and **nothing was updated**; run the command its message names (brew, dpkg…). | | 12 | server_error | Homeserver 5xx; the write may have landed. Retry — the idempotent commands skip what did. | | 13 | timeout | Nobody approved the login in time; run `loopky login` again. | | 14 | proxy_refused | Allowlist problem. Back to `loopky doctor` and hand the user its host list. Retrying will not help. | | 15 | tls_untrusted | A proxy is re-signing TLS. Back to `loopky doctor`; the user must exempt the hosts or name the CA with `SSL_CERT_FILE`. | | 16 | homeserver_unresolved | Transient name lookup failure; retry. Not an allowlist problem. | ## Writing good cards - **One fact per card.** A back that needs "and" is two cards, and so is one with alternatives (`vegetariano / vegetariana`): split it, or keep one form. Short fronts, short backs. - **Fix a card before showing the list, never annotate it.** If you notice a card breaks a rule here, rewrite it; the user reviews cards, not caveats about them. - **Parenthesized asides are notes, not answers.** `hola (informal)`, `猫（ねこ）`: the card shows the note, but typing and Speak grade only `hola`/`猫`. Unbracketed, the note becomes part of the expected answer. - **Language decks declare their pair.** `--front-lang en-US --back-lang es-ES` (BCP-47) is what makes `--listen` and `--speak` work, and it also tags the deck `language` and `spanish` so learners find it. Without the pair the phone reads Spanish in an English voice, so both switches stay off. `--type` (typed answers) and `--reverse` (ask both directions) need no pair. - **Pictures are `https` URLs, never uploads.** SVG, TIFF, WebM and STL do not render on either phone, whatever the host: use a JPEG, PNG or WebP. Add `--check-images` to the dry-run when the URLs came from anywhere you have not fetched. Which source to take them from is the next section. - **Tags are public** and indexed network-wide. Use a few honest topic words; never copy an Anki deck's tags or description without reading them. - **Do not pad.** Make the cards the user asked for, at the count they asked for. ## Where to find pictures A picture is a prompt, so it goes on the side that asks: the thing on the front, its name on the back. Every deck is public and a card has no room for a credit line, so the licence decides the source as much as the topic does. **Try the sources in this order, and move to the next when one has no picture that shows exactly the card's fact, its host is blocked (`loopky doctor` lists them under `recommended`), or the picture's licence is not one of those below.** When none has one, leave the card without a picture: a near miss teaches the wrong thing. 1. **A source made for the topic**, when there is one. All public domain, nothing to credit. | Topic | Find it | The URL that goes on the card | | --- | --- | --- | | Country flags | the ISO 3166 code, no lookup | `https://flagcdn.com/w640/<code>.png`. Widths double from `w20` to `w2560`; anything else 404s. | | Space, astronomy, NASA missions | `images-api.nasa.gov/search?q=…&media_type=image` | `https://images-assets.nasa.gov/image/<nasa_id>/<nasa_id>~medium.jpg`, or another size `images-api.nasa.gov/asset/<nasa_id>` lists. Only items credited to NASA: a `photographer` or `secondary_creator` from outside NASA, or a © in the description, is someone else's copyright. | | Paintings, artefacts | `api.artic.edu/api/v1/artworks/search?q=…&fields=id,title,image_id,is_public_domain` | `https://www.artic.edu/iiif/2/<image_id>/full/843,/0/default.jpg`, only where `is_public_domain` is true. | | Paintings, artefacts | `collectionapi.metmuseum.org/public/collection/v1/search?hasImages=true&q=…`, then `…/objects/<id>` | The object's `primaryImageSmall`, only where `isPublicDomain` is true. | 2. **Wikimedia Commons**, for anything with a name. Read the licence before using a file: `commons.wikimedia.org/w/api.php?action=query&format=json&titles=File:<name>&prop=imageinfo&iiprop=url|extmetadata&iiurlwidth=500` gives `thumburl` and `extmetadata.LicenseShortName`. Take only addresses under `upload.wikimedia.org/wikipedia/commons/`: `/wikipedia/en/` and other per-language paths hold non-free files a Wikipedia article may use and a deck may not. Thumbnails exist only at 120, 250, 330, 500, 960, 1280 and 1920 px; any other `NNNpx-` width is a blank card. For an SVG use its `/thumb/…/500px-….svg.png` render, since the original never renders. 3. **Openverse**, which searches Flickr, museums and other open collections, with no key: `api.openverse.org/v1/images/?q=…&license=cc0,pdm` keeps to pictures that need no credit (add `,by,by-sa` only when the credit fits, below). Each result's `url` goes on the card; its `license` and `attribution` say what to credit. For an everyday object, add `&source=stocksnap,rawpixel`: unfiltered results run to old scans, product shots and unrelated photos. Anonymous use allows 20 requests a minute and 200 a day. 4. **Unsplash**, for an everyday object or scene nothing above shows: the photo's `https://images.unsplash.com/photo-…?w=1080&fm=jpg` address, never the web page's and never `plus.unsplash.com`, which is paid and licensed separately. The Unsplash Licence needs no credit. Searching Unsplash needs an API key; without one the site answers with a bot check, which is not something to work around, so use an address the user gives you or move on. **Choosing pictures for many cards, look at them on contact sheets.** Paste a few candidates per card, a handful of cards per sheet, into one image and pick from that: it costs far less than opening pictures one by one and still catches near misses. Reject a single thing for a plural word, a part standing for the whole, a brand or mascot, and alcohol on a children's deck. Fetch from one host a few at a time; Wikimedia's thumbnails answer 429 at eight parallel requests. **Licences.** Public domain, PDM and CC0 need nothing. CC BY and CC BY-SA need a credit, and the deck's `--description` is the only place for one: `Pictures: <author>, <licence>, via <source>`, per picture, within the description's 500 characters. When the credits will not fit, use a public-domain picture for those cards or leave them without one. Never use a picture marked NC, ND, "fair use", "all rights reserved" or with no licence at all, and never take an address from a search engine's results, Pinterest, Instagram, or a host that forbids hotlinking (Pixabay does): the phone fetches each picture from where it is hosted, for every learner, for as long as the deck exists. A host the sandbox cannot reach can still be right, because the phone fetches the picture, not you. `--check-images` cannot vouch for those, so tell the user which URLs went unchecked. ## Decks from a TV series "A deck from SpongeBob season 1" is a language deck: the goal is to understand the show in the language the user watches it in, so every card comes from the show's own dialogue. **Propose one deck per season before writing anything**, titled with the zero-padded season first, then the show and language (`S01 · SpongeBob · Spanish`), so the deck list sorts in season order. A season is a few hundred cards, and a deck per season lets the user stop, or start at the season they are watching. Ask which language they watch it in and which dub: a Latin-American and a Castilian dub use different words, and the deck's `--back-lang` (`es-MX`, `es-ES`) has to match the one they hear. Create each deck with `--id <show>-s<n> --if-not-exists`, so re-running the creates is safe. **Say how many cards per episode before building, and that it is a selection**, in one sentence such as "about 20 cards per episode, chosen for reuse, not the whole transcript". Users expect every line otherwise. Settle the number then: `card add` appends, so a second round lands after the whole season, and the deck walks it twice instead of episode by episode. If a later round is added anyway, put it with its episodes with one `card reorder` (above): sort the `card list` lines by the episode aside, keeping each episode's own order. Around 30 per episode is still a selection for an 11-minute segment. **Get the dialogue from subtitles in the dub's language, never from memory.** Use the user's own `.srt` files when they have them, then try, in order: | Source | Good for | How | | --- | --- | --- | | OpenSubtitles | Most shows, most languages | `rest.opensubtitles.org/search/episode-<n>/query-<show>/season-<n>/sublanguageid-<spa\|por\|fre\|ger\|jpn…>` with the header `User-Agent: TemporaryUserAgent`, no key; path segments stay in that alphabetical order, and dropping `episode-<n>` lists the season. Each result's `SubDownloadLink` (on `dl.opensubtitles.org`) is a gzipped `.srt`, often Latin-1 rather than UTF-8. Downloads stop at about 200 files a day and answer 404 past that; searches keep working, so the episode and segment list is still there. | | The show's fan wiki | Shows whose wiki is in the dub's language | Transcript pages (often `<Segment title>/transcript`) over the wiki's MediaWiki API: `<wiki>/api.php?action=query&format=json&prop=revisions&rvprop=content&rvslots=main&titles=<A>\|<B>`, several titles per request, no quota. What the voices say, not a translation. The host differs per show, so `loopky doctor` cannot list it; a wiki that answers with a bot check is not usable. | | Addic7ed | TV episodes, mostly English | `www.addic7ed.com/search.php?search=<show>` lists `serie/<Show>/<season>/<episode>/<Title>` pages; each subtitle's `/original/…` or `/updated/…` link downloads with that page as the `Referer`. | | Jimaku — `jimaku.cc` | Anime in Japanese | Each `jimaku.cc/entry/<id>` page links its files under `/entry/<id>/download/…`, no key. | | Kitsunekko — `kitsunekko.net` | Anime in Japanese | `kitsunekko.net/dirlist.php?dir=subtitles%2Fjapanese%2F` lists shows; files are `.ass` or `.srt`, sometimes zipped. | Coverage is uneven — OpenSubtitles had Spanish for three of SpongeBob's first-season segments — so search each episode, and say which ones had nothing. For a whole show, one source for every season beats a patchwork. Prefer a subtitle marked as the dub's own transcript (often "SDH" or "for the hearing impaired") over a translation of the original: a translated subtitle does not say what the voices say. Check the episode list (season, episode number, segment title) against the show's episode guide so episode 3 really is episode 3 — many cartoons split an episode into segments (`s1e01c - Tea at the Treedome`), so match on the segment title. Sources spell titles differently, so compare them normalised (lowercase, letters and digits only) and require equality: word overlap and a search's first hit both pick the wrong episode, and keep a short hand-made list for segments known under two titles. Say which guide the numbering follows, list its gaps, and tell the user which files you used. `loopky doctor` lists the fixed hosts above under `recommended`; when the one you need is blocked, ask the user to allow it, as for the required hosts. If no source is reachable or none matches the dub, stop and ask for the files: a deck built from the wrong subtitle teaches lines the show never says. **Clean the lines before choosing from them.** Drop timing, speaker labels, `[sound cues]`, cues the uploader added (an episode title card, a credit, an advertisement for a website), `♪` song lyrics, the opening and closing theme, and character and place names on their own. Join a sentence split across two subtitle cues. Four traps: - **Many subtitle files are ALL CAPS** (close to half, on one show). Detect it per file and lower-case it, restoring names and "I" when you write the card; anything that finds speaker labels by their capitals, or keeps only lines with lowercase, silently drops those episodes. - **Abbreviations split sentences.** Protect `Mr.`, `Mrs.`, `Dr.` and their kind before splitting on punctuation. - **The opening theme is not always marked with `♪`.** Cut by time: find the theme's first cue and drop everything up to about 35 seconds after it. - **Count the cleaned lines per episode.** A season with a few dozen lines is a broken cleaner, not a quiet season. **Pick what is worth learning, not the transcript.** Every deck is public, so a season's dialogue published in order is the show's script republished. Take each episode's useful words and phrases — the ones a learner needs to follow it and would hear again — and leave the rest. Cards go from the user's language to the one they are learning: the front is the meaning in their language, translated for that scene, and the back is the line or word exactly as the show says it (`--front-lang en-US --back-lang es-MX`). The user recalls the show's words, and Speak and typing grade them. A back may drop a leading filler or name (`Oh,`, `<Name>,`), since what is left is still a piece of the spoken line. Nothing from outside the show: no invented example sentences, no "related" vocabulary, and a word gets a card only in a form the episode uses. **If the user asks for the theme song,** do not card its verses, which republishes the lyrics: card its ordinary single words as vocabulary, with an aside such as `(theme)`. **Order the file by episode, and never repeat.** Cards are studied new-first in file order, so episode 1's cards come first, then episode 2's, and the user meets each episode's language before they watch it. Within an episode, a word before the phrases that use it. A line or word already carded in an earlier episode or an earlier season's deck is not carded again; compare ignoring case, punctuation and `...`. The published decks are the record of what is carded, and `loopky card list <deckId>` prints one card a line, `id<TAB>front<TAB>back` (a picture adds ` [img:…]` to its side), so it covers every season even after your working files are gone. Put the episode on the front as an aside, `I'm ready! (S1E1) → ¡Estoy listo!`: the reader sees where it comes from, and nothing grades it. Publish the first episodes with `deck create`, and add later ones in order with `card add <deckId> --from-file`, which appends. **A whole show is a pipeline: filter, brief, check, then de-duplicate.** 1. **Filter before any model reads anything.** Keep complete sentences of one to seven words, de-duplicated per episode, minus pure interjections and everything already published. That leaves about 100–250 candidates an episode; the full dialogue stays available for context. 2. **One agent per season, in parallel, with a written brief:** what to pick and skip, the exact file format, the per-episode count, whether a back may drop a leading filler, and to report a checker that looks wrong rather than bend a card to fit it. 3. **Give them a checker script, and make "prints OK" the exit condition.** It confirms that every back appears in that episode's dialogue ignoring case and punctuation, the episode aside is well formed, no back holds brackets or slashes, nothing repeats in the season or is already published, and the count is in range, with a lower bound that lets a thin episode come in short rather than padded. This is what makes "nothing from outside the show" enforceable. Test it on lines you know are genuine first: turn newlines and punctuation into a space, never into nothing, or `was...just` glues into one word and a real line fails. 4. **De-duplicate across seasons afterwards, in season order.** Parallel agents cannot see each other's output, so later seasons shrink; with the published backs filtered out in step 1 the repeats are few, without it about a third. Tell the user to expect smaller later seasons. **Pictures from the episode only when their licence allows it, which is rarely.** Stills, frames and screenshots of a commercial show are the studio's copyright, and fan wikis host them as fair use, which the licence rules above exclude; a frame from the user's own copy would be an upload, and Loopky takes only URLs. So an episode picture is limited to shows whose frames are public domain or freely licensed on Wikimedia Commons (some early cartoons). Otherwise picture what a word card names — an object, an animal, a place — from the usual sources, or leave it without one; phrase cards stay bare. Real-life counterparts of the show's world (the animals and objects it is built on) make good covers. Tell the user which it was. To add pictures to cards already published, read `loopky card list <deckId> --json --missing-image` once, match each card on its back text, and send the pictures in one JSONL `card edit --from-file`, each line naming the card's `id` and its `front_image_url`. Add the same URLs to your card file: `card add` tells cards apart by text and picture, so re-running a file without them adds those cards a second time. **Tags and settings.** Add the show's name (lowercase, no spaces, at most 20 characters: `spongebob`), and `tv-series` or `anime`, plus `cartoon` where it is one. A show made for children also gets `kids`. The language pair adds the language tags on its own. Turn on `--listen` and `--speak`, so the user hears and says the lines, and `--type` when they want to spell them; a listening deck for a child who cannot spell yet works best with `--reverse` on and `--type` off. A children's description reads well as a hook line, two lines about the season, then how to study, each on its own line with an emoji. ## Limits worth knowing - The session can write only Loopky's own data (`/pub/loopky/`). It cannot post, follow or edit a profile, and widening that is not an option. - Published decks are public. There are no private decks. - A headless box with nobody at a phone can use `LOOPKY_SESSION`, minted with `loopky login --export` on a machine where the user can approve. It is a bearer token: never echo it, log it or commit it. ## Reporting friction to Loopky Loopky improves from what agents trip over, and only the user can decide to tell the project. So when the work is done, and only if this session hit **real friction in `loopky` or this skill**, ask once whether to open a GitHub issue on `jvsena42/loopky`. Friction is: an error or exit code that misled you, a step here that was wrong or missing, a flag or command you needed and the binary did not have, a workaround you had to invent, or output you could not parse. It is **not** the user's own network allowlist, a session expiring after its hour, a picture source with nothing fitting, or anything the exit-code table already says how to handle. No real friction, no question. 1. **Ask only at the end, and collect nothing until the user says yes.** Never mid-task, not even right after the friction happens: finish what the user asked, verify it, and make this the last thing in your final message. In one short question, name the problem in general words ("`card add` failed on a newline"), say it would become a public issue on `jvsena42/loopky`, and ask whether they want one. Leave the rest for after a yes. Until they say yes, run nothing for it, check no GitHub account, and write no draft. A no, or no answer, ends it for the rest of the session. 2. **After a yes, gather only what reproduces the problem:** `loopky --version`, the OS and architecture, the command's shape with every operand replaced by a placeholder, the exit code and `error.code`, what you expected, what happened, and the workaround if there was one. 3. **Keep the user's data out.** The issue is public, so it never carries card or deck content, titles, descriptions or tags, deck or card ids, public keys, `pubky://` addresses, image or homeserver URLs, file or directory names, user, host or machine names, IP addresses, the `auth_url`, `LOOPKY_SESSION` or any other token, environment variables, or anything the user said about themselves. Describe error messages in your own words rather than pasting them, since they can carry ids and paths. Re-read the draft against this list before showing it. If the problem cannot be explained without one of these, leave it out and say so. 4. **Show the draft, title and body, and file it only after the user approves that text.** If the session has a signed-in GitHub tool (`gh auth status` succeeds, or a GitHub connector is available), use it, searching the repository's open issues first and adding to a matching one rather than opening a duplicate: ```shell gh issue create --repo jvsena42/loopky --title "<title>" --body-file <draft file> ``` The draft file is a temporary one; delete it afterwards. Otherwise, or if they prefer, give them the link to file it themselves, `https://github.com/jvsena42/loopky/issues/new`, with the draft to paste. Issues are public, and are filed from the user's own account. 22:o831,11:[["$","script",null,{"type":"application/ld+json","dangerouslySetInnerHTML":{"__html":"{\"@context\":\"https://schema.org\",\"@type\":\"SoftwareApplication\",\"name\":\"Loopky flashcards\",\"description\":\"Anki-style spaced-repetition flashcards from Claude: build a deck from any topic, import an Anki .apkg or a TSV, add pictures and a language pair for listening and speaking practice, then study it in the free Loopky app on Android and iOS.\",\"applicationCategory\":\"Learning & teaching\",\"operatingSystem\":\"Claude\",\"url\":\"https://agentready.co/connectors/loopky-flashcards\",\"sameAs\":[],\"publisher\":{\"@type\":\"Organization\",\"name\":\"jvsena42\",\"url\":\"https://github.com\"}}"}}],["$","div",null,{"className":"wrap","children":[["$","div",null,{"className":"pp-head","children":[["$","$L23",null,{"name":"Loopky flashcards","url":null,"size":56}],["$","div",null,{"children":[["$","div",null,{"className":"crumbs","children":[["$","$L5",null,{"href":"/","children":"Connectors"}],[" / ",["$","$L5",null,{"href":"/categories/learning","children":"Learning & teaching"}]]]}],["$","h1",null,{"children":["Loopky flashcards",null]}]]}]]}],["$","div",null,{"className":"pp","children":[["$","div",null,{"className":"ca","children":[["$","p",null,{"className":"tag","children":"Anki-style spaced-repetition flashcards from your AI: build a deck from any topic, import an Anki .apkg or a TSV, add pictures and a language pair for listening and speaking practice, then study it in the free Loopky app on Android and iOS."}],null,["$","$L24",null,{"examples":[],"tools":[],"prefix":"","server":null,"instructions":[],"skills":[{"name":"loopky","label":"loopky","gist":"Build and manage Loopky flashcard decks with the `loopky` CLI - make Anki-style spaced-repetition cards from any topic, import an Anki .apkg or a TSV, add, edit or illustrate cards, publish a language","source":"https://github.com/jvsena42/loopky/blob/224c7c8b8b4aafa28b3ccd32b25a2037b21f6125/plugins/loopky/skills/loopky/SKILL.md","raw":"$25"}],"skillNote":"1 in the Claude listing"}],null]}],"$L26"]}]]}]] 22:oa62,1b:[["$","title","0",{"children":"Loopky flashcards by jvsena42: AI connector · Agent Ready"}],["$","meta","1",{"name":"description","content":"Anki-style spaced-repetition flashcards from Claude: build a deck from any topic, import an Anki .apkg or a TSV, add pictures and a language pair for…"}],["$","link","2",{"rel":"manifest","href":"/manifest.webmanifest","crossOrigin":"$undefined"}],["$","link","3",{"rel":"canonical","href":"https://agentready.co/connectors/loopky-flashcards"}],["$","meta","4",{"property":"og:title","content":"Loopky flashcards by jvsena42: AI connector"}],["$","meta","5",{"property":"og:description","content":"Anki-style spaced-repetition flashcards from Claude: build a deck from any topic, import an Anki .apkg or a TSV, add pictures and a language pair for…"}],["$","meta","6",{"property":"og:url","content":"https://agentready.co/connectors/loopky-flashcards"}],["$","meta","7",{"property":"og:site_name","content":"Agent Ready"}],["$","meta","8",{"property":"og:image","content":"https://agentready.co/connectors/loopky-flashcards/opengraph-image?3b61e23efdbb5225"}],["$","meta","9",{"property":"og:image:type","content":"image/png"}],["$","meta","10",{"property":"og:image:width","content":"1200"}],["$","meta","11",{"property":"og:image:height","content":"630"}],["$","meta","12",{"property":"og:image:alt","content":"AI connector on Agent Ready"}],["$","meta","13",{"property":"og:type","content":"website"}],["$","meta","14",{"name":"twitter:card","content":"summary_large_image"}],["$","meta","15",{"name":"twitter:title","content":"Loopky flashcards by jvsena42: AI connector"}],["$","meta","16",{"name":"twitter:description","content":"Anki-style spaced-repetition flashcards from Claude: build a deck from any topic, import an Anki .apkg or a TSV, add pictures and a language pair for…"}],["$","meta","17",{"name":"twitter:image","content":"https://agentready.co/connectors/loopky-flashcards/opengraph-image?3b61e23efdbb5225"}],["$","meta","18",{"name":"twitter:image:alt","content":"AI connector on Agent Ready"}],["$","meta","19",{"name":"twitter:image:type","content":"image/png"}],["$","meta","20",{"name":"twitter:image:width","content":"1200"}],["$","meta","21",{"name":"twitter:image:height","content":"630"}],["$","link","22",{"rel":"icon","href":"/favicon.ico?favicon.3iymezf4ycw3e.ico","sizes":"64x64","type":"image/x-icon"}],["$","link","23",{"rel":"icon","href":"/icon.svg?icon.1m07wgr9jqhm5.svg","sizes":"any","type":"image/svg+xml"}],["$","link","24",{"rel":"apple-touch-icon","href":"/apple-icon.png?apple-icon.3q8qrgufoflqu.png","sizes":"180x180","type":"image/png"}],["$","$L27","25",{}]] 22:o10,1c:null 22:null 22:o22,:HL["/stores/claude.png","image"] 22:o130c,26:["$","aside",null,{"className":"side","children":[["$","div",null,{"className":"card","children":[["$","h2",null,{"children":"Stores"}],["$","div",null,{"className":"st","children":[["$","div","claude",{"style":{"display":"contents"},"children":[["$","span",null,{"className":"s","children":[["$","img",null,{"className":"sm","src":"/stores/claude.png","alt":"","width":16,"height":16}],["$","b",null,{"children":"Claude"}],["$","a",null,{"className":"src","href":"https://github.com/jvsena42/loopky","target":"_blank","rel":"noopener nofollow","children":"Source ↗"}]]}],["$","span",null,{"className":"rk2","children":[["$","small",null,{"children":"Listed, not ranked"}],null]}]]}]]}]]}],["$","div",null,{"className":"card","children":[["$","h2",null,{"children":"Details"}],["$","dl",null,{"className":"kv","children":[[["$","dt",null,{"children":"Company"}],["$","dd",null,{"children":"jvsena42"}]],[["$","dt",null,{"children":"Publisher"}],["$","dd",null,{"children":"Community"}]],["$","dt",null,{"children":"Category"}],["$","dd",null,{"children":["$","$L5",null,{"href":"/categories/learning","children":"Learning & teaching"}]}],[["$","dt",null,{"children":"Audience"}],["$","dd",null,{"children":"For consumers"}]],null,["$","dt",null,{"children":"Sign-in"}],["$","dd",null,{"children":"None needed"}],["$","dt",null,{"children":"Interactive UI"}],["$","dd",null,{"children":"No"}],[["$","dt",null,{"children":"Checked"}],["$","dd",null,{"children":"Oct 27, 2026"}]],null]}]]}],["$","div",null,{"className":"card","children":[["$","h2",null,{"children":["More in ","Learning & teaching"]}],["$","ul",null,{"className":"sim","children":[["$","li","14979",{"children":["$","$L5",null,{"href":"/connectors/ahamotion","prefetch":false,"children":[["$","$L23",null,{"name":"AhaMotion","url":"https://bodgzvrssuydrdmsrqsh.supabase.co/storage/v1/object/public/listing-media/v/ee/ee251ed77c14960827746e164927a4f54438f011dbe9fb6b45a178c9e5651d9f-64.webp","size":24}],["$","b",null,{"children":"AhaMotion"}],["$","small",null,{"children":"#164"}]]}]}],["$","li","4305",{"children":["$","$L5",null,{"href":"/connectors/coursera","prefetch":false,"children":[["$","$L23",null,{"name":"Coursera","url":"https://bodgzvrssuydrdmsrqsh.supabase.co/storage/v1/object/public/listing-media/v/db/dbf38707899973debd8ae7084c4f123c496e92d2aeea05c96f03cb7365fb6bb0-64.webp","size":24}],["$","b",null,{"children":"Coursera"}],["$","small",null,{"children":"#147"}]]}]}],["$","li","4727",{"children":["$","$L5",null,{"href":"/connectors/kahoot","prefetch":false,"children":[["$","$L23",null,{"name":"Kahoot!","url":"https://bodgzvrssuydrdmsrqsh.supabase.co/storage/v1/object/public/listing-media/v/03/034844173668986e8dd3c3df114ea63e9afc07ff90595b86dedf816d462080a3-64.webp","size":24}],["$","b",null,{"children":"Kahoot!"}],["$","small",null,{"children":"#515"}]]}]}],["$","li","14952",{"children":["$","$L5",null,{"href":"/connectors/quizlet","prefetch":false,"children":[["$","$L23",null,{"name":"Quizlet","url":"https://bodgzvrssuydrdmsrqsh.supabase.co/storage/v1/object/public/listing-media/v/b8/b86199a994e55145d0146787685cccb43f5568b2941b84be8549eff8e8f9bc76-64.webp","size":24}],["$","b",null,{"children":"Quizlet"}],["$","small",null,{"children":"#2,339"}]]}]}],["$","li","4317",{"children":["$","$L5",null,{"href":"/connectors/learning-commons","prefetch":false,"children":[["$","$L23",null,{"name":"Learning Commons","url":"https://bodgzvrssuydrdmsrqsh.supabase.co/storage/v1/object/public/listing-media/v/a0/a0b7e829783a839e85fedf28d175a4dffbfceba97791e0ed6446ece36d44da5f-64.webp","size":24}],["$","b",null,{"children":"Learning Commons"}],["$","small",null,{"children":"#161"}]]}]}],["$","li","14993",{"children":["$","$L5",null,{"href":"/connectors/wayground","prefetch":false,"children":[["$","$L23",null,{"name":"Wayground","url":"https://bodgzvrssuydrdmsrqsh.supabase.co/storage/v1/object/public/listing-media/v/44/44081a943fb0498f417826d3431f69e680fc6a61b7b8236ccfd771bb715e09a0-64.webp","size":24}],["$","b",null,{"children":"Wayground"}],["$","small",null,{"children":"#204"}]]}]}],["$","li","15104",{"children":["$","$L5",null,{"href":"/connectors/sketchy-medical","prefetch":false,"children":[["$","$L23",null,{"name":"Sketchy Medical","url":"https://bodgzvrssuydrdmsrqsh.supabase.co/storage/v1/object/public/listing-media/v/24/24a33a07be7c55c7c45bafa8060bf20186e05b2bed57b4f4fef6a6577a51d7a0-64.webp","size":24}],["$","b",null,{"children":"Sketchy Medical"}],["$","small",null,{"children":"#1,492"}]]}]}],["$","li","4325",{"children":["$","$L5",null,{"href":"/connectors/udemy-business","prefetch":false,"children":[["$","$L23",null,{"name":"Udemy Business","url":"https://bodgzvrssuydrdmsrqsh.supabase.co/storage/v1/object/public/listing-media/v/65/6588360147a197fc6b2733bea6df87ef7ad3444e4c58ef1994029dd4666e7f26-64.webp","size":24}],"$L28","$L29"]}]}]]}]]}]]}] 22:o5a,28:["$","b",null,{"children":"Udemy Business"}] 29:["$","small",null,{"children":"#190"}] 22:o11,20:false 1f:7037 22:o17,1e:C 1d:C 1:C 15:C b:C 22:C </article></body></html>

Loopky flashcards

Skills

Loopky flashcards

Skills