AniList CLI

CLI for searching, retrieving anime and manga information, interacting with user profile and lists on Anilist, and more.

Security Scan

The skill's requirements and runtime instructions match its stated purpose (a CLI wrapper around AniList), but the npm package has no linked homepage/source in the metadata so verify the package before installing.

Purpose & Capability

Name and description describe an AniList CLI. Declared requirement (node) and the install package (@mtsku/anilist-cli) align with that purpose; the CLI binary anilistcli matches commands listed in SKILL.md.

Instruction Scope

SKILL.md only instructs the agent to check for the binary, optionally run npm install -g, and execute anilistcli commands (search, discover, profile, list management, auth). It does not instruct reading unrelated files or env vars. Note: it recommends a global npm install which modifies system-wide node modules.

Install Mechanism

Install uses npm (package @mtsku/anilist-cli), which is a common and expected mechanism for Node CLIs. However, the skill metadata lists no homepage/source and the registry owner is not human-readable; this reduces traceability and increases risk of installing an untrusted npm package.

Credentials

The skill declares no required environment variables and the SKILL.md references only a token provided via the CLI (anilistcli auth set-token). That is proportional to an API-backed CLI. The SKILL.md does not disclose where the token will be stored (local config file, home directory, etc.), which is an implementation detail worth verifying.

Persistence & Privilege

The skill is not always-enabled and does not request system config paths or other skills' credentials. The main persistent effect is installing a global npm binary and whatever config the CLI writes locally when you run auth set-token.

Assessment

This skill appears coherent for running an AniList CLI, but before installing: 1) check the npm package page (npmjs) and repository for @mtsku/anilist-cli — confirm the maintainer, recent activity, and source code. 2) Prefer installing in a contained environment (container or VM) or install locally rather than globally to limit system impact. 3) Inspect the package source (or its GitHub repo) to see how it stores auth tokens (where it writes config). 4) Only provide your AniList token if you trust the package; if unsure, use public read endpoints without auth or use a known upstream client. If you can't find a trustworthy source for the npm package, treat the install as risky and avoid providing secrets.

AniList CLI Skill

Use this skill for direct AniList CLI workflows. This guide is for LLM/agent execution only.

Installation Check

1. Check availability:
   • command -v anilistcli
2. If missing, install:
   • npm install -g @mtsku/anilist-cli
3. Verify:
   • anilistcli --help

Command Map

• Discovery:
  • anilistcli discover seasonal --season WINTER --year 2026 -n 20
  • anilistcli discover upcoming -n 15
• Airing:
  • anilistcli airing upcoming --hours 48 -n 25
  • anilistcli airing next "<title>"
  • anilistcli airing mine --hours 72 --limit 50
• Search/media:
  • anilistcli search anime "<query>" -n 5
  • anilistcli media recs "<title>" -n 10
  • anilistcli media relations "<anilist-url-or-title>"
• Profile/social:
  • anilistcli profile [username]
  • anilistcli friends [username] -n 50
• List management:
  • anilistcli mine summary --hours 72 -n 10
  • anilistcli list view --type anime --status-in "CURRENT,PLANNING"
  • anilistcli planning add "<title>"
  • anilistcli status set "<title>" CURRENT
  • anilistcli progress set "<title>" 12

Auth Setup

• Set token:
  • anilistcli auth set-token "<token>"
• Verify auth:
  • anilistcli auth where

Output Mode

• Use --json for machine-readable output.
• Public read endpoints work without auth.
• For mutations, run --dry-run first unless explicit write execution is requested.
• Quote title inputs that include spaces.