riipandi

Skill for querying App Store prices across global regions, fetching data via appstoreprice.org. Uses Minis built-in browser (minis-browser-use CLI) to directly call the website's native signing functions in page context, no API Key needed, no need to implement signing algorithm. Supports: search apps by name, query prices for a single App across all regions, get cheapest region rankings, paginated app list browsing. Triggers when user mentions "App Store price", "cheapest region", "Turkey price", "appstoreprice", "app comparison", "App Store low-price region", "best subscription region", or any scenario requiring cross-region iOS/macOS App price comparison.

Use the asc (App Store Connect CLI) to manage iOS/macOS apps — TestFlight builds, beta groups, distribution, App Store submissions, release, user reviews, analytics reports, crash logs, and more. Triggers when user mentions "asc", "TestFlight", "beta test", "app store review", "App Store Connect", "release v1.x", "public tester", "add build to test", "check crashes", "what's new", "store listing", "submit to app store review", "approve and release", or any App Store Connect operation.

A skill for reading and writing Bilibili data using Python + UV, powered by bilibili-api-python + aiohttp. Cookies are auto-acquired via browser_use get_cookies for authentication — no manual copying needed. Supports video details / subtitles / AI summaries / comments, user profiles, search, trending / rankings, following feed, favorites, watch later, watch history, interactions (like / coin / triple), dynamic posting and deletion, etc. Trigger when user mentions "Bilibili", "bilibili", "Bilibili video", "Bilibili trending", "bilibili-hub", "get Bilibili data", "Bilibili subtitles", "Bilibili comments", "Bilibili favorites", "Bilibili dynamics", or any scenario requiring programmatic access to Bilibili content.

Use the flarectl CLI tool to manage Cloudflare DNS records, including listing, adding, updating, and deleting DNS records, as well as querying Zone information. Trigger this skill when the user mentions "Cloudflare DNS", "CF DNS", "add DNS record", "delete DNS record", "update DNS", "view DNS records", "cloudflare-dns", "flarectl", or any scenario involving Cloudflare DNS management.

Generate images using OpenAI's Codex backend API with gpt-image-2 tool. Use when the user asks to generate images via Codex, ChatGPT image generation, or gpt-image-2. Triggers on "codex image", "codex generate", "gpt-image", "chatgpt generate image". Token is auto-fetched from chatgpt.com session — no manual token setup needed.

Extract contact info from text, chat history, web pages, screenshots, business card photos, QR codes/OCR results, clean name/phone/email/company/title/address/website, generate vCard/.vcf files, and guide user to import into iOS Contacts or share with others. Trigger words include: extract contact, save to contacts, generate vCard/vcf, business card recognition, add contact from image/screenshot/text, share contact, export contact.

Query DeepSeek API usage (balance, monthly spending, per-model token details, daily breakdown, cache hit rate). Access DeepSeek Open Platform via browser_use, auto-login and export monthly data. Requires user to configure DeepSeek account credentials in local environment variables. Triggered when user says "check usage", "check token consumption", "check spending", "check balance", "how much used today".

Use Doubao speech synthesis (Volcengine TTS) to convert text to audio files. Triggers when user mentions "Doubao TTS", "Doubao speech synthesis", "doubao tts", "Volcengine TTS", "volcengine tts", "speech synthesis", "text to speech", "TTS", "generate audio", "read text aloud", or any scenario requiring Doubao/Volcengine speech synthesis API.

Refresh elph-ai chat model catalogs from models.dev (origin) with optional live provider pricing, inject full thinkingLevelMap on every model, regenerate src/models/catalog.rs, and verify registration. Use when the user runs /update-models, asks to sync or regenerate model catalogs, update models.dev data, refresh pricing, or keep provider model lists current.

Interactively create a new Elph skill (SKILL.md + optional scripts/references). Use when the user wants to create a skill, scaffold a skill, or runs /create-skill.

Run make check/lint/test (cargo fmt/check/clippy/test) and fix failures, then audit changed/related Rust code for memory/resource leaks, deadlock risk, data races, and structural complexity (spaghetti code, god functions/modules, tangled control flow). Also audits Turso/libSQL/SQLite usage for lock contention (SQLITE_BUSY/"database is locked"), WAL/checkpoint misconfig, connection/pool misuse, embedded-replica sync issues, and corruption risk. Use when user asks to verify build quality gates, prep Rust code for merge/release, audit concurrency/memory safety, clean up messy/spaghetti Rust code, or check a Rust service using Turso/libSQL for locking/corruption/sync problems. Consult current Rust docs (rust-lang.org, docs.rs) and lint guidance, plus Turso/libSQL docs (docs.turso.tech) when relevant, to ensure fixes align with active best practices, not deprecated patterns. Flags backward-compat/legacy code and structural refactors found during cleanup and asks the user before removing/restructuring.

Analyze pi → elph porting gaps and Elph-specific implementation differences. Compare upstream pi-ai / pi-agent-core CHANGELOGs and source against elph-ai / elph-agent: (1) what upstream has that elph still lacks, (2) how Elph-only features diverge in design and wiring. Porting doctrine: adopt only true gaps (intent/behavior from pi), implement on Elph architecture — catalogs are models.dev via update-models, never pi seed. Prefer reverse-chronological timeline prose over tables. Persisted docs are always English; in-chat reports follow the user's current language. Use for port gap audit, upstream drift, parity check, Elph extension diff, implementation delta, changelog walk, selisih implementasi, or /pi-port-gap.

Guide terminal UI development with iocraft (components, flex layout, scroll, a11y) and CLI/slash command UX: anstyle coloring, readable structured output, TTY/NO_COLOR rules, and dialog-safe plain text. Use when building or refactoring a TUI, CLI subcommands, slash commands, colored terminal output, fixing scroll/focus/layout bugs, improving keyboard/contrast ergonomics, or the user mentions iocraft, terminal UI, CLI colors, anstyle, command UX, accessibility, a11y, or runs /tui-design.

Probe, test, and document every tool the agent harness has access to (native tools, subagents, connected MCP servers). Use when the user wants to test, audit, or inventory the harness's tool/capability set, or asks "what tools do you have".

Audit a Rust workspace for dependency hygiene: duplicate crate versions across members, unused/dead dependencies, feature-flag bloat, and un-unified workspace dependency tables. Proposes and safely applies fixes (unify to [workspace.dependencies], drop unused deps, trim feature sets), verifying cargo check/clippy/test stay green. Use when user asks to clean up Cargo.toml(s), dedupe dependency versions, find unused crates, unify workspace deps, or audit workspace dependency structure. Does not cover security advisories or license compliance — see rust-dep-audit for that.

Audit a Rust workspace's dependencies for security advisories (RUSTSEC via cargo-audit), license compliance and ban/duplicate policy (cargo-deny), and staleness (cargo-outdated). Proposes a remediation plan classified by risk (patch/minor auto-safe, major flagged), applies safe bumps, and verifies cargo check/clippy/test stay green. Use when user asks to audit dependencies for vulnerabilities/CVEs, check license compliance, find outdated crates, or run a supply-chain/security pass on Cargo dependencies. Does not cover duplicate-version or unused-dependency hygiene — see cargo-workspace-hygiene for that.

Run make check/lint/test (cargo fmt/check/clippy/test) and fix failures, then audit changed/related Rust code for memory/resource leaks, deadlock risk, and data races, applying fixes and performance improvements. Use when user asks to verify build quality gates, prep Rust code for merge/release, or audit concurrency/memory safety in a Rust codebase. Consult current Rust docs (rust-lang.org, docs.rs) and lint guidance to ensure fixes align with active best practices, not deprecated patterns.

Analyze OpenWiki → owly porting gaps and Owly-specific implementation differences. Compare upstream langchain-ai/openwiki CHANGELOG and source against the owly crate: (1) what upstream has that owly still lacks, (2) how Owly-only features diverge (elph-agent runtime, TUI, checkpoint, providers). Prefer reverse-chronological timeline prose over tables. Write all skill output and docs in American English. Use for openwiki port gap audit, owly parity, upstream drift, wiki CLI port, implementation delta, or /openwiki-port-gap.