'rollup' 검색 결과

Analyze an organization's sub-transaction patterns in TRES Finance, identify groups of repetitive transactions, and propose data-driven rollup rules that consolidate them into one aggregated entry per interval (daily or monthly) for cleaner ERP integration. Also lists and deletes rollup rules. Trigger this skill whenever the user asks about rollup rules, transaction aggregation, consolidating transactions, reducing transaction noise, rolling up gas fees, rolling up staking rewards, rolling up micro-transactions, or collapsing many small ledger entries into fewer summary entries. Also trigger on "create a rollup rule", "suggest rollup rules", "what should I roll up", "show my rollup rules", "delete a rollup rule", "aggregate transactions", "too many transactions", "reduce transaction count", "roll up fees", "daily rollup", "monthly rollup". If a wallet has too many transactions, high-frequency activity, or noisy ledger entries, proactively suggest rollup rules. For computing the EXACT impact of a single already-specified rule or reviewing submitted/pending rules, use the tres-rollup-review skill instead.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Compute the EXACT sub-transaction impact of a rollup rule in TRES Finance — every filter applied — and flag genuine problems (zero matches, overlap, config mistakes) before the rule is created. Two modes. Mode A: a pre-create quality gate invoked by the tres-rollup-rules skill to vet proposed candidate rules. Mode B: standalone review of a rule someone submitted or of existing PENDING rules. Trigger this skill when the user says "review this rollup rule", "what would this rollup rule actually match", "preview the rollup impact", "how many transactions would this rule catch", "is this rollup rule valid", "validate my rollup rule", "check my pending rollup rules", or "review the rollup requests". Do NOT use this to design or propose new rollups — that is tres-rollup-rules. This skill only measures impact and flags issues; it never executes mutations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create a source-linked rollup of a selected batch of Obsidian wiki log entries. Preview the complete draft while preserving original entries and child pages, then optionally apply the rollup and its index updates together.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a batch of recent wiki log entries
• Condensing logs while preserving source references
• Previewing a rollup before applying it

Use when designing, querying, or troubleshooting the Financial Services Cloud data model — including managed-package (FinServ__ namespace) and Core FSC (standard objects, no namespace) object structures, household relationship modeling, financial account ownership, and the FSC rollup framework. Trigger keywords: FSC data model, FinancialAccount, FinancialHolding, FinancialAccountRole, FinancialAccountParty, FinServ namespace, household rollup, AssetsAndLiabilities, FinancialGoal, LifeEvent, AccountContactRelation FSC. NOT for setting up financial accounts and roles in Setup — use admin/financial-account-setup. NOT for household membership and rollup scheduling — use admin/household-model-configuration.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when configuring Financial Services Cloud (FSC) financial accounts — including account types, FinancialHolding positions, FinancialGoal records, FinancialAccountRole assignments (Primary Owner, Joint Owner, Beneficiary), and household balance rollup behavior. Triggers: configure financial accounts in FSC, set up financial account roles Financial Services Cloud, FSC household balance rollup not working, add holdings to financial account, FinancialAccountType picklist setup, FSC brokerage or retirement account configuration. NOT for household group setup and rollup scheduling — use admin/household-model-configuration. NOT for the FinServ object graph and SOQL — use data/fsc-data-model.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Set up, configure or troubleshoot Salesforce Collaborative Forecasts: forecast types, forecast categories, rollup methods, quota management, forecast hierarchy, manager adjustments, pipeline inspection integration. Trigger keywords: forecast type, forecast category, cumulative rollup, individual rollup, quota, forecast adjustment, forecast hierarchy, opportunity splits forecasting, pipeline forecast. NOT for configuring the opportunity stages, sales processes or split types themselves — use admin/opportunity-management. NOT for territory-based forecasting setup — use admin/enterprise-territory-management. NOT for Classic/Customizable Forecasting.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert in Ethereum L2 solutions - Optimism, Arbitrum, zkSync, Base, and rollup architecture for scalable dApp developmentUse when "layer 2, l2, optimism, arbitrum, zksync, base, rollup, op stack, scaling, layer2, optimism, arbitrum, zksync, base, rollup, scaling, ethereum" mentioned.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when configuring the Financial Services Cloud (FSC) household data model — including Household record type setup, Primary Group assignment, ACR-based membership, rollup field inclusion, and batch rollup scheduling. NOT for NPSP household account configuration (use admin/npsp-household-accounts), non-FSC Account hierarchies, or standard Contact-Account relationships outside of FSC.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build a weekly sales forecast from HubSpot deals using the team’s configured stage probabilities. Compare expected revenue with the quarterly quota, break it down by stage, owner, and segment, and report deal risks in Slack.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing weekly sales forecast reports
• Comparing quarterly forecasts with quotas
• Reviewing forecasts by stage, owner, and segment

Design and debug Solana applications using MagicBlock. The skill covers fast transaction execution, state delegation and settlement, private payments, price feeds, randomness, and temporary permissions, with guidance on routing transactions and validating integrations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Design a Solana game with fast transactions
• Investigate delegated account and routing errors
• Implement private payments and token transfers

A native Remotion data frame — bars grow from zero by real data via spring physics while the figures roll 0→target in sync. The numbers come alive in a way a static HTML chart can't.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when writing analytical SQL over time-series data with the TimescaleDB Toolkit (timescaledb_toolkit extension) hyperfunctions: approximate percentiles, statistical summaries, time-weighted averages, counter/gauge rates, uptime/heartbeat tracking, state durations, OHLC candlesticks, approximate distinct counts, top-N, and downsampling. **Trigger when user asks to:** - Compute percentiles/medians/p95/p99 over large or rolled-up time-series data - Compute rates or deltas from monotonic counters (Prometheus-style) or gauges - Compute time-weighted averages or integrals over irregularly sampled data - Track uptime/downtime from heartbeats, or time spent in each state - Build OHLC/candlestick or VWAP data for financial ticks - Store re-aggregatable summaries in continuous aggregates (two-step aggregation, rollup) - Approximate COUNT DISTINCT, find top-N / most frequent values, or downsample for charts **Keywords:** timescaledb_toolkit, hyperfunctions, percentile_agg, uddsketch, tdigest, approx_percentile, stats_agg, time_weight, counter_agg, gauge_agg, heartbeat_agg, state_agg, candlestick_agg, hyperloglog, approx_count_distinct, min_n, max_n, mcv_agg, lttb, asap_smooth, rollup, two-step aggregation

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still an open loop, and what was just started. Use when someone asks "what happened this week", "what is still open", "what did the team finish", "give me the weekly rollup", or wants a status report over a .specstory/history corpus.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Wire Prisma Next into the project's build system with the right build-tool plugin — Vite today via @prisma-next/vite-plugin-contract-emit (Vite 7 / 8); Next.js / Webpack / esbuild / Rollup / Turbopack are named as gaps rather than fabricated. Always offers the Vite plugin proactively when the project is using Vite. Use for vite plugin, vite-plugin, vite.config.ts, prismaVitePlugin, contract emit on save, HMR, hot reload contract, dev server, Next.js plugin, next plugin, withPrismaNext, webpack plugin, esbuild plugin, rollup plugin, build integration, dev server plugin, vite 7, vite 8.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create a bounded, extractive, structurally idempotent rollup of recent Obsidian wiki log entries, with dry-run preview by default and one optional transaction apply. Use for manual log compression without modifying child pages. Triggers: fold the log, run a fold, run wiki-fold, log rollup, roll up log entries, commit the fold.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Summarize recent agent sessions for the current project, grouped by date with highlights from recorded observations. Review today, the last seven days, or a chosen number of sessions, with totals for sessions, days, and observations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review today's agent work
• Recap project activity from the last seven days
• Summarize a chosen number of recent sessions

Record and query iii engine logs, traces that show how calls flow, and operational metrics. Set up reactions to incoming errors, inspect alerts, and review metrics aggregated over time windows.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating errors through related logs and traces
• Triggering notifications when error logs arrive
• Reviewing metrics aggregated over time

Summarize litigation matters from a shared log, including risk levels, upcoming deadlines, stale records, and estimated financial exposure. Flag overdue tasks, incomplete conflict checks, and other gaps that need a legal team's attention.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review the status of all active litigation matters
• Check deadlines across the next 14, 30, and 60 days
• Find stale matters and overdue deadlines

Track case deadlines for a legal clinic in a shared record. Add and update dates, record completion, and generate reports showing overdue work, approaching deadlines, and workload by student or practice area.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing deadlines across cases for the coming week
• Recording a changed date or reassigned student
• Finding overdue or unassigned deadlines

Improve website loading and responsiveness by optimizing images, fonts, scripts, and caching. Identify priorities, reduce JavaScript download size, split code into smaller loads, and verify changes through a structured performance improvement workflow.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Improving slow page loading
• Reducing JavaScript download size
• Reviewing image and font loading

End-to-end onboarding of a new entity, customer, or account into TRES Finance. Orchestrates 8 steps in order: wallet upload, data collection (commit), balance validation, reconciliation, cost basis, export unidentified addresses, import contacts, and rollup rules. Trigger ONLY when the user explicitly wants to onboard a new entity, customer, or account — e.g. "onboard a new entity", "onboard new customer", "start onboarding for [name]", "set up a new account in TRES", "run the full onboarding flow", "I need to onboard [company name]", "new entity onboarding". Do NOT trigger for individual tasks — those have their own dedicated skills. If the user asks to "add wallets" without mentioning onboarding, use tres-wallets-upload. "Validate balances" alone is tres-asset-balance-validation. "Run a commit" alone is tres-data-collection-commit. Only trigger when the user wants the full pipeline.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate structured test reports with pass/fail rollups, coverage summaries, and test artifacts. Use when the user is asking for test-result packaging or delivery, not for root-cause debugging or feature implementation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user asks to "run the weekly social readout", "which denominator does our engagement rate use", or "which posts won this week and what changes next cycle"; produces the organic-social metric dictionary (every rate names its denominator — ERR engagement-by-reach vs ERI by-impressions vs ER-by-follower — locked across periods), median-not-mean per-post rollups with organic and boosted separated, EMV as labeled exec-translation only (never inside any score), an attributed CHAOSS/Orbit-style community-health readout with employees excluded, and the best/worst-performer write-back the next calendar cycle consumes. Not for dollar-ROI math or the ECHO profile result gate verdict — use roi-calculator and social-quality-auditor. 社媒周报/互动率分母/指标字典/复盘回写

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user asks to "read back" a paid campaign change, "did this ad change work", or "compare ROAS/CPA before and after"; reads ROAS/CPA against a control over a fixed readback window and returns a Promote / Keep-testing / Rollback / Unproven readback decision with the math delegated to roi-calculator. Not for RQS scoring or veto adjudication — use ad-account-auditor; not for the ROI ratio math — use roi-calculator; not for cross-channel rollups — use performance-analyzer. 付费广告复盘/ROAS回看/投放效果归因

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.