NERYA skills

Skill reference · SKILL.md is the only definition

Every capability
is a skill.

Each skill is a directory: a SKILL.md that says when to use it and how it flows, scripts/ for JSON-in / JSON-out helpers, references/ for lazy-loaded playbooks, and templates/. Viewing a skill unlocks its specialized tools for the rest of the session. These are the 25 that ship today.

0built-in skills
0skill families
0SKILL.md per skill
0runtime frameworks

01 · move the money safely

Trading & strategy

trading

trade · risk · lifecycle

Size positions, place trades, review portfolio state, manage open risk, and move strategies through lifecycle gates.

flow market → portfolio → intent → risk check → approval gate → submit → reconcile

The agent can never switch live trading on by itself. A "go live" request gets an explicit reject and waits for a human operator at the Approval Gate.

strategy_author

strategy · backtest · sdk

Author, validate, refactor, or backtest a full strategy package before proposal promotion.

flow define → scaffold proposal → author files → validate → submit → backtest

backtest

replay · evidence

Replay strategy packages or in-flight proposals over historical candles before promotion.

flow pick strategy / proposal → run preset → report metrics & confidence

triggers

schedule · event · watcher

Create or inspect scheduled tasks, event hooks, condition watchers, price alerts, and route explanations.

flow classify → define target / key / cooldown → dry-run → create → verify

tasks

automation · schedules

Create, schedule, inspect, or manage operator tasks, recurring reports, and non-strategy agent / script jobs.

flow classify → write durable prompt → create_task → deliver via gateway → inspect

02 · know before you act

Market & data

markets

quotes · books · wallets

Current or historical market data, order books, symbol metadata, wallet balances, and on-chain activity reads.

flow normalize VENUE:SYMBOL → read quote / book / candles → check freshness → pass on

market_data_routing

router · sources

Choose symbols, venues, data sources, freshness checks, and fallbacks before research, backtests, or reports.

flow identify asset class → map symbol → check freshness → pick source + fallback

news_social

news · rss

Latest economy / finance / market news and crypto headlines: an RSS first pass before broad web search.

flow RSS pass → respect freshness window → summarise returned items only

research

web · fetch

External info: web search, page fetch, news, social posts, blog content, and current facts outside the workspace.

flow search → fetch full pages → track source / method / time → summarise

analysis

tables · logs · profiling

Local data, logs, tables, databases, charts, profiling, disk inspection, and one-off evidence extraction.

flow classify input → read schema / sample → run narrow script → summarise

03 · build a defensible view

Research & valuation

market_research

coordinator · thesis

Professional market or single-name research combining price, fundamentals, news, sentiment, macro, flows, and risk.

flow gather evidence → load equity / quant / lenses → synthesize thesis, risks, invalidation

quant_research

factors · validation

Factor research, statistical analysis, leakage checks, signal validation, backtest diagnostics, and attribution.

flow hypothesis → clean data → check leakage → measure IC / turnover / drawdown → baseline

equity_research

stocks · memo

Deep research on a US-listed stock: financials, filings, estimates, news, valuation, and memo output.

flow normalize ticker → fetch statements / estimates → load filings + DCF → memo

dcf_valuation

intrinsic value

Intrinsic value, DCF, fair value, valuation sensitivity, and price-target analysis.

flow require fundamentals → choose assumptions → run dcf_calc → sensitivity

sec_filings

10-K · 10-Q · 8-K

List, fetch, and read SEC filing sections: risk factors, MD&A, business, notes, and financial statements.

flow normalize ticker / type → list → read needed section → cite filing / date

research_report

report artifact

Turn gathered evidence into a professional market, stock, sector, strategy, backtest, or flash report.

flow confirm evidence → choose type → structure conclusion / evidence / risks / action

expert_investors

lenses · checklists

Apply named investor lenses, value / growth-quality checklists, macro allocation, and portfolio risk views.

flow start from evidence → select lens → compare emphasis / rejects / monitors

04 · coordinate, remember, grow up

Agents, memory & growth

agents

delegation · workers

Decide whether to keep work local, delegate one bounded subtask, or form a coordinated team.

flow tiny → do locally · independent → spawn worker · 2+ lanes → load team

team

committee · multi-role

An Agent Team, committee, multi-role research pass, or coordinated low-frequency strategy decision.

flow objective / roles / stop → split lanes → run → collect → leader synthesis → verify

memory

recall · durable facts

Remember, recall, audit, or reconstruct durable facts and prior decisions across sessions.

flow write smallest durable fact → search before re-deriving → procedures become skills

evolve

proposals · growth

Proposal-first capability growth: new skills, workflow-to-skill conversion, self-reflection, and config-change proposals.

flow capture workflow → stage proposal → never self-activate

Protected scopes (risk limits, live trading, kill switch, signer / secrets) are never editable.

llm

summarize · translate

A separate one-shot LLM helper that transforms supplied content: summarize, translate, rewrite, label, or draft.

flow define transform → bound IO → pass needed text → check drift → return

05 · extend the runtime

Build & connect

coding

code · shell · source

Workspace code reading, editing, search, shell, focused plans, background processes, verification, and Nerya source changes.

flow read + search patterns → plan if multi-step → edit narrowly → prove → report

browser

DOM · screenshots

Operate, inspect, or verify a live browser session: JavaScript, clicks, forms, screenshots, and console / network evidence.

flow prefer fetch if it proves it → open session → act minimally → verify with DOM / shot

notify

outbound · channels

Send a message out to an operator, channel, webhook, or email, rather than the current chat reply.

flow identify recipient / urgency → ensure channel config (vault refs) → send → status

how a skill is built

Anatomy of a skill

nerya/skills/builtin/<name>/
SKILL.md       frontmatter (name, description, tags) + when to use + flow
scripts/       executable helpers, JSON in, JSON out, sandboxed
references/    lazy-loaded methodology and research playbooks
templates/     code and config templates
Progressive disclosure

Until a skill is viewed, only a small core toolset is advertised (file read / edit / write, shell, search, skill discovery). Viewing a skill unlocks its specialized tools for the rest of the session, so context stays small and permissions stay tight.

Want to see them work together?

The recipes page wires these skills into runnable triggers, SDK scripts, and operator one-liners.