Results for “mechanisms”

亚马逊管理之道 (亚马逊管理之道 (The Amazon Way — Amazon 自身的领导力与运营操作系统) — 这个 master skill 蒸馏的不是『在亚马逊平台上开店卖货』(那是跨境电商运营,已由 cross-border-ecommerce 另蒸),也不是 AWS 云技术架构;而是亚马逊这家公司『怎么运营自己、怎么做决策、怎么招人、怎么创新、怎么规划』的一整套可迁移的管理机制(mechanisms)与心智操作系统。面向想在自己团队/公司引入亚马逊式机制的创始人/CEO/高管/运营负责人(COO)、产品经理与技术产品经理(PM/PMT)、组织与流程设计者(chief of staff / ops)、以及在亚马逊工作或准备面试亚马逊(著名的 LP 行为面试 + Bar Raiser)的人。覆盖: (a) 第一性张力 — 亚马逊 OS 的核心世界观分歧: **机制 > 良好意图(Good intentions don't work, mechanisms do:问题不能靠『下次更努力』修复,要装一个带检查闭环的自我强化流程) ⇄ 可控输入指标 vs 滞后输出指标(管你能控制的 input 如选品/价格/在库/配送速度,而非 revenue/股价这类滞后又不可控的 output) ⇄ 长期主义 vs 季度业绩(Day 1、willing to be misunderstood、用现金流+飞轮长期投入,宁可牺牲短期利润) ⇄ 客户执念 vs 竞争对手执念(working backwards 从客户倒推,而非从竞品或『我们能造什么』正推) ⇄ 叙事备忘录 vs PPT(6-pager + 开会前静默阅读、动手前先写 PR/FAQ;写作逼出清晰思考,禁 PowerPoint) ⇄ 单线程负责人/两个披萨团队 vs 协调税(separable、autonomous、one owner per initiative,砍掉跨团队依赖) ⇄ 高标准可学习可传递 vs 与生俱来(insist on the highest standards + Bar Raiser 招聘门,标准是 domain-specific 且能教的) ⇄ 节俭催生创造力 vs 血汗文化(frugality/约束驱动发明 —— 但 frugality + 高压 bar + URA 强制淘汰 = 文化阴暗面批判) ⇄ 两类决策(Type 1 不可逆/单向门 慎重 vs Type 2 可逆/双向门 高判断力个人快速决策,别用重流程拖慢))**; (b) 核心机制(mechanisms,本行的『工具栈』其实是一套运营机制而非软件) — Leadership Principles(14 条→2021 增至 16 条,是一套运营语言和决策仲裁器)、Working Backwards(从客户倒推:动手前先写新闻稿+常见问答 PR/FAQ)、叙事备忘录(6-pager narrative / 1-pager + silent reading 静默阅读、禁 PPT)、Weekly Business Review(WBR + metrics deck 指标看板)、input/output metrics(可控输入指标体系、DMAIC 式指标选择)、年度规划(OP1/OP2 + S-Team goals)、Bar Raiser(招聘机制,独立于用人经理的抬杠者拥有一票否决)、Two-Pizza Team / Single-Threaded Leader STL / separable teams、Correction of Errors(COE 事故复盘 + 5 Whys 五问法)、Andon Cord(安灯绳,借自丰田,一线可拉停)、Flywheel(飞轮:低价→更多客户→更多卖家→更多选品→更低成本结构→更低价)、Type 1/Type 2(单向门/双向门决策分级)、Regret Minimization Framework(遗憾最小化,贝索斯创业决策法); (c) 心智模型层 — customer obsession(客户执念是所有 LP 之首)、long-term thinking / Day 1(第二天就是停滞衰亡)、invent and simplify、ownership(主人翁,不说 that's not my job)、bias for action(可逆决策就快,speed matters)、disagree and commit(充分反对后即便不同意也全力执行)、frugality、dive deep(深入细节、不靠代理指标脱离一线)、think big、are right a lot(用强判断力和证伪自己的能力多做对的判断)、earn trust、deliver results; (d) 工作流/SOP — 用亚马逊方式发起一个新产品/业务(先写 PR/FAQ→评审→倒推着造)、如何跑一场 WBR、如何写和评审一份 6-pager(叙事流程 + 静默阅读)、Bar Raiser 招聘 loop、年度规划(OP1/OP2→S-Team goals→输入指标追踪)、事故后的 Correction of Errors; (e) 知识正典(en-primary,极其丰富且可取一手) — 贝索斯致股东信 1997-2021(1997 首封是奠基文本,每年附在信末;Day 1、遗憾最小化、long term)、《Working Backwards》Colin Bryar & Bill Carr(2021,运营机制圣经)、《The Everything Store》Brad Stone(2013,公司史)、《Amazon Unbound》Brad Stone(2021,权力与阴暗面续作)、《Invent and Wander》贝索斯文集(2020)、《The Amazon Way》/《Think Like Amazon》John Rossman(前亚马逊高管)、Amazon 官方 Leadership Principles 页(amazon.jobs,一手)、HBR『The Institutional Yes』(2007 贝索斯访谈); (f) 行业大佬/figures — Jeff Bezos(创始人,源头教义)、Andy Jassy(现任 CEO,OS 超越创始人的证据 + AWS 缔造者)、Colin Bryar(前贝索斯影子/TPM,《Working Backwards》作者)、Bill Carr(前数字媒体 VP,《Working Backwards》作者)、Jeff Wilke(前全球消费者 CEO,运营架构师)、John Rossman(前亚马逊、机制布道者/顾问)、Brad Stone(记者/编年史作者,批判性外部视角); (g) 争议/批判(必须保留,不能洗白) — 文化阴暗面(NYT 2015『Inside Amazon: Wrestling Big Ideas in a Bruising Workplace』揭露高压职场)、仓储与一线劳工争议、URA(unregretted attrition 强制淘汰)与 stack-ranking 的残酷、frugality + 高 bar = 燃尽(burnout);机制能否迁出亚马逊(cargo-culting:在初创或非科技公司照搬 PR/FAQ/输入指标/Bar Raiser 常失败);是贝索斯个人天才(personality)还是制度化机制(institution)—— OS 在贝索斯卸任后于 Jassy 治下延续,是机制派的证据; (h) 流派/思想谱系 — **信徒/机制布道派(Bryar & Carr《Working Backwards》+ 前亚马逊 operator 顾问圈,信 mechanisms 可移植、任何公司可安装)** vs **批判派(Brad Stone《Amazon Unbound》+ NYT + 劳工视角,认为 OS 与高淘汰的残酷机器不可分割,不该被浪漫化)** vs **情境/规模怀疑派(机制之所以有效是因为亚马逊特定的规模/现金流/创始人权力,照搬到小公司=cargo cult)** vs **创始人中心 vs 制度中心之争(是贝索斯个人 vs 可传承的机制)**。不含: 在亚马逊开店卖货/选品/PPC/FBA 的卖家运营(=cross-border-ecommerce)、AWS 云技术架构与运维、通用 MBA 管理理论泛泛而谈、把普通商业常识包装成『亚马逊独家秘诀』。) Master OS — automated mastery of 亚马逊管理之道 (The Amazon Way — Amazon 自身的领导力与运营操作系统) — 这个 master skill 蒸馏的不是『在亚马逊平台上开店卖货』(那是跨境电商运营,已由 cross-border-ecommerce 另蒸),也不是 AWS 云技术架构;而是亚马逊这家公司『怎么运营自己、怎么做决策、怎么招人、怎么创新、怎么规划』的一整套可迁移的管理机制(mechanisms)与心智操作系统。面向想在自己团队/公司引入亚马逊式机制的创始人/CEO/高管/运营负责人(COO)、产品经理与技术产品经理(PM/PMT)、组织与流程设计者(chief of staff / ops)、以及在亚马逊工作或准备面试亚马逊(著名的 LP 行为面试 + Bar Raiser)的人。覆盖: (a) 第一性张力 — 亚马逊 OS 的核心世界观分歧: **机制 >

The English summary is being prepared. Showing the original description.

Guide malware cleanup on infected Windows and Linux systems after containment and investigation. Covers removing malicious files and mechanisms that preserve attacker access, rotating credentials, patching entry points, and documenting validation results before recovery.

• Cleaning infected systems after containment
• Removing mechanisms that preserve attacker access
• Rotating compromised credentials and fixing entry points

Inspect Linux scheduled tasks, services, shell profiles, shared library settings, and SSH keys for mechanisms that maintain attacker access. Correlate findings with audit logs to produce a timeline, risk scores, and remediation commands.

• Investigating how attackers maintained access to a Linux host
• Hunting for suspicious scheduled tasks and services
• Building a timeline from persistence-related audit events

Compare five growth loops, mechanisms where user activity brings in more users, to find a suitable approach for a product. Develop an implementation roadmap, measurement plan, and growth estimates based on sharing, collaboration, content, or referrals.

• Designing product features that attract new users
• Planning growth with less reliance on paid acquisition
• Comparing sharing, collaboration, and referral mechanisms

Analyze software protections during authorized reverse engineering, the examination of compiled programs. Helps identify mechanisms that hinder debugging, obscure code, or prevent tampering, then choose safe analysis methods, document findings, and develop defensive recommendations.

• Analyze protected software with written permission
• Examine malware within an authorized scope
• Study protection mechanisms in CTFs or approved training

Analyze how EDR, software that monitors endpoint threats, and antivirus products detect activity. Support authorized exercises by examining monitoring mechanisms, assessing evasion approaches, and checking detection results in an isolated test environment.

• Assessing EDR detection coverage in authorized exercises
• Examining internal monitoring mechanisms
• Testing an in-house implant against security products

Examine Linux authentication logs, shell history, SSH keys, scheduled tasks, and system settings to investigate a compromise. Help reconstruct activity, identify ways attackers maintain access, and document suspicious accounts, files, and configuration changes.

• Investigating a potentially compromised Linux server
• Finding mechanisms that maintain unauthorized access
• Tracing user activity through logs and command history

Observe malware in an isolated Cuckoo Sandbox environment and review its processes, network traffic, and system changes. Use the findings to trace infection stages, identify persistence mechanisms, and extract indicators of compromise for behavioral reports.

• Investigating suspicious files after static analysis
• Tracing multi-stage infections and persistence mechanisms
• Extracting indicators of compromise from observed behavior

Explore computer science and AI research directions using eight creativity frameworks. Combine ideas across fields, question hidden assumptions, and transfer mechanisms from other disciplines to develop research questions with testable predictions.

• Finding research directions beyond incremental improvements
• Connecting mechanisms across distant disciplines
• Reframing a research problem that feels stuck

Audit groups of bug reports to find shared root causes, checking claims against current code and tests. Produce a cause map, prioritize fixes that remove faulty mechanisms, and document which issues have enough evidence to close.

• Grouping backlog issues by shared root cause
• Checking whether old bug reports still apply
• Comparing fixes that remove faulty mechanisms

Plan persistence testing for authorized Windows and Linux security exercises, examining how access can survive logons or restarts. The skill compares mechanisms by privilege level and environment, with validation steps, detection indicators, and cleanup considerations.

• Planning persistence tests for authorized exercises
• Comparing methods by operating system and privilege
• Reviewing detection indicators for persistence

Query the ChEMBL API for molecules, biological targets, activity records, and mechanisms of action. Search by text or look up an identifier, then receive concise summaries or JSON output when machine-readable results are needed.

• Look up a molecule or target by its ChEMBL identifier
• Retrieve activity records for a molecule
• Review mechanisms of action

Guides implementation of UK international data transfer mechanisms post-Brexit including the International Data Transfer Agreement (IDTA), UK Addendum to EU SCCs, UK adequacy assessments, and ICO transfer risk assessment tool. Keywords: UK IDTA, UK addendum, ICO TRA, post-Brexit transfers, UK GDPR.

The English summary is being prepared. Showing the original description.

Evaluate and compare levitation mechanisms for a given application through a structured trade study. Covers magnetic (passive diamagnetic, active feedback, superconducting), acoustic (standing wave, phased array), aerodynamic (hovercraft, air bearings, Coanda effect), and electrostatic (Coulomb suspension, ion traps) mechanisms. Use when selecting the most appropriate levitation approach for transport, sample handling, display, bearings, or precision measurement applications.

The English summary is being prepared. Showing the original description.

Documents the hook enforcement system, bypass mechanisms, and common failure patterns to help agents avoid getting stuck on protected path writes

The English summary is being prepared. Showing the original description.

"Apply Agency Theory (Jensen and Meckling, 1976) to diagnose principal-agent problems — moral hazard, adverse selection — and design governance mechanisms to align interests. Use this skill when the user needs to analyze conflicts of interest between owners and managers, design incentive or monitoring structures, evaluate corporate governance effectiveness, or when they ask 'how do we ensure managers act in shareholders interest', 'why is this incentive plan failing', or 'what governance mechanisms reduce agency costs'.".

The English summary is being prepared. Showing the original description.

"Apply Bhaskar's critical realism to analyze phenomena through three ontological domains (real, actual, empirical), identify generative causal mechanisms via retroduction, and examine structure-agency interplay. Use this skill when the user needs to go beyond surface correlations to underlying causes, design research that distinguishes mechanisms from events from experiences, or when they ask 'what causes this beyond the observed pattern', 'what structures enable or constrain this behavior', or 'how do I move from correlation to causal explanation'.".

The English summary is being prepared. Showing the original description.

Detect and analyze Linux persistence mechanisms including crontab entries, systemd service units, LD_PRELOAD hijacking, bashrc modifications, and authorized_keys backdoors using auditd and file integrity monitoring

The English summary is being prepared. Showing the original description.

Detect and analyze Linux persistence mechanisms including crontab entries, systemd service units, LD_PRELOAD hijacking, bashrc modifications, and authorized_keys backdoors using auditd and file integrity monitoring

The English summary is being prepared. Showing the original description.

Detect and analyze Linux persistence mechanisms including crontab entries, systemd service units, LD_PRELOAD hijacking, bashrc modifications, and authorized_keys backdoors using auditd and file integrity monitoring

The English summary is being prepared. Showing the original description.

Choose a named creative method suited to the project and stage of work. Generate, expand, compare, or refine ideas with concrete mechanisms, honest tradeoffs, and at least one practical option with a first step.

• Finding starting ideas for writing or products
• Expanding an existing idea
• Getting unstuck during creative work

Review recent code changes from four angles: reuse, quality, efficiency, and whether fixes address underlying mechanisms. Combine findings, apply suitable cleanup with tests, and leave changes that could affect behavior for human review.

• Cleaning up recent code changes
• Finding duplicated logic and reusable helpers
• Reviewing efficiency in the last commit

Design and build AI agents for business, research, operations, or creative work. Define essential actions and knowledge, start with a simple execution loop, and add progress tracking or separate child agents as needs emerge.

• Designing an assistant for business tasks
• Building a research agent
• Choosing essential actions and knowledge

Coordinate specialized AI agents under a lead coordinator for research, development, and review. Configure voting rules, share persistent knowledge, assign tasks, monitor progress, and pause or resume sessions through Claude Flow.

• Divide application development among specialized agents
• Research and compare GraphQL and REST
• Coordinate reviewers for a pull request