Loading...
Loading...
Found 9,590 Skills
Run and monitor existing (B2C/demandware/SFCC) jobs using the b2c cli, import/export site archives (IMPEX). Always reference when using the CLI to run jobs, import or export site archives, check job execution status, or trigger search indexing. For creating new jobs, use b2c-custom-job-steps skill instead.
End-to-end workflow for taking a new tool idea from research to working MVP. Use when the user has an idea for a CLI tool, library, or small project and wants to go from concept to initial implementation. Triggers on "I have an idea for a tool", "build a new CLI", "create a new project", "kickoff new tool", "I want to build", "let's build a new", "新しいツールを作りたい", "CLIを作る".
Mine Gmail history into a local flat-file knowledge base (~/.cortex/). Use when asked to "run the cortex", "mine emails", "cortex run", "cortex dry run", "set up the cortex", "cortex from DATE", or "mine my inbox". Extracts contacts, clients, communications and knowledge facts into portable JSONL/JSON files. Requires gws CLI and ANTHROPIC_API_KEY.
Download sales, trends, financial, and analytics reports from App Store Connect using the `asc` CLI tool. Use this skill when: (1) Downloading sales reports: "asc sales-reports download --vendor-number ... --report-type SALES ..." (2) Downloading finance reports: "asc finance-reports download --vendor-number ... --report-type FINANCIAL ..." (3) Analytics reports: "asc analytics-reports request/list/reports/instances/segments" (4) Checking app sales, revenue, downloads, subscriptions, proceeds, or analytics (5) User says "download my sales report", "show sales data", "get financial report", "check my app revenue", "how many downloads", "subscription metrics", "app analytics", "app usage data", "engagement metrics"
Run pre-flight submission checks for an App Store version using the `asc` CLI tool. Use this skill when: (1) Checking if a version is ready to submit to App Store review (2) Diagnosing why a version cannot be submitted (missing build, no pricing, wrong state) (3) Running a CI/CD gate before calling `asc versions submit` (4) User asks "is my version ready?", "check readiness", "why can't I submit?", "run pre-flight checks", "check submission requirements", or any submission-readiness task (5) Building an automated pipeline that conditionally submits based on readiness
Reference for calling the Gemini CLI agent from other agents. ALWAYS read BEFORE invoking Gemini to ensure correct JSON protocol, session management, and subtask delegation patterns.
Control Home Assistant smart home devices, run automations, and receive webhook events. Use when controlling lights, switches, climate, scenes, scripts, or any HA entity. Supports bidirectional communication via REST API (outbound) and webhooks (inbound triggers from HA automations).
Perses project lifecycle management: create, list, switch, and configure projects. Manage RBAC with roles and role bindings per project. Uses MCP tools when available, percli CLI as fallback. Use for "perses project", "create project", "perses rbac", "perses roles", "perses permissions". Do NOT use for dashboard creation (use perses-dashboard-create).
How to use the Paw Mail CLI (paw-mail). Use this skill when: (1) you need to run a CLI command (auth, accounts, emails, sync, threads, config), (2) someone asks how to use or invoke the mail CLI, (3) you need to check CLI flags or subcommands.
Use when a user needs to actually use or build on Zeko: bridge with Bridge CLI or Bridge SDK, get testnet funds, find the right Zeko and Mina endpoints, run GraphQL or curl queries, understand sequencer and archive-node roles, or build zkApps on Zeko with o1js or OCaml. This skill is for public user and builder workflows, especially terminal-driven and non-browser automation flows.
Local-first architecture decision framework for web applications. Covers when to go local-first vs server-based vs hybrid, sync engine selection (ElectricSQL, Zero, PowerSync, Replicache, LiveStore, Triplit), client-side storage options (IndexedDB, OPFS, SQLite WASM, PGlite), and conflict resolution strategies (LWW, CRDTs, server-wins, field-level merge). Use when deciding whether to adopt local-first architecture, choosing a sync engine, selecting client storage, or designing conflict resolution strategies.
Unified CLI entry point for the entire Skill System. One command (sk) to operate all skills, run configurable gate validation, and execute discoverable project scripts via CLI-Anything style scan/run workflows.