'summary' 검색 결과

Classical end-to-end empirical analysis workflow in the modern tidyverse + econometrics R ecosystem — dplyr + tidyr + haven + fixest + sandwich + lmtest + clubSandwich + AER + ivreg + did + bacondecomp + HonestDiD + eventstudyr + rdrobust + rddensity + Synth + gsynth + synthdid + MatchIt + WeightIt + cobalt + ebal + grf + DoubleML + mediation + marginaleffects + modelsummary + kableExtra + gt + ggplot2 + ggpubr + cowplot + binsreg. **Defaults to economics empirical-paper style** (AER / QJE / AEJ) — every run produces a publication-ready output set with a multi-column regression table (M1→M6 progressive controls/FE) as the centerpiece, plus Table 1 (descriptives), mechanism / heterogeneity / robustness tables, and event-study + coefficient + trend figures. Covers the full 8-step R pipeline an applied economist runs on every paper — (1) data import & cleaning (read_dta/read_csv, naniar, janitor, validate-merges), (2) variable construction (mutate/across/winsorize/group_by + lag/lead with dplyr), (3) descriptive statistics & Table 1 (gtsummary, modelsummary::datasummary, tableone), (4) classical diagnostic tests (shapiro/jarque.bera.test/bptest/dwtest/bgtest/vif/adf.test/kpss.test/Hausman), (5) baseline modeling (fixest::feols, ivreg, did::att_gt, eventstudyr, sun_ab, did_imputation, synthdid, rdrobust, MatchIt, WeightIt, grf::causal_forest, DoubleML, mediation), (6) robustness battery (modelsummary stack, clubSandwich CRSE, fwildclusterboot, ri2, robomit Oster, bacondecomp, HonestDiD), (7) further analysis (interactions + marginaleffects, mediation::mediate, gsem via lavaan, dose-response splines, grf CATE), (8) publication-ready tables & figures (modelsummary, kableExtra, gt, stargazer, texreg, flextable to LaTeX/Word/HTML; ggplot2 + ggpubr + cowplot + binsreg + iplot for figures). **Also covers two parallel domain modes that share the same 8-step scaffolding** — **Mode A — Epidemiology / public health** (target-trial emulation, IPTW + g-formula + TMLE doubly-robust triplet via `WeightIt` / `gfoRmula` / `tmle` / `ltmle`, Mendelian randomization via `MendelianRandomization` / `TwoSampleMR` / `MRPRESSO`, KM / Cox / AFT / RMST survival via `survival` / `survminer` / `flexsurv`, E-value sensitivity via `EValue`, principal stratification — STROBE / TRIPOD reporting), and **Mode B — ML causal inference** (DML via `DoubleML`, S/T/X/R/DR meta-learners via `causalweight` / `grf`, causal forest via `grf::causal_forest`, BART/BCF via `bartCause` / `bcf`, matrix completion via `MCPanel`, CATE distribution + policy tree via `policytree`, off-policy evaluation, conformal causal via `conformalInference` / `cfcausal`, fairness audit via `fairmodels`, DAG learning via `pcalg` / `bnlearn` / LLM-assisted). Use when the user asks for a complete R empirical analysis, wants a tidyverse-style reproducible R script / Quarto workflow, prefers fixest over reghdfe, needs the R counterpart to StatsPAI / 00.1 / 00.2, or names a specific R step in isolation ("feols with cluster", "MatchIt nearest neighbor", "bacondecomp in R", "gtsummary table 1", "modelsummary to Word"). Mode A triggers on "target trial emulation R", "tmle ltmle", "MendelianRandomization", "TwoSampleMR", "MRPRESSO", "survival cox AFT", "STROBE R", "EValue R", "公共健康 R", "流行病学 R". Mode B triggers on "DoubleML R", "grf causal forest", "policytree", "bartCause bcf", "conformal causal R", "fairmodels", "pcalg NOTEARS", "因果机器学习 R".

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

Convert a stakeholder summary markdown file into a single self-contained HTML executive report — bottom line and decision asks up front, supporting detail later — styled with a Test Double-derived palette and self-contained mermaid diagrams. Use when the user wants to turn a stakeholder summary, executive summary, or business summary into an HTML report, generate an HTML version of a summary doc, or produce a shareable HTML file from a summary markdown. Produces an HTML sibling file only; does not publish anything.

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

Summarize a Paperclip project or workspace in plain language, starting with up to three concrete actions needed to unblock work. Review issues and comments, then save a concise Markdown update to its summary slot.

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

• Identify decisions or approvals blocking work
• Refresh a project's summary card
• Summarize activity across workspaces

Turn sales call transcripts or notes into a customer follow-up draft, an internal team summary, and proposed customer record updates. Capture decisions, concerns, and commitments, with source references supporting the suggested changes.

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

• Drafting a customer follow-up after a sales call
• Preparing a call summary for the internal team
• Listing objections and commitments from both sides

Turn a completed contract review into a short summary for procurement, finance, or department heads. Explain signing status, important conditions, required actions, and approval timing in plain language tailored to the reader.

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

• Summarizing a contract review for procurement
• Explaining renewal and cancellation conditions to a budget owner
• Sharing contract issues and required business decisions

Build TypeScript summary panels that combine data already fetched by other panels. Accept partial updates, wait for required fields before rendering, and update displayed metrics without additional network requests, using reusable base classes and a coordinator.

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

• Combine email and stock metrics in one summary panel
• Wait for required data before showing a summary
• Update metrics using data fetched by other panels

Get a quick structural overview of a codebase with Trailmark. The skill identifies programming languages, counts entry points where execution begins, and returns dependency information to support orientation before deeper analysis.

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

• Getting oriented in an unfamiliar codebase
• Checking languages and entry point counts before analysis
• Preparing a structural overview for Vivisect or Galvanize

Rewrites technical research content into a structured lay summary that cross-disciplinary teams can quickly understand and act on. Use when the user wants to explain research to colleagues outside their specialty — clinicians, wet-lab scientists, bioinformaticians, product managers, or leadership. Trigger on: "lay summary", "explain my research to the team", "non-technical summary", "cross-disciplinary summary", "translate my findings", "align our team on the study", or any request to communicate research goals, findings, or next steps to a mixed or non-specialist audience. Part of the AIPOCH Academic Writing skill hub. Sits midstream: after research content is clarified, before downstream deliverables like slide decks or graphical abstracts.

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

Integrates Power Pages generative-AI summarization APIs (PREVIEW) into a Single Page Application (SPA) site — the Search Summary API and the Data Summarization API — on any record-detail or list page. Generates per-target service code (CSRF-handled) and AI site settings; delegates Web API settings, table permissions, and web roles to `/integrate-webapi` and `/create-webroles`. Use whenever a user wants AI/Copilot output that condenses Dataverse content on a Power Pages site — an AI summary, AI-generated overview or "key insights" across a record or list, a search-results summary, a case/incident summary, or recommendation-chip refinement — even when phrased as "AI-generated paragraph", "insights", or "overview". Do NOT use for: generative pages in model-driven apps (use the model-apps `genpage` skill), Copilot Studio agents/chatbots, summarizing documents or PDFs, Power BI dashboards, plain keyword search with no AI summary, or plain Dataverse CRUD (use `/integrate-webapi`).

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

Produces a plain-language stakeholder summary from an existing feature specification, for sharing with non-technical stakeholders before implementation kicks off. Use when the user wants to draft a stakeholder summary, executive summary, or business summary of a feature spec or PRD. Does not write the spec itself — use plan-a-feature. Does not sequence the build into phases — use plan-a-phased-build. Does not produce an implementation plan — use plan-implementation.

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

Generates a concise, executive-ready performance summary covering key metrics, trends, and what's driving movement. Use this skill when someone needs to produce a briefing, executive summary, performance narrative, or stakeholder readout — for example, "write an exec summary of last week's performance," "create a performance briefing for our leadership team," "produce a monthly business review summary," "what should I tell executives about our metrics," or "generate a performance narrative." Also trigger for "QBR summary," "weekly business review," or "stakeholder briefing."

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

Generates a concise, executive-ready performance summary covering key metrics, trends, and what's driving movement. Use this skill when someone needs to produce a briefing, executive summary, performance narrative, or stakeholder readout — for example, "write an exec summary of last week's performance," "create a performance briefing for our leadership team," "produce a monthly business review summary," "what should I tell executives about our metrics," or "generate a performance narrative." Also trigger for "QBR summary," "weekly business review," or "stakeholder briefing."

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

Compare two saved cost-summary JSON snapshots to identify changes in total spending, sessions, and model costs. Set limits on spending increases or token growth to flag cost regressions during pull request checks.

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

• Comparing spending before and after a pull request
• Finding models responsible for cost changes
• Failing checks when spending exceeds set limits

Combine today's calendar meetings and open tasks into a summary for a daily team check-in. Review the results as JSON, a table, YAML, or CSV without changing calendar or task data.

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

• Prepare a summary for a daily team check-in
• Review today's meetings alongside open tasks
• Get a daily summary in table or JSON format

Review a GitHub pull request or branch and receive a concise summary of its purpose, design choices, and notable code. Check linked issue acceptance and highlight evidence-based concerns through their observable impact on users.

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

• Understand a pull request before reviewing it
• Summarize changes in a branch without a PR
• Review design decisions with file and line references

Turn completed milestone artifacts into one readable project summary. It explains what was built, how it works, and why decisions were made, helping new team members get started and supporting project reviews.

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

• Introducing a completed project to new team members
• Reviewing a milestone's deliverables and decisions
• Summarizing requirements and technical debt for handover

Fetch a web page and return a concise Markdown summary focused on its main content. The output includes a title, a short overview, up to five key points, and the source URL, without saving files.

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

• Getting a quick overview of a shared URL
• Reviewing a page's main points without navigation or ads
• Receiving a Markdown summary with its source URL

Turn a development-ready feature's specifications, customer context, demand evidence, and mockups into a concise executive summary. Give sales, leadership, and engineering one shared document covering the problem, solution, key decisions, scope, dependencies, metrics, and audience-specific questions.

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

• Create a shared feature briefing for sales, leadership, and engineering
• Summarize customer needs and reasons to prioritize a feature
• Clarify key decisions, exclusions, and dependencies

Econometrics skill for descriptive statistics and summary tables. Activates when the user asks about: "descriptive statistics", "summary statistics", "summary table", "Table 1", "balance table", "means and standard deviations", "correlation matrix", "data summary", "sample characteristics", "variable distributions", "描述性统计", "描述统计", "汇总统计", "统计表", "均值标准差", "平衡性检验", "相关矩阵", "样本特征", "变量分布"

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

Write a structured clinical case summary or case presentation. Use when asked to write a clinical case summary, case presentation, patient case report, or clinical handover. Produces a structured summary using SBAR or SOAP format. For educational and documentation purposes only — not a substitute for clinical judgement.

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

Produces structured summaries of U.S. divorce settlement agreements (MSAs), extracting material terms across property, custody, support, taxes, insurance, fees, and deadlines. Triggers on requests for divorce settlement summary, MSA summary, marital settlement agreement, property division, child custody, parenting plan, child support, or alimony extraction.

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

Produces privilege-safe U.S. corporate legal billing summaries from time and expense data. Converts entries into client-friendly narratives with categorized hours, rates, expenses, and milestones while enforcing engagement-letter rules and ethical billing safeguards. Use when asked to create a billing summary, invoice narrative, timekeeper breakdown, expense summary, or fee narrative.

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

Produce a short executive summary for the current rolling-wave project. Use when the user wants a concise status update, investor/team-friendly summary, leadership summary, project progress snapshot, or TL;DR of completed slices, the current slice plan, and upcoming slices.

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

Create a Dubai weather card from a supplied temperature and unit. The skill writes an SVG, a scalable image format, and a Markdown summary to designated files, preserving the provided temperature exactly.

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

• Turning a Dubai temperature reading into a weather card
• Saving a temperature summary in Markdown
• Updating weather image and summary files in a workflow