Enable reliable interaction with Anki through the AnkiConnect local HTTP API. Use this skill to translate user requests into AnkiConnect actions, craft JSON requests, run them via curl/jq (or equivalent tools), and interpret results safely.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionanki-connectExecute the skills CLI command in your project's root directory to begin installation:
Fetches anki-connect from intellectronica/agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate anki-connect. Access via /anki-connect in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
1
total installs
1
this week
236
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
236
stars
Enable reliable interaction with Anki through the AnkiConnect local HTTP API. Use this skill to translate user requests into AnkiConnect actions, craft JSON requests, run them via curl/jq (or equivalent tools), and interpret results safely.
http://127.0.0.1:8765 (default). Verify readiness using curl, e.g. curl -sS http://127.0.0.1:8765 should return Anki-Connect.CRITICAL — NO EXCEPTIONS
Before any destructive or modifying operation on notes or cards (adding, updating, deleting, rescheduling, suspending, unsuspending, changing deck, or changing fields/tags), request confirmation from the user. Use the AskUserQuestion tool if available; otherwise ask via chat. Only request confirmation once per logical operation, even if it requires multiple API calls (e.g., search + update + verify). Group confirmation by intent and scope (e.g., “Update 125 notes matching query X”).
Treat the following as confirmation-required by default:
addNote, addNotes, updateNoteFields, updateNoteTags, updateNote, updateNoteModel, deleteNotes, removeEmptyNotes, replaceTags, replaceTagsInAllNotes, clearUnusedTags.setEaseFactors, setSpecificValueOfCard, suspend, unsuspend, forgetCards, relearnCards, answerCards, setDueDate, changeDeck.Every request is JSON with:
action: string action nameversion: API version (use 6 unless user specifies otherwise)params: object of parameters (optional)Every response is JSON with:
result: return valueerror: null on success or a string describing the errorAlways check error before using result.
requestPermission first when interacting from a non-trusted origin; it is the only action that accepts any origin.version to ensure compatibility; older versions may omit the error field in responses when version ≤ 4.Prefer jq to build JSON and parse responses. Keep requests explicit and structured.
jq -n --arg action "deckNames" --argjson version 6 '{action:$action, version:$version}' \
| curl -sS http://127.0.0.1:8765 -X POST -H 'Content-Type: application/json' -d @-
jq -n \
--arg action "findNotes" \
--argjson version 6 \
--arg query "deck:French tag:verbs" \
'{action:$action, version:$version, params:{query:$query}}' \
| curl -sS http://127.0.0.1:8765 -X POST -H 'Content-Type: application/json' -d @-
curl -sS http://127.0.0.1:8765 -X POST -H 'Content-Type: application/json' -d @- \
| jq -e 'if .error then halt_error(1) else .result end'
Use multi to reduce round-trips and to group actions under a single confirmation when modifying data.
jq -n --argjson version 6 --arg query "deck:French" \
'{action:"multi", version:$version, params:{actions:[
{action:"findNotes", params:{query:$query}},
{action:"notesInfo", params:{notes:[]}}
]}}' \
| curl -sS http://127.0.0.1:8765 -X POST -H 'Content-Type: application/json' -d @-
Replace the empty array with the result of the previous action when chaining; in CLI usage, split into two calls unless using a scripting language.
requestPermission (safe).version to confirm the API level and use version: 6 in requests.apiReflect with scopes: ["actions"] to list supported actions.findNotes/findCards + notesInfo/cardsInfo for previews before modification.error for each response.deckNamescreateDeckfindNotes, findCardsnotesInfo (note IDs)addNote, addNotescanAddNotes or canAddNotesWithErrorDetail for preflight checks.updateNoteFields, updateNoteTags, or combined updateNotedeleteNotessuspend, unsuspendchangeDecksetDueDatestoreMediaFile, retrieveMediaFile, getMediaFilesNames, getMediaDirPath, deleteMediaFiledata), file path (path), or URL (url) for upload.syncfindNotes/findCards)or, parentheses, and - for NOT logic.deck:Name, tag:tagname, note:ModelName, card:CardName.front:... or other field names to limit by field.re: for regex, w: for word-boundary searches, nc: to ignore accents.is:due, is:new, is:learn, is:review, is:suspended, is:buried to filter card states.prop: searches for properties like interval or due date.getEaseFactorssetEaseFactorssetSpecificValueOfCardsuspendunsuspendsuspendedareSuspendedareDuegetIntervalsfindCardscardsToNotescardsModTimecardsInfoforgetCardsrelearnCardsanswerCardssetDueDatedeckNamesdeckNamesAndIdsgetDeckscreateDeckchangeDeckdeleteDecksgetDeckConfigsaveDeckConfigsetDeckConfigIdcloneDeckConfigIdremoveDeckConfigIdgetDeckStatsguiBrowseguiSelectCardguiSelectedNotesguiAddCardsguiEditNoteguiAddNoteSetDataguiCurrentCardguiStartCardTimerguiShowQuestionguiShowAnswerguiAnswerCardguiUndoguiDeckOverviewguiDeckBrowserguiDeckReviewguiImportFileguiExitAnkiguiCheckDatabaseguiPlayAudiostoreMediaFileretrieveMediaFilegetMediaFilesNamesgetMediaDirPathdeleteMediaFilerequestPermissionversionapiReflectsyncgetProfilesgetActiveProfileloadProfilemultiexportPackageimportPackagereloadCollectionmodelNamesmodelNamesAndIdsfindModelsByIdfindModelsByNamemodelFieldNamesmodelFieldDescriptionsmodelFieldFontsmodelFieldsOnTemplatescreateModelmodelTemplatesmodelStylingupdateModelTemplatesupdateModelStylingfindAndReplaceInModelsmodelTemplateRenamemodelTemplateRepositionmodelTemplateAddmodelTemplateRemovemodelFieldRenamemodelFieldRepositionmodelFieldAddmodelFieldRemovemodelFieldSetFontmodelFieldSetFontSizemodelFieldSetDescriptionaddNoteaddNotescanAddNotescanAddNotesWithErrorDetailupdateNoteFieldsupdateNoteupdateNoteModelupdateNoteTagsgetNoteTagsaddTagsremoveTagsgetTagsclearUnusedTagsreplaceTagsreplaceTagsInAllNotesfindNotesnotesInfonotesModTimedeleteNotesremoveEmptyNotesgetNumCardsReviewedTodaygetNumCardsReviewedByDaygetCollectionStatsHTMLcardReviewsgetReviewsOfCardsgetLatestReviewIDinsertReviewsimportPackage paths are relative to the Anki collection.media folder, not the client.deleteDecks requires cardsToo: true to delete cards along with decks.No bundled scripts or assets are required for this skill.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
We added anki-connect from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in anki-connect — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
anki-connect is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
anki-connect has been reliable in day-to-day use. Documentation quality is above average for community skills.
anki-connect fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for anki-connect matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: anki-connect is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: anki-connect is focused, and the summary matches what you get after install.
We added anki-connect from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
anki-connect reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 39