Loading...
Loading...
Found 973 Skills
Analyze a batch of functional specs from a ***plain spec file to determine which pairs conflict. Replaces the pair-by-pair `analyze-2-func-specs` flow when a caller wants to check many specs at once (e.g. a new spec against every existing spec, or a freshly inserted batch against itself).
Personal US-equity options trading knowledge base. Use for trade analysis, options strategy recommendations, earnings plays, post-mortems, or ticker mentions in a trading context (e.g., "analyze APP", "sell put on TSLA", "structure for NVDA earnings"). Triggers on multi-leg options (Jade Lizard, bull put spread, iron condor, diagonal, calendar), IV / IV crush, channel checks, earnings positioning, AH action, LEAPS / stock replacement, dealer GEX / gamma exposure / max pain / options chain analysis, or any single-stock options play. Provides concrete strikes, IV-aware structures, and probability -weighted scenarios drawn from 21 trading pitfalls, a gamma framework, and case studies (INTC, Mag-7, APP, NOK, CBRS). Market data via TradingView + Funda AI. Responds in Chinese with English technical terms. **Always sanity-check net vega sign before recommending a directional structure** — wrong vega (credit spread at low IVR, debit spread at high IVR) is a known failure mode; see pitfall 19.
Guides technical support engineering—customer ticket investigation, reproduction, log and API analysis, root-cause isolation, workaround communication, engineering escalation with evidence, and knowledge-base fixes for product bugs and integration issues. Use when debugging a customer-reported issue, writing a repro for engineering, analyzing API errors, drafting technical replies, or improving support runbooks—not for CS program design, renewals, or billing ops (customer-ops-specialist), production incident command (incident-management-engineer), building product features (fullstack-software-engineer), or company-wide crisis statements and launch announcements (communication-lead), or exec/VIP and community escalation program design (community-executive-escalations-program-manager). Product how-to, macros, and ticket triage without deep debugging: product-support-specialist.
Agent-optimized CLI for Bluesky (ATProto) and X (Twitter). YAML in, YAML out, exit codes for automation. Use when the task involves posting, replying, reading feeds, searching, annotating URLs, or running a sync/check/dispatch agent loop across social platforms.
Drive terminal sessions, panes, and TUIs from an agent — spawn shells, send keystrokes, snapshot pixel-perfect PNGs of any pane, and extend shux itself with line-delimited JSON-RPC plugins in any language. Use when you need to multiplex terminal work, drive a TUI you'd otherwise control with tmux / screen / iTerm2 / expect / pexpect / asciinema / vhs / termshot, run scripted CLI/REPL interactions, do headless visual regression on a terminal UI, or write a process plugin that subscribes to the shux event bus and calls back through `window.rename`, `pane.send_keys`, `state.apply`, etc. Trigger phrases include "drive terminal", "spawn pty session", "send keys to a TUI", "screenshot a tui", "snapshot pane", "replace tmux", "iTerm2 automation", "expect script", "headless terminal test", "agent multiplexer", "asciinema record", "write a shux plugin", "extend shux", "shux plugin install".
Convert Markdown articles into inline-style HTML compatible with WeChat Official Accounts. It uses the kami paper-style theme by default, and supports switching between multiple themes including kami, magazine-ink, magazine-indigo, magazine-forest, magazine-kraft, magazine-dune, elegant, modern, and minimal, as well as parameter configurations such as font, font size, accent color, background color, and output path. It is used for official account typesetting, article HTML generation, and replacing unstable external typesetting services, and is especially suitable for converting articles in this vault into a format that can be copied to the WeChat Official Account editor.
Unified Minions skill for both deterministic shell jobs and LLM subagent orchestration. Replaces the older `gbrain-jobs` routing intent. Use when: submitting gbrain jobs, shell/background tasks, spawning subagents, checking progress, steering running work, pausing/resuming, parallel fan-out. One durable, observable, steerable queue interface.
Verify a research claim or academic citation by tracing it through publication → methodology → raw data → independent replication. Routes through perplexity-research for the actual web lookup, then formats results as a citation-checked brain page. Use when a book/article/conversation cites a study and you want to confirm the claim is real, replicated, and accurately characterized.
Fetch official brand/product/tool logos (Stripe, GitHub, Notion, AWS, Figma, etc.) as clean SVGs from SVGL (svgl.app) — as saved .svg files, inline markup, or installed React components. Check this whenever logos or SVGs come up, e.g. adding brand marks to integration/partner rows, footers, pricing tables, or slides; replacing a blurry logo with a vector; getting light/dark variants; or finding an official logo. Prefer it over hand-writing SVG markup or grabbing random files. Skip for generic UI icons, illustrations, charts, favicons from an existing logo, or designing a brand-new custom logo.
Your agent goes blind after send. Sync Smartlead, Instantly, HeyReach, and 5 more sequencers into one local SQLite database your agent can query directly. Every reply, click, bounce, and booking lands on your machine. No CSV exports, no merged sheets, no API round trips.
Publish (with optional images), delete and read your own posts on Bluesky via the AT Protocol (XRPC). Use when the user wants to post to their Bluesky account (text or 带图 / with a picture), cross-post an article as a short dev-focused post, attach an image, delete a post, or list their own recent posts with engagement stats (reposts, likes, replies). Auth uses the user's handle plus an App Password.
Report coding-agent progress, questions, decisions, blockers, tests, PRs, human replies, inbox instructions, and handoffs to the Agora coordination server. Use for every coding task when AGORA_URL is set, especially at session start, before risky or shared edits, when blocked, when asking for human or agent input, after running tests or verification, when opening or updating PRs, when polling for human replies or instructions, and before the final response.