180 件 ・ 関連度順
概要と使いどころ
Analyzes Java/JAR malware (such as Adwind/jRAT-class cross-platform RATs) by inventorying the archive, reading the manifest entry point, detecting obfuscators and string encryption, and flagging suspicious runtime, reflection, and networking class usage. Activates for requests to analyze a malicious JAR, inspect Java malware, or identify a Java RAT.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked 把这段黑话翻译成人话, 这句话到底什么意思, 帮我把周报去黑话, 用大厂黑话改写这段, 互联网黑话词典, 对齐抓手闭环是什么意思, or translate Chinese internet-company jargon (互联网黑话) into plain words and back. Produces a line-by-line translation of 黑话 into plain Chinese with what each sentence actually commits to (who, what, by when), a rewrite at the chosen tone (白话, 得体职场, or 满分大厂味 parody), a 40-plus term glossary with plain meanings, and a 周报去黑话 mode that turns a jargon-heavy weekly report into one a reader can act on.
日本語の概要は準備中です。原文の説明を表示しています。
Assemble the final `.ppmplugin` binary bundle for a PAM native extension and verify its contents. First **reconciles** the manifest's declared `entrypoints` against the binaries actually staged — if the manifest declares a platform with no built binary it gates (build it / ship without it / stop) rather than shipping a broken bundle. Then re-runs the plugin's upload-compatibility checks on the reconciled manifest, zips the manifest plus whichever of `android/<PascalName>Plugin.dex` and `ios/<PascalName>Plugin.framework/` are present into `ppmplugin/<name>.ppmplugin`, and verifies the archive layout with `jar tf` (exactly the manifest + the shipped binaries — nothing missing, nothing extra). Output: a statically verified `.ppmplugin` file on disk. Prereqs: `jar` (JDK). Run after /generate-ppmplugin-manifest and the build skill(s).
日本語の概要は準備中です。原文の説明を表示しています。
Migrate Databricks workloads from classic compute to serverless compute. Use when migrating notebooks, jobs, pipelines, or Scala JARs (`spark_jar_task`) from classic clusters to serverless, checking if existing code is serverless-compatible, or writing new serverless-compatible code. Provides concrete fixes for the serverless Spark Connect architecture and guides the full migration. Not for classic DBR version upgrades or cluster configuration changes within classic compute.
日本語の概要は準備中です。原文の説明を表示しています。
产品设计 / UX 设计 (产品设计 / UX 设计 (Product Design / UX Design) — 数字产品的用户体验设计：从用户研究 → 信息架构 → 交互设计 → 视觉/UI → 可用性测试 → 设计系统的认知操作系统，面向 UX designer / product designer / interaction designer / UX researcher / design systems engineer / design lead，以及想入行、转岗、服务这行(设计外包、设计工具厂商、研究平台)的视角。覆盖: (a) 第一性张力 — **用户中心/研究驱动 (user-centered, 'you are not the user', research before pixels, observe behavior not opinions) ⇄ 商业目标/约束/交付 (business goals, north-star metrics, ship it, designer 服务于产品成功不是个人作品集)**; **设计直觉/品味/craft (taste, aesthetics, 'attractive things work better' — Norman 情感化设计) ⇄ 数据/实验/A-B 测试 (data-driven, metrics, experimentation, 'opinions are not data')**; **用户说的 (stated preference, 访谈里说喜欢) ⇄ 用户做的 (revealed behavior, 行为观察 > 自陈, usability test 看人真实卡在哪)**; **一致性/设计系统/规范 (consistency, design system, Jakob's law 用户带着别处的习惯来, 复用组件) ⇄ 创新/打破模式 (innovation, 该不该破规范)**; **减法/简化 (simplicity, Krug 'Don't Make Me Think', less but better — Dieter Rams) ⇄ 功能丰富/利益相关者塞需求 (feature creep, stakeholder pressure)**; **UX(体验/流程/研究) ⇄ UI(视觉/像素/组件)** 的职责之争, **designer 该不该写代码 (design engineer / 'should designers code')**; (b) 核心工作流 / pipeline (最标准、最易蒸高质量+CLI 化) — Double Diamond (发现 discover → 定义 define → 开发 develop → 交付 deliver) / Design Thinking (共情 empathize → 定义 → 构思 ideate → 原型 prototype → 测试 test) / Design Sprint (Jake Knapp 5 天冲刺); 完整链: 用户研究 (访谈/问卷/可用性测试/卡片分类) → persona / journey map / JTBD → 信息架构 IA + 用户流 user flow → 线框 wireframe (低保真) → 交互/原型 prototype (高保真) → 视觉 UI / 设计系统落地 → 可用性测试 usability testing → handoff 给开发 → 度量迭代 (北极星 / HEART 框架); (c) 工具栈 — 设计/原型 (Figma 绝对主导 / Sketch 衰退 / Adobe XD 已停更 / Framer 高保真+建站 / Penpot 开源 / Principle / ProtoPie 微交互); 协作白板 (FigJam / Miro / Mural); 用户研究 (Maze / UserTesting / Lookback / Dovetail 研究库 / Optimal Workshop 卡片分类树测试 / Hotjar / Microsoft Clarity 热图); 设计系统/交付 (Storybook / 蓝湖(中) / Zeplin / design tokens / Tokens Studio); 度量 (Amplitude / Mixpanel / 北极星指标); AI 新兴 (Figma AI / v0 by Vercel / Galileo AI / Uizard / Cursor 给 design engineer); (d) 知识正典 — Don Norman《The Design of Everyday Things》(affordance/signifier/mapping 圣经)、Steve Krug《Don't Make Me Think》(可用性入门)、Alan Cooper《About Face》《The Inmates Are Running the Asylum》(交互设计/persona 起源)、Jakob Nielsen 10 Usability Heuristics + NN/g 文章库、Jake Knapp《Sprint》、Jeff Gothelf《Lean UX》、Teresa Torres《Continuous Discovery Habits》、Erika Hall《Just Enough Research》、Julie Zhuo《The Making of a Manager》、《Refactoring UI》(Adam Wathan/Steve Schoger)、《Universal Principles of Design》、Laws of UX (Jon Yablonski)、《100 Things Every Designer Needs to Know About People》(Susan Weinschenk)、IDEO/Stanford d.school 设计思维材料; (e) figures/流派 — 认知心理/人因派 (Don Norman 认知科学奠基、Susan Weinschenk 行为心理、Kathryn Whitenton); 可用性工程派 (Jakob Nielsen 启发式/折扣可用性、Steve Krug、Jared Spool UIE); 交互设计/目标导向派 (Alan Cooper goal-directed/persona、Kim Goodwin); 设计思维派 (IDEO Tim Brown、David Kelley d.school); 精益/持续探索派 (Jeff Gothelf Lean UX、Teresa Torres continuous discovery、Marty Cagan《Inspired》产品发现); 设计系统/系统化派 (Brad Frost Atomic Design、Nathan Curtis design tokens、Alla Kholmatova); 视觉/UI craft 派 (Adam Wathan & Steve Schoger Refactoring UI、Dieter Rams 'less but better' 工业设计遗产); 设计领导/职业派 (Julie Zhuo、Aarron Walter 情感化设计、John Maeda); 移动优先 (Luke Wroblewski 'Mobile First'); (f) 行业话术/黑话 — affordance 可供性 / signifier 意符 / mental model 心智模型 / IA 信息架构 / heuristic evaluation 启发式评估 / usability 可用性 / a11y accessibility 无障碍 / WCAG / persona 用户画像 / journey map 用户旅程 / JTBD jobs-to-be-done / north-star metric 北极星 / HEART 框架 / wireframe 线框 / mockup / prototype 原型 / fidelity 保真度 (lo-fi/hi-fi) / design system 设计系统 / design token 设计令牌 / atomic design 原子设计 / component library 组件库 / handoff 交付 / red routes 关键路径 / dark pattern 暗黑模式 / Fitts's law / Hick's law / Jakob's law / Miller 7±2 / progressive disclosure 渐进披露 / above the fold / hamburger menu / skeuomorphism vs flat / micro-interaction / empty state / edge case / happy path / design debt 设计债 / dogfooding / dot voting / affinity mapping 亲和图 / card sorting 卡片分类 / tree testing / A/B test / NPS / SUS (System Usability Scale); (
日本語の概要は準備中です。原文の説明を表示しています。
Audits a methods section against a 45-item reporting checklist synthesized from the APSA Experimental Section rubric, JARS-Quant, CONSORT, and DA-RT, covering pre-registration, recruitment, randomization and treatments, sample flow and attrition, sample-size justification, three-tier results labeling, conjoint reporting, validity, and open-science infrastructure. Use when checking whether a methods section reports enough, preparing a submission or replication archive, asking what CONSORT, JARS, or DA-RT require, or documenting a deviation from a pre-analysis plan. Writing that plan before data collection goes to pre-registration-writing.
日本語の概要は準備中です。原文の説明を表示しています。
Javaのtinystructで、端末とWebの両方から使える処理を実装するスキル。起動スクリプトの生成からAPI、データ保存、テストまで開発手順を案内します。
Provides the static system voice catalog used by Jarvis. It does not define a user-facing workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Turn any concept, lesson, slide deck, or source material into a Feynman learning cycle in which learners explain first, expose the smallest gap, rebuild the explanation through Socratic prompts, strip jargon, stress-test analogies, and transfer the idea to a new context. Use when the user asks for teach-back, learning by explaining, or a Feynman-style classroom. Do not use when the Feynman technique itself is merely the lesson topic or when study strategy should remain a parallel goal.
日本語の概要は準備中です。原文の説明を表示しています。
Plain-English translation layer for non-technical Copilot CLI users. Translates every approval prompt, error message, and technical output into clear, jargon-free English with color-coded risk indicators.
日本語の概要は準備中です。原文の説明を表示しています。
Writing style guide derived from Modal's documentation voice. Apply when writing or editing docs, guides, tutorials, or technical prose that should read direct, second-person, confident, low-jargon, and example-first. Use to draft new docs in this voice or to revise existing prose toward it.
日本語の概要は準備中です。原文の説明を表示しています。
Decompile Android APK, XAPK, JAR, and AAR files using jadx or Fernflower/Vineflower. Reverse engineer Android apps, extract HTTP API endpoints (Retrofit, OkHttp, Volley), and trace call flows from UI to network layer. Use when the user wants to decompile, analyze, or reverse engineer Android packages, find API endpoints, or follow call flows. 中文触发词：反编译APK、安卓逆向、提取API、分析安卓应用、反编译安卓、逆向工程、追踪调用链、提取接口
日本語の概要は準備中です。原文の説明を表示しています。
根据研究者提供的**研究计划书（Research Proposal）**执行基于中国制度环境的公司金融类实证研究全流程。**启动后第一件事：根据计划书的主题、识别策略、贡献边际与样本范围，从中国-context 英文顶级期刊池（JF/JFE/RFS/JFQA/MS/JCF/JBF/JAR/JAE/TAR/CAR/JIBS/China Economic Review/PBFJ 等 25+ 期刊）中推荐 5 本最匹配的目标期刊（[J1]–[J5]），等待研究者明确选定一本；该期刊决定 main.tex 的 bibliographystyle、Section 骨架、Introduction 风格与表注规范**。然后用 Python 完成数据清洗、描述性统计、基准回归、内生性检验（IV/2SLS、DML）、平行趋势、异质性、机制、稳健性检验与图表绘制。LaTeX 表格和图像严格遵循 template/ 示例格式，研究逻辑与排版严格遵循 rule/ 下的《通用实证研究逻辑与规范总结》与《回归表写作规范总结》。数据集与政策集从 asset/ 中按计划书中的关键词检索。**当计划书预期的实证结果无法实现时（系数不显著、平行趋势不通过、IV 弱工具、机制不成立等），skill 自动切换备选方案直至完成研究项目**。最终交付物：Python 代码 + LaTeX 表格 + 图像（.pdf/.png）。触发条件：研究者提交研究计划书（含 X→Y 假设、识别策略、样本、政策冲击等）。
日本語の概要は準備中です。原文の説明を表示しています。
根据研究者提供的**研究计划书（Research Proposal）**执行基于**外国（美国/欧盟/英国/日本/跨国）制度环境**的公司金融类实证研究全流程。**启动后第一件事：根据计划书的主题、识别策略、贡献边际与样本范围，从外国 CF 顶刊池（AER/QJE/JPE/JF/JFE/RFS/JFQA/JAR/JAE/MS/JCF/JBF 等 25+ 期刊）中推荐 5 本最匹配的目标期刊（[J1]–[J5]），等待研究者明确选定一本；该期刊决定 main.tex 的 bibliographystyle、Section 骨架、Introduction 风格与表注规范**。然后用 Python 完成数据清洗、描述性统计、基准回归、内生性检验（IV/2SLS、DML）、平行趋势、异质性、机制、稳健性检验与图表绘制。LaTeX 表格和图像严格遵循 template/ 示例格式，研究逻辑与排版严格遵循 rule/ 下的《通用实证研究逻辑与规范总结》与《回归表写作规范总结》。数据集与政策集从 asset/ 中按计划书中的关键词检索（WRDS / NBER/Fed releases / FRED / 全球宏观库）。**当计划书预期的实证结果无法实现时（系数不显著、平行趋势不通过、IV 弱工具、机制不成立等），skill 自动切换备选方案直至完成研究项目**。最终交付物：Python 代码 + LaTeX 表格 + 图像（.pdf/.png）。触发条件：研究者提交研究计划书（含 X→Y 假设、识别策略、样本、政策冲击等）。
日本語の概要は準備中です。原文の説明を表示しています。
STATA code pattern library for empirical archival accounting research. Provides tested syntax from 126 peer-reviewed JAR (Journal of Accounting Research) replication files (2017-2025). Use when the user asks procedural questions like "How do I implement [method]?" or "Show me code for [technique]" — including: entropy balancing, propensity score matching (PSM), difference-in-differences (DiD), regression discontinuity (RDD), instrumental variables (IV), event studies (CAR/BHAR), survival analysis, Fama-MacBeth regressions, bootstrap, quantile regression, reghdfe/xtreg/areg, clustering standard errors, fixed effects, esttab/outreg2 table formatting, winsorization, leads/lags. Users can specify their variables (e.g., treatment, outcomes, controls) and receive adapted syntax. NOTE: This skill provides code patterns from published papers, not research design advice.
日本語の概要は準備中です。原文の説明を表示しています。
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".
日本語の概要は準備中です。原文の説明を表示しています。
Write or rewrite text in plain, layman-readable English in the spirit of ASD-STE100 Simplified Technical English: short sentences, active voice, simple tenses, one word one meaning, condition before command, every technical term defined at first use, no AI slop. Default mode is Plain. Strict mode applies full STE vocabulary compliance when the user names STE, ASD-STE100, or compliance. Use for documentation, READMEs, runbooks, procedures, error messages, release notes, incident reports, API guides, and explanations for readers outside the field. Also use when the user says "STE", "Simplified Technical English", "ASD-STE100", "plain English", "layman's terms", "explain it simply", "no jargon", "de-slop", "make this readable", "write for non-native readers", or asks for docs that translate well. The same rules govern the reply: answer first, prose only.
日本語の概要は準備中です。原文の説明を表示しています。
Raw, anti-design aesthetic inspired by concrete architecture with unadorned elements, jarring layouts, and functional minimalism.
日本語の概要は準備中です。原文の説明を表示しています。
Switch Agent persona preset. Supports 8 presets including default assistant, business, tech expert, butler, girlfriend, boyfriend, family, and Jarvis. Use when user asks to change communication style or personality.
日本語の概要は準備中です。原文の説明を表示しています。
Use when converting medical text between academic and patient-friendly tones, translating medical jargon for patients, adapting research papers for public audiences, or rewriting clinical notes for patient handouts. Maintains medical accuracy while adjusting readability level.
日本語の概要は準備中です。原文の説明を表示しています。
Use when configuring Maven plugins, setting up common plugins like compiler, surefire, jar, or creating custom plugin executions.
日本語の概要は準備中です。原文の説明を表示しています。
Restate the last message in plain human language, with no jargon. Use for /bro or when asked to say it plainly.
日本語の概要は準備中です。原文の説明を表示しています。
ALWAYS invoke this skill when you need the user to act - run a command, paste a secret, click, approve - and whenever they ask how to do something or say they do not know what to do: "step by step", "walk me through it", "what do I do", "what should I do", "I don't understand what to do", "explain what I need to do", in any language. Picking which task comes next is os-whats-next; this skill is for doing the thing in front of you. First earn the ask: try it yourself, find another route, shrink it to the part only they can do. Then one action per step, commands labelled by what they touch, no jargon. Commands are single lines that prompt for any value - typing hidden for secrets - and confirm in plain words. Afterwards verify their step.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a docs page or section has been written or rewritten and is about to be handed over, when the operator says "reader review", "does this read like a human wrote it", "too much jargon", "plain language", or when a docs brief asks for a review before a pull request.
日本語の概要は準備中です。原文の説明を表示しています。