>_ ankicli

GitHub bundles

Bundled skill guide

This page is the index for the shipped ankicli skill bundles: where they live in GitHub, which harness targets exist, and how to install the same public bundle into a local skill home.

Copy this guide

Paste it into Claude, Codex, or OpenClaw for structured context.

Use the links below when you want the source folder in GitHub, or copy the install commands when you want the local bundle installed.

When to use this

  • You want the GitHub location of the bundled ankicli skill instead of a long explanation of the skill format.
  • You want the install command for Codex, Claude Code, OpenClaw, or a custom skills directory.

What the agent should know

  • The public skill surface is one umbrella skill named `ankicli`, shipped per target under `bundled-skills/<target>/ankicli/`.
  • The top-level `SKILL.md` routes into focused reference files under `references/`; operators do not need to pick separate sub-skills at install time.

Open the bundle in GitHub

If the goal is 'show me the skill,' the GitHub folders are the clearest source. Each target ships the same umbrella skill layout with a top-level `SKILL.md` and a `references/` directory.

These folders are also what ankicli installs locally, so the GitHub tree and the installed copy stay aligned.

  • The GitHub folders are the simplest thing to link from docs because they match what users actually install.
  • The OpenClaw plugin is a separate integration surface, not the source of truth for the standalone public bundle.
Browse all bundled skills See every shipped target bundle. Codex skill folder Open `bundled-skills/codex/ankicli/`. Claude Code skill folder Open `bundled-skills/claude/ankicli/`. OpenClaw skill folder Open `bundled-skills/openclaw/ankicli/`.

Install the same bundle locally

Install the same umbrella skill into the harness you use locally. The install target chooses the destination folder; the skill content stays the same.

Install into Codex home

ankicli skill install --target codex

Install into Claude Code home

ankicli skill install --target claude

Install into OpenClaw home

ankicli skill install --target openclaw

Install everywhere detected

ankicli skill install --target all

Install into a custom path

ankicli skill install --path /path/to/skills

How the bundle is organized

The bundle is intentionally simple: one `SKILL.md` at the top, then a small set of focused references. That makes the docs easier to navigate and keeps install-time choices out of the operator workflow.

SKILL.md

---
name: ankicli
description: Use when an agent needs to inspect, study, create, modify, organize, sync, or troubleshoot an Anki collection through ankicli. Covers setup, study workflows, note authoring, collection and deck management, diagnostics, sync and backups, and goal-driven learning plans.
---

Use ankicli as the local source of truth for Anki operations.

## Core operating rules

1. Confirm runtime, backend, and target readiness first.
2. Prefer `--json` in agent-driven workflows.
3. Prefer read, search, and preview commands before mutation.
4. Use `--dry-run` where supported before real writes.
5. Treat structured ankicli error codes and capability flags as authoritative.
6. Distinguish sync from backup.
7. Prefer saved workspace config for routine use.

## Baseline checks

- `ankicli --json doctor env`
- `ankicli --json doctor backend`
- `ankicli --json profile list`
- `ankicli --json workspace show`

## Read the right reference

- Read `references/setup.md` for install verification, `ankicli configure`, workspaces, auth, and skill installation.
- Read `references/study.md` for tutor-style study sessions, reveal flow, grading, and summaries.
- Read `references/note-authoring.md` for note creation, update, tagging, moving, and media-enrichment workflows.
- Read `references/collection-management.md` for collection inspection, decks, tags, and maintenance-style operations.
- Read `references/diagnostics.md` for runtime, profile, backend, capability, and collection troubleshooting.
- Read `references/sync-and-backups.md` for auth status, sync preflight, backup creation, and restore safety.
- Read `references/learning-plans.md` for travel, anime immersion, exam prep, and time-budgeted study-planning workflows.

Reference files

These are the focused references the umbrella skill points to. Read the one that matches the job instead of dumping every workflow into a prompt.

  • `setup.md`: install verification, configure, workspaces, auth, and skill install
  • `study.md`: tutor-style sessions, reveal flow, grading, summaries
  • `note-authoring.md`: note creation, updates, tags, moves, media workflows
  • `collection-management.md`: decks, tags, collection inspection, maintenance
  • `diagnostics.md`: doctor commands, profile/runtime/backend/capability failures
  • `sync-and-backups.md`: sync preflight, auth, backup and restore safety
  • `learning-plans.md`: travel, anime immersion, exam prep, medical-student workflows

Reference files

references/setup.md
references/study.md
references/note-authoring.md
references/collection-management.md
references/diagnostics.md
references/sync-and-backups.md
references/learning-plans.md

Recommended operator flow

Use the GitHub folder when someone asks where the skill lives. Use the install command when someone wants it in a local skill home. Use the matching docs page when an agent needs task-specific operating context.

That keeps the docs page acting like an index and keeps the bundle itself as the durable source of truth.

Operator verification baseline

ankicli --version
ankicli --json doctor env
ankicli --json doctor backend
ankicli --json profile list