Results for “status”

Control LG smart appliances via ThinQ API. Use when user asks about their fridge, washer, dryer, AC, or other LG appliances. Supports checking status, changing temperature, toggling modes (express, eco), and monitoring door status.

Defines RESTful API design conventions including URL structure, status codes, error formats, pagination, versioning, rate limiting, CORS, validation, and OpenAPI documentation.

List recent Stripe charges with amount, status, and customer

Design consistent, developer-friendly REST APIs with conventions for resource naming, HTTP methods, status codes, pagination, filtering, error responses, versioning, and rate limiting.

xurl CLI for authenticated X posts, replies, reads/search, DMs, media upload, followers, auth status, or raw v2 API calls.

REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.

REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.

REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.

REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.

REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.

REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.

Mirror issues and status across issue trackers with stable external-ID mapping to avoid duplicates. Load when syncing GitHub and Linear issues, mirroring ticket status, or keeping two trackers in sync. Also triggers on "issue sync", "sync issues", "mirror issues to", "keep Linear and GitHub in sync", or bidirectional issue tracker updates. Requires API access on both sides — stops if credentials missing.

Interact with GitHub using the `gh` CLI to check PR status, manage issues, review code, and query the API.

Publishing and scheduling blog posts on self-hosted or WordPress.com sites via the WP REST API — drafts, media upload, categories/tags, and status=future scheduled publishing using Application Passwords.

Manages Xiaohongshu (Little Red Book) login state via a CLI script, supporting QR code and phone verification code login, logout, and status checks.

Provides a comprehensive checklist for designing REST and GraphQL APIs, covering resource design, HTTP methods, status codes, pagination, security, performance, and documentation.

Manage n8n workflows and automations via API. Use when working with n8n workflows, executions, or automation tasks - listing workflows, activating/deactivating, checking execution status, manually triggering workflows, or debugging automation issues.

Retrieves Jira tickets, analyzes requirements, updates ticket status, adds comments, and transitions issues via MCP or direct REST API.

Manages Xiaohongshu (Little Red Book) login authentication by checking login status, logging in via QR code or phone verification code, and logging out.

Query free LLM APIs from OpenRouter, Groq, Cerebras, Google AI, and Mistral, with commands to compare models and check status.

Automate AI video generation workflows: browse avatars and templates, generate personalized videos, track processing status, and retrieve shareable URLs via the Composio MCP integration.

Generate personalized status briefings on demand. Pulls from your configured data sources (GitHub, email, Teams, Slack, and more), synthesizes across them, and drafts updates in your own communication style for any audience you define.

Trigger: empty list state, loader skeleton, error boundary layout, offline indicator, system fallback UI. Scope: UI fallback layouts, skeleton placeholders, client recovery views. Boundary: Excludes server-side API error status coding.

Full pull request lifecycle — create branches, commit changes, open PRs, monitor CI status, auto-fix failures, and merge. Works with gh CLI or falls back to git + GitHub REST API via curl.

Queries live GPU inventory, submits authenticated fixed-rate RFQs, and checks status via the canonical Itô compute CLI or MCP server, with gated node qualification.

Submits, retrieves, and manages headless B2C Commerce storefront orders via SCAPI ShopAPI Orders or legacy OCAPI, including SLAS authentication, order amendment, status retrieval, and notifications.

Access blockchain RPC endpoints via Quicknode to read onchain data including balances, token prices, transaction status, gas estimates, and block data across Base, Ethereum, Polygon, Solana, and Unichain. Supports both API key and x402 wallet-based pay-per-request access.

Send notifications to Feishu/Lark. Internal utility used by other skills, or manually via /feishu-notify. Supports push-only (webhook) and interactive (bidirectional) modes. Use when user says "发飞书", "notify feishu", or other skills need to send status updates.

Search, explore, and run fal.ai generative AI models for image, video, audio, and 3D generation, including schema lookup, job submission, status polling, result retrieval, and file uploads.

Interact with GitHub via the `gh` CLI. Use for issues (read, comment, file), pull requests (view, comment, check CI status), workflow runs, and `gh api` for queries the subcommands don't cover. Authentication is via the bot's GITHUB_TOKEN (already wired through `gh auth setup-git` at container start).