金融
个人理财、预算与财务工具
qweather
deusyu
天气查询 — 实时天气、天气预报、生活指数、城市搜索。数据源为和风天气 (QWeather)。 触发词: 天气, 气温, 下雨, 预报, weather, forecast, 穿什么, 洗车, 紫外线, UV, 空气, 今天天气, 明天天气, 北京天气, 或任何 "[城市] 天气" 格式的输入。
futures-market-analysis
Lzh-xbccz
"商品期货、贵金属、能源、股指期货八维分析：1-7维先形成主判断，第8维用CZSC缠论确认/冲突/不足；覆盖 CL/BZ/GC/SI/HG/NG/PL/PA/ES/NQ/YM/RTY，并识别 Binance TradFi 商品永续 CLUSDT/BZUSDT/XAUUSDT/XAGUSDT/COPPERUSDT/NATGASUSDT/XPTUSDT/XPDUSDT 的K线、资金费率、OI、多空比。"
kanban-orchestrator
magnusthovsland
Decomposition playbook + anti-temptation rules for an orchestrator profile routing work through Kanban. The "don't do the work yourself" rule and the basic lifecycle are auto-injected into every kanban worker's system prompt; this skill is the deeper playbook when you're specifically playing the orchestrator role.
handoff
ostikwhy-blip
Use when ending or pausing a Claude Code session whose work must continue in a fresh session — user says "create a handoff", "write a handoff", "I'm ending this session", "prepare for a fresh session", "hand this off", or "/handoff" — or when starting a session in a project that already contains a HANDOFF.md at the root ("resume", "pick up where we left off", "continue from the handoff"). Also relevant when a session shows degradation symptoms — Claude contradicted an earlier decision, re-explored something already established, hallucinated file contents, or the user says the session "feels off", "is getting confused", or "context is running low".
diagram
naterminch
Convert long, dense, or complex text into a Mermaid diagram so the idea is seen instead of read. Use when the user asks to visualize, diagram, draw, map, or "show as a diagram", or when a long explanation/process/architecture/relationship would be clearer as a picture. Renders Mermaid to SVG via pele when available.
ctrl-compile
krishanraja
"Compilation owner first: use ctrl-compile, not ctrl-build, to generate or regenerate the machine-readable CTRL import from a completed, frozen human-readable standard. Also use after graded intake to test discrimination, cluster item-level evidence, decide keep/delete/untested, build the subject-owned working profile and honest held-out baseline, or repair a rubric that passes everything. Trigger defensively against permanent-profile inference without grading, held-out tuning, threshold manipulation, erased contradictions, or unnecessary personal data. Do not use to elicit the standard (ctrl-intake), package an already compiled import as platform skills (ctrl-build), review new work (ctrl-check), capture recurring changes (ctrl-capture), or deploy an import. Last reviewed 2026-09-13."
evidence-research
krishanraja
Decision-grade research and due diligence for Krish. Use when asked to investigate, research, compare, verify, diligence, map a market, evaluate evidence, establish current truth, or produce a sourced recommendation; when claims are recent, disputed, niche, costly, or consequential; and when strategy depends on external facts. Do not use for a simple stable fact with one authoritative source or as a substitute for execution. Frame the decision first, prefer primary evidence, preserve contradictions and dates, separate fact from inference, and hand a claim-evidence matrix to strategy and verification.
ctrl-capture
krishanraja
"Turns authorised review, method, routing, freshness, and post-release evidence into versioned change proposals for the named standard owner, then monitors accepted changes through the governed CTRL release chain. Use for weekly or scheduled capture, recurring false positives or uncovered needs, method corrections, under-trigger evidence, possible staleness/retirement, accepted proposal handoffs, and whether deployed changes reduced recurrence. Also trigger to refuse direct live-standard edits, one-example overlearning, raw-ledger runtime use, reused-holdout claims, history deletion, or ownerless automatic changes. Do not use for first-time elicitation (ctrl-intake), compilation (ctrl-compile), packaging (ctrl-build), review (ctrl-check), or installation/release (harness-maintainer). Last reviewed 2026-08-05."
efsr
ssiumha
전자금융감독규정(EFSR) compliance preparation. Use when preparing for electronic financial regulation audit, 조항 조회, 체크리스트 생성, or 이행 계획 수립.
developer-ralph
parsoFish
Launch the Ralph loop runner for a single work item; iterate until quality gates pass, iteration budget is exhausted, or the loop is detected as wedged.
plaid
raintree-technology
Plaid banking API expert for financial data integration. Covers Plaid Link, Auth (account/routing numbers), Transactions, Identity verification, Balance checking, and webhooks. Build fintech apps with bank connections, ACH transfers, and transaction history. Triggers on Plaid, banking API, Plaid Link, bank connection, ACH, financial data, transaction history.
prompt-engineering
CodeAlive-AI
Universal prompt engineering techniques for any LLM. Use when crafting, optimizing, or reviewing prompts for AI models. Triggers on requests like "improve this prompt", "write a system prompt", "optimize my instructions", "help me prompt engineer", "audit this prompt", "review my prompt", or when building agentic systems that need structured prompts.
site-reliability-engineer
nahisaho
Production monitoring, observability, SLO/SLI management, and incident response. Trigger terms: monitoring, observability, SRE, site reliability, alerting, incident response, SLO, SLI, error budget, Prometheus, Grafana, Datadog, New Relic, ELK stack, logs, metrics, traces, on-call, production monitoring, health checks, uptime, availability, dashboards, post-mortem, incident management, runbook. Completes SDD Stage 8 (Monitoring) with comprehensive production observability: - SLI/SLO definitions and tracking - Monitoring stack setup (Prometheus, Grafana, ELK, Datadog, etc.) - Alert rules and notification channels - Incident response runbooks - Observability dashboards (logs, metrics, traces) - Post-mortem templates and analysis - Health check endpoints - Error budget tracking Use when: user needs production monitoring, observability platform, alerting, SLOs, incident response, or post-deployment health tracking.
analyzing-financial-statements
ronnycoding
This skill calculates key financial ratios and metrics from financial statement data for investment analysis
creating-financial-models
ronnycoding
This skill provides an advanced financial modeling suite with DCF analysis, sensitivity testing, Monte Carlo simulations, and scenario planning for investment decisions
cost-optimizer
curiositech
Tracks cumulative LLM costs across DAG execution and makes real-time decisions to stay within budget. Downgrades models, skips optional nodes, or stops early when cost exceeds thresholds. Use when managing execution budgets, analyzing cost breakdowns, or optimizing model routing for cost. Activate on "cost budget", "too expensive", "reduce cost", "cost optimization", "model downgrade", "budget exceeded". NOT for LLM model selection logic (use llm-router), pricing comparisons across providers, or billing/invoicing.
always-on-agent-safety
curiositech
Safety, privacy, cost management, and frank advice for building always-on AI agents with episodic memory. Covers data hygiene, privacy risk surfaces, runaway cost prevention, scope creep, psychological effects of persistent AI companions, and responsible deployment patterns. This is the skill that tells you what can go wrong and how to prevent it. Activate on: "agent safety", "always-on agent privacy", "agent cost control", "persistent agent risks", "AI companion safety", "agent data hygiene", "runaway agent costs", "parasocial AI risk", "/always-on-agent-safety". NOT for: architecture design (use always-on-agent-architecture), input design (use always-on-agent-inputs), application brainstorming (use always-on-agent-applications), healthcare compliance specifically (use hipaa-compliance).
setup-specialists
xtrm-dev
First-run setup workflow for a Specialists install. Use when the user says "setup specialists", "configure specialists", "change the specialist models", "models shipped do not exist on my machine", "set notes_mode globally", "opt out of GitNexus for one specialist", "sp init --global", "sp edit --global", or asks how to apply specialist overrides across all repos at once. Verifies local Pi models, explains the 3-layer field merge (package canonical → ~/.config/specialists/user.json → .specialists/user), bootstraps the global user.json via sp init --global, applies model + behavior overrides via sp edit --global, and validates with sp doctor --specialists.
agent-context-partitioner
curiositech
Algorithmic skill for designing evidence-backed partitions of LLM context or task DAGs across K agents. Covers two modes: (A) online/reactive spawning under context pressure, and (B) static pre-planned DAG execution with graph min-cut optimization. Encodes algorithms for sequence-stable clustering, dynamic K selection, token-budget-aware partitioning, and handoff protocol design. Use when designing multi-agent systems, deciding when and how many agents to spawn, or optimizing a task DAG for token efficiency. NOT for one bounded task that does not benefit from parallelism, runtime scheduling or authorization policy, or comparing vectors whose embedding-space identities are unknown or incompatible.
net-payments
ai-2070
"Use this skill when the user is integrating the Net Payments SDK (net-payments Rust crate, net_payments lib, or the Python/Node CapabilityGateway + PaymentProvider payment surface) — x402-native payments for the Net mesh. Covers pricing a capability at discovery (net.pricing.terms@1), issuing signed quotes (net.payment.quote@1), the provider lifecycle engine (PaymentEngine: quote → verify → settle → tiered verification → billing), the caller flow (CallerPaymentFlow / ProviderChannel: pricing → spend policy → payload → pay), paid agent-to-agent tasks (prepare → purchase → submit: serve_a2a_configured, redeem_for_task on a reservation-bound quote, A2aCallerFlow + a durable A2aPurchaseStore), facilitators (mock + the real HTTP verify/settle client, config packs, auth), tiered verification (observed confirmed(n) final) with the independent on-chain ChainChecker, reorg handling, the settlement signer seam (SchemeSigner / ExternalSigner / ExternalSvmSigner / ExternalXrplSigner — EIP-3009 exact-EVM, SPL exact-SVM, exact-XRPL; keys never cross the boundary), the spend policy engine (budgets, delegation inheritance, requires_payment_approval), immutable billing events + the billing stream, network enablement (CAIP-2/CAIP-19, the signed asset registry, Base/Solana/xrpl config-not-code ladder), the outbound HTTP 402 two-way door, the failure schematic (net.payment.failure@1) that rides denials beside the human error, the multi-language SDK surfaces (Python AND Node/TS at full demand+supply parity with Rust — CapabilityGateway, paid PaymentProvider + buildPricingTerms, HTTP-402 client, eip155/svm/xrpl signers, approval verbs, free publishTools; paid A2A is Rust + Python only), and cross-language golden vectors + conformance. Triggers on imports of net-payments / net_payments; on x402, PaymentEngine, PaymentQuote, PricingTerms, net.payment. / net.billing. / net.settlement.*, X402Carry, VerificationTier, confirmed(n), reorg, SchemeSigner, ExternalSigner, ExternalSvmSigner, SvmTransferIntent, SPL/Solana settlement, SpendPolicyEngine, BillingEvent, MeshPaymentChannel, serve_payments, serve_a2a_configured, redeem_for_task, A2aCallerFlow, prepare_task/purchase_task/submit_task, gated_invoke, requires_payment_approval, CAIP-2/CAIP-19, HttpFacilitator, EIP-3009, HTTP 402; and on phrases like 'price a capability', 'charge for a tool', 'charge for an agent task', 'sell bounded work to another agent', 'paid A2A', 'pay to invoke', 'settle on Base/Solana', 'verify a payment on-chain', 'spend limit / budget', 'approve a payment', 'pay an x402 API'. Net signs the commercial facts around invocation; it does NOT custody funds, process payments, issue invoices, or move money. Skip for unrelated event-bus / mesh work (the net-event-bus skill) or for editing payments' own internals unless the task is payments integration."
closed-form-marbling-renderer
curiositech
Render mathematically-faithful Turkish marbling (Ebru) and paper-marbling with closed-form coordinate-deformation maps — a drop is a radial outward push, a comb/tine is a decaying shear, all composed as homeomorphisms over colored region boundaries. No fluid solver, runs 60fps on a 2D canvas. Use when building a marbling/Ebru toy or generative-art renderer, implementing drop/comb/wave/swirl deformations, scripting traditional patterns (Battal, Gel-Git, Şal, Bülbül Yuvası), keeping combed edges crisp via adaptive resampling, modeling ox-gall shouldering for crisp ring-in-ring drops, or exporting high-DPI marbled prints. NOT for real fluid / Navier-Stokes simulation, metaball / alpha-blended "smoke" blob effects, raster image-processing filters, or non-marbling generative art.
cost-accrual-tracker
curiositech
Track real-time API cost accrual during LLM execution. Activate on 'cost tracking', 'token usage', 'API costs', 'budget monitoring', 'usage metrics'. NOT for cost estimation, pricing tiers, or billing systems.
agentic-patterns
curiositech
Fundamental patterns for effective agentic behavior. Teaches decomposition, tool orchestration, error recovery, context management, quality self-assessment, and knowing when to stop. Model-agnostic principles that make any agent more effective regardless of domain. Activate on: "how should I structure this agent", "agentic workflow", "agent patterns", "multi-step task", "tool orchestration", "/agentic-patterns", "decompose this", "agent best practices", "chain of actions", "when should the agent stop", "agent loop design". NOT for: creating agent infrastructure (use agent-creator), building DAGs (use jury_rig-architect), specific tool implementation.
bellifemine-2007-jade-fipa
curiositech
JADE platform for building FIPA-compliant multi-agent systems with standardized agent communication