artherahq
OrganizationReusable Agent Skills for quantitative finance research, extracted from the Aria toolchain.
Categories
Indexed Skills (20)
ai-generated-ui-craft
The generation-time discipline for an AI producing UI code — not a UI category (see `terminal-software-design` for dashboards, `conversational-ui-restraint` for chat) but the self-critique process that separates a considered design from a templated one. Trigger for "this looks AI-generated", "make this feel less generic/templated", "why does every AI-built page look the same", "make this look considered/deliberate", or — proactively — before finalizing any UI generation task, as a self-check pass. Trigger regardless of which UI category skill was also used; this is orthogonal to both. Portable: self-contained prose, no script dependency.
conversational-ui-restraint
Build or review a chat/copilot/assistant interface — message list, composer, streaming responses, conversation sidebar, canvas/side-panel for structured output. Trigger for "make this chat UI look like ChatGPT/Claude", "为什么我的 对话界面看起来很乱", "streaming response feels janky", "conversation sidebar needs work", "this looks AI-generated", or when reviewing a chat/assistant screen before shipping it. This is a DIFFERENT problem than dense dashboards — a chat UI's job is to get out of the way of the content, not to show more data per screen (use `terminal-software-design` for tables/dashboards/data grids, not this). Do NOT trigger to invent a generic app aesthetic from a blank slate (use `ui-ux-pro-max`) or for landing pages. Portable: self-contained prose, no script dependency — works pasted into any assistant.
operator-revenue-integrity
Verify an operator's or tenant's self-reported revenue before it is used to settle a revenue-share, guarantee, or performance clause. Trigger for "核实流水", "商户流水是不是真的", "这个月分账对不对", "怀疑商户漏报流水", "能耗和流水对不上", "verify operator revenue", "tenant underreporting sales", "revenue share settlement check", or whenever a payout depends on a number the counterparty reported themselves. Do NOT trigger for public-market or securities analysis — declared-revenue verification for a private operator is a different problem from equity research (use `equity-research-report`), and this skill has no opinion on whether a business is a good investment, only on whether the number it reported is supportable.
terminal-software-design
Build or review UI for a terminal, IDE, trading/data dashboard, admin/ops tool, or any dense data-driven desktop/web app — as opposed to a marketing site or landing page. Trigger for "review my sidebar", "why does this look unfinished", "dashboard feels too sparse/too dense", "Electron window has a weird line at the edge", "make this table easier to scan", "这个侧边栏要怎么改", "为什么这个终端界面看起来不对", or when reviewing a finished screen/component in one of these product categories before shipping it. Portable: every reference file here is self-contained prose with no script dependency — it works pasted as instructions into any assistant, not only inside this harness. Do NOT trigger to invent a generic app aesthetic from a blank slate (use `ui-ux-pro-max`), to match one specific reference product's own conventions like TradingView/X/Trading212 (use `trading-ui-patterns`), or to freeze the user's own palette/spacing into reusable tokens (use `ui-design-system`) — this skill is the density/composition/native-chrome discipline
trading-ui-patterns
Build or review a trading/investing-app component against the specific conventions of X (timeline post, action bar), TradingView (watchlist row, technical rating gauge), or Trading212 (order ticket, holdings row). Trigger for "make this look like TradingView/X/Trading212", "watchlist row like TradingView", "order ticket like Trading212", "technical rating gauge", "做一个像 TradingView 一样的自选股列表", "参考 X 的帖子卡片样式", or when reviewing a finished component against one of these reference patterns before shipping it. Also trigger when a watchlist/quote/holdings component needs to render more than one market's data (e.g. both US and CN symbols) — this is where the direction-color convention silently breaks. Do NOT trigger to invent a generic app aesthetic from a blank slate (use `ui-ux-pro-max` for open-ended style exploration) or to freeze the user's own palette/spacing choices into reusable tokens (that's `ui-design-system`) — this skill is specifically about matching one of these three products' own component convention
minimal-editorial-exports
An alternate visual style for aria-code's own generated exports — report covers, PPTX title slides, single-chart share images, Canva one-pagers — built on heavy negative space, one accent color, and restrained serif/monospace type, instead of the default dense institutional/dashboard look. Trigger for "极简", "杂志风", "editorial", "zine", "less corporate", "make the cover page quieter", "one number, lots of white space", or when the user wants a report/deck/chart export that reads as considered rather than templated-dashboard. Do NOT trigger for the default financial report body (tables, indicators, full analysis) — this governs cover pages, title slides, and single-focal-point exports only, never dense data views (use `terminal-software-design` or the existing institutional/bloomberg themes for those). Do NOT trigger to invent a generic aesthetic from nothing — use `ui-ux-pro-max` for open-ended exploration instead.
minimal-editorial-poster
Compile a minimal editorial/zine-poster prompt for a theme, sentence, mood, or brief from ANY domain aria-code touches — a financial story, a real-estate listing highlight, a sports recap, a general subject — not tied to financial-report styling. Trigger for "做一张极简海报", "zine风格的海报", "minimal poster for [subject]", "给这个故事配一张海报", or when the user wants a standalone poster-style creative asset rather than a data export. Produces a ready-to-use image-generation prompt and, when an image backend is configured, actually executes it via aria.report.generate_image_local / edit_image_local (self-hosted, no API key) or the OpenAI-backed equivalents — falls back to prompt-only + a non-image brief when neither is available. Do NOT trigger for styling aria-code's own report/PPTX/Canva exports (use `minimal-editorial-exports` for that — this skill is for a standalone poster from a theme, not a data-export cover).
industry-design-direction
Pick a concrete visual direction for a website or app in a specific industry — which aesthetic, which palette, which font pairing, which page structure — from a library of 95 industry profiles, 57 defined styles, 96 palettes, 57 font pairings, and 30 landing structures. Trigger for "design a landing page for a dental clinic", "帮我设计一个餐厅网站", "what should a fintech app look like", "给这个 SaaS 产品定一套 配色和字体", "我要做一个电商网站，用什么风格", or whenever someone needs a starting direction for a product whose industry is known but whose look is not. Do NOT trigger once a direction already exists and the job is enforcing it across screens (use `ui-design-system` — that skill operationalizes a chosen aesthetic into tokens; this one chooses it). Do NOT trigger for dense dashboards/terminals (`terminal-software-design`), chat interfaces (`conversational-ui-restraint`), or trading-app components (`trading-ui-patterns`) — those are category skills with far more depth for their category than the one-line profile here. Portable: every refer
ui-asset-sourcing
Source the actual assets a website or app needs — icons, imagery, logos, avatars, empty-state art — without hallucinating SVG paths, shipping emoji as icons, or dropping in stock photos that fight the palette. Trigger for "what icons should I use", "给这个网站配图", "add icons to this UI", "generate a hero image for this landing page", "这个空状态要放什么插图", "need a logo for this brand", or whenever a design direction exists and the remaining gap is the visual material to fill it. Names which icon set fits which aesthetic, how to fetch real icon and brand SVGs rather than inventing path data, and how to generate on-palette imagery with Aria Code's own image tools (`aria.report.generate_image_local` free/local, or `aria.report.generate_image` paid) when a stock photo would be wrong. Do NOT trigger to choose the design direction itself (use `industry-design-direction`) or to compile a single editorial poster (`minimal-editorial-poster`). Portable: self-contained prose, no script dependency.
short-form-video-editing
Turn approved footage, posters, charts, and image assets into a platform-ready short-form video package: edit plan, captions, publish copy, and delivery manifest. Use when creating social clips, product explainers, market recaps, or finance videos that need platform specifications, asset provenance, subtitle, and release checks.
backtest-validation
Validate whether a backtest result is trustworthy before drawing any conclusion from it. Trigger for "回测这个策略", "这个策略过拟合吗", "夏普这么高可信吗", "加上手续费还赚钱吗", "样本外表现", "validate this backtest", "is this strategy overfit", or whenever the user (1) presents or produces backtest results and wants a judgement, (2) asks whether an edge is real, (3) compares strategy variants and picks the best one, or (4) is about to deploy/paper-trade a strategy based on historical performance. Fire even when the user only asks for the metrics ("just show me the Sharpe") — the metrics are not a conclusion until the gauntlet passes. Pair with point-in-time-research: that skill guards the data going in; this one guards the claim coming out. Do NOT trigger for pure data fetching or for live trading questions with no historical simulation involved.
equity-research-report
Produce comprehensive, evidence-backed public-equity research reports with market, filing, fundamental, valuation, technical, risk, catalyst, scenario, and source analysis. Use when the user asks for "全面分析报告", "股票研报", "深度分析公司", "完整个股分析", "comprehensive equity report", or requests analysis of a stock, company, or equity thesis with current auditable data.
execution-position
Convert a trading signal into a sized, risk-gated PAPER order intent — or a refusal with reasons. Trigger for "这个信号该买多少", "帮我算仓位", "凯利公式下注多少", "现在要不要加仓", "position sizing", "how much should I buy", "simulate this trade", or whenever the user (1) has a signal/decision and asks for the size, (2) wants a trade checked against limits before acting, (3) asks about stops or exposure, or (4) another skill hands over a strategy/rebalance that needs execution shape. Fire even for casual "梭哈吗". Do NOT trigger for portfolio-wide weight construction (portfolio-optimization) or post-hoc risk analysis (risk-assessment). NEVER place live orders.
factor-research
Evaluate whether a cross-sectional factor genuinely predicts returns. Trigger for "这个因子有效吗", "算一下IC", "动量因子在A股还有效吗", "帮我评估这个选股信号", "factor IC", "is this signal predictive", "compare momentum vs value factors", or whenever the user (1) proposes or computes a ranking/score across assets and asks if it works, (2) asks which factor explains recent moves, (3) wants factors screened/ranked before building a strategy, or (4) hands a signal to strategy construction. Fire even for informal phrasing ("这个指标选股靠谱吗"). Do NOT trigger for single-asset technical indicator questions (no cross-section) or for validating a finished strategy's returns (that is backtest-validation).
multiple-testing-correction
Correct for multiple hypothesis testing before calling any factor, sub-period, or parameter sweep "significant" — and check whether a claimed set of "independent" signals or bets is actually a smaller number of correlated ones wearing a disguise. Trigger for "测了8个因子哪个显著", "筛选因子", "factor screen", "parameter sweep", "which of these signals is real", "p-hacking", "data snooping", "统计显著性", "breadth", "多重检验", "这些信号真的独立吗", or whenever the user has run more than one significance test in a batch and is about to act on which ones "passed." Also trigger when a Sharpe/IR target is being justified by citing a number of "independent" bets, signals, or symbols — that count needs a correlation check before it goes into any Information Ratio math. Pair with backtest-validation: that skill's Deflated Sharpe Ratio is this same correction applied to the single case of "best strategy variant out of N backtested"; this skill is the general case for any batch of hypothesis tests, plus the separate breadth-illusion check neither s
point-in-time-research
Enforce point-in-time data discipline for any quant research task. Trigger for requests such as "回测策略", "因子IC", "检查前视偏差", "量化选股", "验证夏普比率", or "point-in-time backtest". Also trigger this skill whenever the user: (1) backtests a strategy or factor, (2) asks for a Sharpe / alpha / IC / return — even as a quick one-liner ("just give me the Sharpe", "run this backtest"), (3) reviews or asks you to confirm / audit / validate quant or backtest code ("is my code PIT clean?", "confirm this is correct", "check my backtest for look-ahead"), (4) evaluates whether a signal or edge is real, or (5) screens on fundamentals. Fire even when the user claims they already fixed PIT issues — check specifically for whichever of the three silent leaks (period-end dating, latest-value overwrite, same-session execution) may remain. Do NOT trigger for generic finance questions that involve no simulation or data join.
strategy-generation
Turn a natural-language trading idea into a disciplined, testable strategy spec and implementation. Trigger for "帮我生成一个动量策略", "写一个BTC均值 回归策略", "设��多因子选股", "做一个ETF轮动", "generate a momentum strategy", "build me a trading strategy", "turn this idea into code", or whenever the user (1) describes a trading idea and wants it made concrete, (2) asks for strategy code, (3) wants strategy variants compared, or (4) asks to improve an existing strategy. Fire even for vague asks ("有什么好策略推荐吗" — the answer is a disciplined spec, not a tip). Do NOT trigger for validating an already-backtested result (backtest-validation) or for pure factor evaluation (factor-research).
ui-design-system
Help the user build and enforce *their own* design system — capture their brand/aesthetic decisions into a portable design-tokens.json, then keep every UI they generate consistent with it. Trigger for "帮我建立设计系统", "把我的品牌色定成规范", "make my UI consistent", "set up design tokens", "check this screen matches my design system", "为我的 app 定一套配色和圆角规范", "review my components against my tokens", or whenever the user is building UI and wants coherence across screens rather than one-off styling. Do NOT trigger to invent an aesthetic from a blank slate with no user input (ask them, or use ui-ux-pro-max for exploration first) — this skill operationalizes the user's OWN choices, it does not impose a house style. Works across targets (CSS/Tailwind, SwiftUI, React Native, Flutter) because tokens are platform-neutral.
gamma-exposure
Compute or review a Gamma Exposure (GEX) / dealer-hedging-behavior estimate from options open interest before it gets reported as if it were an observed fact. Trigger for "GEX", "gamma exposure", "gamma squeeze", "gamma wall", "zero gamma flip", "dealer positioning", "做市商对冲", "伽马敞口", "波动率压制/放大", "0DTE flows", "净伽马", or whenever the user is inferring options-dealer hedging pressure from open interest and implied volatility, building a GEX chart/panel, or about to state a GEX regime call ("dealers are long/short gamma at X") as if it were measured rather than estimated under an assumption. Also trigger when reviewing GEX-computation code for a silent sign or scaling bug — the failure mode this skill exists to catch produces a plausible-looking wrong answer, not a crash. Do NOT trigger for a plain options-chain display (bid/ask/volume/greeks per contract, no hedging inference) or for risk exposure of options the user actually holds — that is `risk-assessment`.
your-skill-name
Replace this with one or two sentences that say exactly when to trigger the skill, in the words a user would actually use. Name the concrete situations. Add a "Do NOT trigger for …" clause if the skill is easy to over-fire. This field is the only thing the model sees when deciding whether to load the skill.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.