Loading...
Loading...
Found 384 Skills
Manage CompShare GPU cloud resources through the compshare CLI. Use when Codex needs to install or configure compshare-cli, search GPU specifications and inventory, inspect pricing, create or manage instances, connect over SSH, transfer files, run durable remote jobs, manage images, disks, US3, teams or billing, ask product questions, or diagnose CLI problems.
Advanced rendering in Decentraland scenes. Billboard, TextShape, PBR materials, GltfNodeModifiers, and VisibilityComponent. Use when the user wants billboards, floating labels, 3D text, material effects, glow, transparency, or model node control. Do NOT use for screen-space UI (see build-ui) or loading 3D models (see add-3d-models).
Read-only OKX tracking: unified-account equity, perp positions, orders, fills, bills. Use when monitoring OKX without trading (e.g. account equity, current PnL, recent fills, withdrawal history, margin level).
Design, implement, review, and troubleshoot Pakistan 1LINK 1BILL integrations for bill inquiry, bill payment, fixed invoice or voucher collections, variable or top-up payments, credit-card bill payments, packages, payment-status inquiry, voids, PSID or consumer-number flows, reconciliation, and certification. Use when a bank, fintech, government entity, educational institution, utility, biller, or Pakistani business needs to add or repair a 1BILL collection workflow.
Designed for Codex, Claude Code, WorkBuddy, and other Agent Skills clients, it turns one-sentence ideas, story outlines, novels, copywriting, scripts, storyboards, or existing materials into understandable, coherent, publishable AI short dramas and AI short videos. Suitable for landscape or portrait content on platforms like Douyin, Hongguo Short Dramas, WeChat Channels, Kuaishou, Bilibili, YouTube, etc.; supports live-action, independent short films, anthology series, serial dramas, pets, anthropomorphic fantasy, animation/comic dramas, UGC, and brand stories. Used for story diagnosis, screenwriting, storyboarding, character/repeated prop consistency, model routing for Wan 3, Seedance 2.5/2.0/Fast, MiniMax H3, etc., 15–30 second long segments, native dialogue, reference audio, dubbing, paid budget management, continuity editing, physical quality inspection, and cold audience acceptance. It is especially used to avoid fragmented stitching, random cuts, static dialogue, identity/clothing/prop drift, text distortion, incorrect movement directions, mesh penetration, plain observational shots, mismatched lip-sync/voice, music restart, and incomprehensible plots.
A Google Maps API alternative and Google Places API alternative on fetcher.sh — pay-per-call in USDC via x402, or prepaid credits with a Bearer key, no Google Cloud billing account. Use when the user wants to search places by text query or anchor the search to a latitude/longitude coordinate, fetch a place's full details by its feature ID (fid), pull a place's reviews sorted by relevance/newest/rating, or look up a single review by ID. Also covers local business discovery, points-of-interest data, store-locator input, and review monitoring without Google Cloud Platform's API key setup, billing, and per-request pricing.
Your team has high autonomy — and standups are vague, weekly meetings drift into status reports, and 1:1s produce nothing but "I'm fine." This playbook fixes all three layers at once. What's inside: • Daily Standup system — 3-field format, good sample, 4 COO principles to keep it honest • Weekly Meeting — strict 25-min agenda, Scrum Master rotation, 0–10 pulse check • 1:1 Framework — 9-dimension quantified pulse, 5-group deep question bank, bilateral feedback structure • Diagnostic layer — "stuck-at" detection: info / authority / collaboration / capability / direction • FAQ for 4 common failure modes (dead standups, status-report meetings, "I'm fine" 1:1s, scaling beyond 10 people) 🇨🇳 Your team has high autonomy — but standups are getting vague, weekly meetings turn into status reports, and you can't get honest answers in 1:1s. This three-layer Motivation playbook solves exactly this problem: standups are the information layer, weekly meetings are the alignment layer, and 1:1s are the individual layer. When these three things are done right, motivation isn't managed—it grows naturally. 🇯🇵 Your team has high autonomy, yet standups are vague, weekly meetings turn into progress reports, and you only get "I'm fine" in 1on1s — this playbook solves all three layers at once. 🇰🇷 Your team has high autonomy, but standups are vague, weekly meetings turn into progress reports, and you can't get honest feedback in 1:1s — this playbook solves all three layers simultaneously. Triggers: "team motivation" | "no one writes standups" | "weekly meetings turn into status reports" | "can't get honest answers in 1:1s" | "high-autonomy team management" | "how COOs manage teams" | "team motivation" | "standup best practices" | "1on1 framework" | "weekly meeting template" | "team motivation" | "team motivation" | "AI startup team ops" | "remote team alignment" | "engagement decline"
Build, debug, review, and explain integrations with the Listen Notes Podcast API (PodcastAPI.com). Use for podcast or episode search, metadata, recommendations, playlists, transcripts, pagination, authentication, mock-server testing, API usage, caching and attribution rules, pricing, quotas, and billing questions.
Migrate workloads from Google Cloud Platform to AWS — including AI and agentic workloads regardless of cloud provider. Triggers on: migrate from GCP, GCP to AWS, move off Google Cloud, migrate Terraform to AWS, migrate Cloud SQL to RDS, migrate GKE to EKS, migrate Cloud Run to Fargate, migrate App Engine to Elastic Beanstalk, Google Cloud migration, migrate from OpenAI to Bedrock, move off OpenAI, switch from ChatGPT API to AWS, migrate from Gemini to Bedrock, migrate LangChain to Bedrock, migrate LangGraph to AWS, migrate agentic workloads to AWS, move AI workloads to AWS, migrate my AI app to AWS. Runs a 6-phase process: discover GCP resources from Terraform files, app code, or billing exports, clarify migration requirements, design AWS architecture, estimate costs, generate migration artifacts, and collect optional feedback. Clarify must finish before Design, Estimate, or Generate. Includes AI provider migration guidance (for example, OpenAI to Amazon Bedrock) by selecting closest-fit Bedrock model families for required modality, latency/quality targets, context windows, and cost constraints. Model mapping is compatibility-guided, not 1:1 parity; validate prompts, tool-calling behavior, and eval metrics before cutover. Do not use for: Azure or on-premises migrations to AWS, AWS-to-GCP reverse migration, general AWS architecture advice without migration intent, GCP-to-GCP refactoring, or multi-cloud deployments that do not involve migrating off GCP.
Use when a screen, page, deck, doc, README, or component needs visual symbols — icons, glyphs, status markers, step indicators, section-header art, feature-list bullets, or anything replacing emoji/placeholder text with real graphics. Covers one icon or forty, at 16px or 128px. Fetches real icons from Icons8 via MCP and keeps a project on a single coherent family: one pack locked for the whole project, plain metaphors instead of brand logos or literal machinery, free PNG URLs for previewing and prototyping, SVG only for the approved final set. Use it when building or filling in UI (nav, toolbars, cards, tables, checklists, empty states), when making text-only rows or slides read visually, when swapping emoji for icons, when auditing icons already in a file for consistency, or when Icons8 is mentioned. Not for logo design, illustration, CSS/rendering bugs, accessibility labeling, or billing questions.
Analyze CDN domain traffic anomalies using hcloud CLI. Query billing mode and traffic/bandwidth metrics for specified domains, compare against 3-month baseline and absolute thresholds to identify traffic theft or abuse. Use this skill when the user wants to: (1) analyze CDN domain traffic anomalies, (2) check if a domain has traffic theft or abuse, (3) query CDN billing mode and traffic/bandwidth metrics, (4) compare current traffic against historical baseline. Triggers include: CDN流量异常, 流量异常分析, 域名流量分析, 流量盗刷, 带宽异常, 95带宽异常, 流量突增, 流量对比, 基准分析, traffic anomaly, bandwidth anomaly, CDN traffic analysis, traffic theft detection, baseline comparison
Intelligently read any URL content with auto platform detection and fallback strategies. Supports WeChat, Zhihu, Bilibili, Toutiao, Weibo, Xiaohongshu, Douyin, X/Twitter, and generic websites. Trigger words: read url, read link, read this, fetch url, grab content, ink-reader