Loading...
Loading...
Found 10,839 Skills
Collect follower lists from Instagram — follower usernames, profile links, bios. Use when the user wants to map an account's audience or export follower lists for research.
Use when the user asks to "check pacing", "am I over/under-spending", "is this campaign on track to hit budget", or "why did spend spike/stall mid-flight"; returns a spend-vs-target-curve read, learning-phase status, an over/under-delivery call, and a reallocation trigger. Not for initial budget allocation — use budget-optimizer; not for choosing the bid strategy — use bid-strategy-planner; not for the RQS gate — use ad-account-auditor. 付费广告预算节奏监控/跑量过快过慢/在途配速
Use when the user asks to "QA my conversion tracking before launch", "check my UTMs / pixel / event firing", "set up a tracking pre-flight", or "set the dedup rule so Meta and Google stop double-counting"; builds and fixes the measurement plumbing — conversion-event firing, UTM hygiene, cross-platform dedup rules, attribution-window alignment, and offline/iOS-ATT modeled-gap flags — as a pre-flight checklist plus a UTM/event-spec builder. Not for scoring R1/R2 — that is a scored veto in ad-account-auditor; not for account structure — use campaign-architect. 付费广告转化追踪QA/UTM规范/跨平台去重
Identify motif-level structures in a piece of information, expand abstract relationships back into concrete observable phenomena, and then use wind tunnel testing to verify key causal relationships and boundaries. USE WHEN user says 'find structure', 'what is the motif', 'structure wind tunnel', 'underlying structure', 'don’t just do AB testing', or wants to explore the generative mechanism behind a problem. Only expand cross-domain sources or multi-motif combinations when explicitly requested by the user. NOT FOR general summaries, single analogies, factual queries, or execution tasks with a clear unique solution.
Install, audit, repair, and manage a loopback-only CLIProxyAPI bridge that registers subscription-backed Codex, Grok, Antigravity/Gemini, or newly added CLI models in WorkBuddy. Use whenever the user asks to connect a local CLI or agent model to WorkBuddy, install CLIProxyAPI, add or repair a WorkBuddy custom model, preserve image/tool/reasoning/Fast capabilities, onboard another CLI provider, or diagnose a WorkBuddy model that stopped working. This Skill is macOS-first and should be used even when the user names only the model or says their local WorkBuddy API has expired.
Guided journey from a working-but-untested vibe-coded prototype to a production-ready product with tests, clean structure, a business-rules boundary, and resilience at scale. Orchestrates nine skills phase by phase - working-with-legacy-code, clean-code, refactoring-patterns, software-design-philosophy, clean-architecture, pragmatic-programmer, release-it, system-design, ddia-systems - asking the user questions at every decision point and recording results in the project docs/ folder (TESTING.md, TECH-DEBT.md, RELIABILITY.md, IMPROVE-CODE-QUALITY-PLAN.md) so the journey resumes across sessions. Use when the user wants to harden an AI-generated prototype, add tests before refactoring, make code safe to change, or says 'this works on my machine but I am scared to touch it'. For a large aged codebase, use remove-technical-debt; to decide structure before building, use design-code-architecture; for a product and UX pass, use improve-app. For one framework in isolation, invoke that skill directly.
AE Agent system administration CLI for root and agent administrators. Use when the user asks to manage Agent members, sandboxes and shared tools, company model visibility/defaults/pricing, usage statistics and exports, cost quotas, balance alerts, or IM channels. Must use ae-cli system commands, discover real IDs before writes, and never attempt to bypass a permission denial.
Payment center for account funds. Use for: check account balance, recharge / top-up entry. Skip for: usage/billing queries (use qianwen-usage), model tasks.
Lock system architecture for a capability or epic — modules, schemas, public contracts, and proposed slices.
Adapt designs for narrow, medium, wide, embedded, or print web contexts without losing usability, hierarchy, or target sizing. Use when the user mentions responsive design, breakpoints, narrow layouts, viewport changes, touch-capable browsers, or cross-context adaptation.
Query OpenRouter's Benchmarks API for model benchmark rankings and scores. Use when the user asks for benchmark-backed model selection, model rankings by coding/intelligence/agentic ability, Artificial Analysis or Design Arena ELO/win-rate results, benchmark citations, or wants to call GET /api/v1/benchmarks. Also use alongside openrouter-models when the user asks what model should power an app, product, workflow, or use case and benchmark evidence could inform or rule out part of the recommendation, including creative writing, editing, coding, design, agentic, or intelligence-heavy apps. Do not use for OpenRouter usage analytics, billing/spend analysis, generation metadata, provider uptime/latency, generic model pricing/capability lookup without any selection or benchmark-relevance decision, or creating an evaluation suite for a local app.
As a standard S0 pre-skill for larger page workflows like `hiui-page-workflow`, it focuses on requirement refinement for B-end back-office systems and before HiUI page generation. It transforms vague or abstract back-office/management/operation/configuration/approval workflow requirements into executable product solutions, MVP scopes, user flows, business rules, traceable page inventories, product PRDs, global generation contexts, page-level prompts, and HiUI handoff packages. It is suitable for clarifying back-office product ideas, converting rough requirements into PRDs or product solutions, breaking down work surfaces such as lists/details/editing/configuration, defining role permissions/data permissions/state machines/audit rules, and supplementing permission matrices, state transition tables, field dictionaries, exception and audit matrices, batch/import-export specifications, and legacy system transformation and release strategies when needed; it also acts as a B-end product expert to provide judgments including business value decomposition, priority suggestions, solution trade-offs, multi-tenant/version/activation models, master data and system boundaries, anti-pattern identification and risk prompts, continuously turning vague B-end requirements into implementable inputs; when requirements arise in existing projects/repositories, it is also used to perform context-aware requirement refinement combining the current repository's pages, modules, interfaces, types, and documents.