anki-connect_skill

Overview

This skill enables reliable interaction with Anki via the local AnkiConnect HTTP API. It translates user intents into precise AnkiConnect actions, builds JSON requests, runs them against the local server, and interprets responses into clear results. Use it whenever you need to read or modify decks, notes, cards, models, media, or run sync operations.

How this skill works

The skill maps user requests to AnkiConnect actions and assembles JSON payloads with the required action, version (default 6), and params. It verifies AnkiConnect connectivity, calls permissive actions like requestPermission/version, optionally discovers supported actions via apiReflect, then executes read or multi-step write sequences. For any modifying operation on notes, cards, decks, or models it asks the user for confirmation before proceeding, executes the API calls, checks the error field, and returns a concise summary of results or failures.

When to use it

• Listing decks, models, tags, or media files
• Searching for notes/cards and previewing note/card info
• Adding, updating, deleting notes or cards (with confirmation)
• Changing deck assignments, suspending/unsuspending, or rescheduling cards
• Uploading/downloading media or running a sync operation
• Automating bulk workflows using multi to batch actions

Best practices

• Verify Anki is running and AnkiConnect responds at http://127.0.0.1:8765 before making requests
• Use version: 6 and always check the response error field before using result
• Preview with findNotes/findCards and notesInfo/cardsInfo before any destructive change
• Group related modifications into a single confirmation using multi to minimize user prompts
• Use canAddNotes or canAddNotesWithErrorDetail for preflight checks when adding many notes
• Avoid editing a note in the Anki browser while updating it; updates may fail if the note is open

Example use cases

• List all deck names and IDs to display options for a deck-move operation
• Find 125 notes matching a search query, preview their fields, then update a field after user confirmation
• Batch-upload several media files (base64 or URL) and insert notes that reference them
• Suspend or unsuspend a selection of cards after confirming the scope and count
• Run a sync after programmatic changes to ensure collection state is preserved