Token导航 LogoToken导航

Agent Skill · 待分类

running-decision-processes(运行决策过程)

running-decision-processes 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

running-decision-processes 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在待分类类的 11,209 个 Skill 里排第 4,445。

总安装 742周安装 30GitHub Stars 3下载 233核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:running-decision-processes(运行决策过程)
来源仓库:https://github.com/oldwinter/skills
仓库路径:skills/running-decision-processes
安装命令:
npx skills add https://github.com/oldwinter/skills --skill running-decision-processes
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/oldwinter/skills --skill running-decision-processes

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

用于处理 GitHub 仓库、Issue 和 Pull Request 协作信息。适合围绕代码变更和仓库状态进行整理与分析。可结合来源仓库 README 核验具体用法和权限范围。安装前建议确认是否会触发命令执行或文件读写操作。

running-decision-processes 属于待分类类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/running-decision-processes

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/oldwinter/skills --skill running-decision-proc…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

running-decision-processes 怎么安装?

在终端执行 npx skills add https://github.com/oldwinter/skills --skill running-decision-processes。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

running-decision-processes 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

running-decision-processes 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

running-decision-processes 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

running-decision-processes 用的人多吗?

公开数据是累计安装 742 次,近一周安装 30 次,下载 233 次,GitHub 3 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

running-decision-processes 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理待分类类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

待分类类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
infsh-cli

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
running-decision-processes

运行决策过程 · 本页

7423需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Running Decision Processes

Scope

Covers

  • Running an end-to-end decision process for a cross-functional, high-stakes, or high-ambiguity decision
  • Making implicit assumptions explicit (so they can be tested and reviewed later)
  • Avoiding “decision drift” (hesitation, hidden vetoes, unclear decision rights)
  • Capturing durable artifacts: decision brief, roles, meeting plan, decision log, comms, and a review loop

When to use

  • “Draft a decision memo / pre-read and run the decision meeting.”
  • “We’re stuck between two bad options—help us decide and commit.”
  • “Set up RAPID/DACI/RACI for this decision and clarify who decides.”
  • “Create an options + criteria matrix and a decision log entry.”
  • “This feels like a one-way door / irreversible decision—tighten the process.”

When NOT to use

  • You need to decide what problem to solve (do problem definition first).
  • You need prioritization across many opportunities (use a roadmap/prioritization workflow).
  • The “decision” is actually a status update or routine coordination (use a meeting/operating cadence).
  • The decision is personal/legal/HR or requires specialist counsel (escalate to humans and domain experts).

Inputs

Minimum required

  • Decision to make (one sentence) and decision deadline (or “no later than” date)
  • Context/why now (what changed; what happens if you don’t decide)
  • Scope boundaries + non-negotiables (policy, budget, timeline, customer commitments)
  • Stakeholders and required approvers (who can block / who must live with the outcome)
  • Current options under consideration (even if rough) and key uncertainties

Missing-info strategy

  • Ask up to 5 questions from references/INTAKE.md.
  • If answers are unavailable, proceed with explicit assumptions and label unknowns.

Outputs (deliverables)

Produce a Decision Process Pack (Markdown in-chat, or files if requested) in this order:

  1. Decision Brief / Pre-read (problem, context, decision statement, constraints, criteria, options, recommendation if any)
  2. Options + Criteria Matrix (including assumptions/unknowns that drive the choice)
  3. Decision Rights + Process (RAPID/DACI/RACI, roles, timeline, meeting plan)
  4. Decision Log Entry (decision, rationale, tradeoffs, assumptions, owner, review date)
  5. Decision Communication (announcement + what changes + next steps)
  6. Decision Review Plan (what to measure, when to revisit, how to learn)
  7. Risks / Open questions / Next steps (always included)

Templates: references/TEMPLATES.md

Workflow (8 steps)

1) Classify the decision (speed vs rigor)

  • Inputs: Decision statement (draft); deadline; stakes.
  • Actions: Classify as one-way door (hard to reverse) vs two-way door (reversible). Set a timebox and required rigor (light/standard/heavy). Name the failure cost (what’s the worst credible outcome?).
  • Outputs: Decision classification + process intensity + timebox.
  • Checks: The process chosen matches reversibility and stakes (no “heavy process” for reversible choices; no “wing it” for irreversible ones).

2) Make the decision explicit (anti-hesitation)

  • Inputs: Context/why now; constraints; success criteria.
  • Actions: Turn implicit debate into a crisp decision: “We are deciding X by date to achieve Y.” List non-negotiables and what “good” means.
  • Outputs: Decision Brief sections: Decision statement, Why now, Success criteria, Constraints.
  • Checks: A stakeholder can restate the decision in one sentence without adding qualifiers.

3) Gather context (historian pass)

  • Inputs: Prior docs; past decisions; stakeholder perspectives.
  • Actions: Reconstruct relevant history (what was tried, what failed, and why). Surface “baggage” and hidden constraints. Collect only the decision-relevant facts.
  • Outputs: Decision Brief sections: Background, Prior decisions + rationale, Known constraints.
  • Checks: The brief distinguishes facts vs assumptions vs opinions.

4) Generate options + criteria; log assumptions

  • Inputs: Candidate options; goals; constraints.
  • Actions: Define evaluation criteria and (if helpful) weights. Expand to 2–4 viable options (including “do nothing” if appropriate). For each option, make key assumptions explicit (what must be true for this to work?).
  • Outputs: Options + Criteria Matrix; Assumptions/Unknowns list.
  • Checks: Each option has at least 2–3 explicit assumptions; criteria reflect actual tradeoffs (not “everything is important”).

5) Design the decision process + decision rights

  • Inputs: Stakeholder list; org constraints; decision intensity.
  • Actions: Choose a decision-rights model (RAPID/DACI/RACI). Assign roles (who recommends, who decides, who must be consulted, who is informed). Create a tight plan: pre-read, input window, meeting, decision capture, comms.
  • Outputs: Decision Rights + Process doc; meeting plan.
  • Checks: There is exactly one Decider (or a clearly defined decision body), and veto power is explicit.

6) Run a “curiosity loop” (contextual advice)

  • Inputs: Key unknowns; list of 8–12 people to consult (mix of experts + context-aware peers).
  • Actions: Ask lightweight, specific questions that demand rationale (“pick top 2 and why”, “what would change your mind?”). Capture inputs, disagreements, and decision-relevant evidence. Update options/assumptions accordingly.
  • Outputs: Curiosity Loop input summary; updated matrix/assumptions.
  • Checks: Inputs are specific and actionable (not generic opinions); dissent is recorded, not smoothed over.

7) Decide and commit (document the why)

  • Inputs: Final brief + matrix; role assignments; meeting agenda.
  • Actions: Run the decision meeting (or async decision) with a bias toward clarity. Make the decision explicit, name the tradeoffs, assign an owner, and set a review date. Document rationale and what would cause a revisit.
  • Outputs: Decision Log Entry; committed next steps; decision announcement draft.
  • Checks: The decision and owner are unambiguous; the team knows what changes tomorrow.

8) Communicate, execute, and review (learning loop)

  • Inputs: Decision log; implementation plan; metrics.
  • Actions: Send the decision communication. Translate into tasks/milestones. Schedule a review to compare outcomes vs assumptions and capture learning (keep “intuition” testable).
  • Outputs: Sent comms (or ready-to-send); review plan; retrospective prompts.
  • Checks: A review date and measurement plan exist; assumptions are testable and tracked.

Quality gate (required)

Examples

Example 1: “We need to decide whether to sunset Feature X by March 15. Create a decision memo, run a RAPID decision process, and draft the announcement.” Expected: Decision Brief + options/criteria matrix + RAPID roles + decision log entry + comms + review plan.

Example 2: “We’re split on building vs buying an analytics tool. It’s a one-way door. Set up a rigorous process and capture assumptions so we can learn.” Expected: One-way door classification + weighted criteria + assumptions log + consultation loop + decision log with review date.

Boundary example: “Help me decide if I should change careers.” Response: This skill is for organizational product/leadership decisions; suggest a personal decision framework or coach instead.

平台分布

Codex

33.83%
按下载量换算79

Claude

32.45%
按下载量换算76

Cursor

17.2%
按下载量换算40

Gemini CLI

10.09%
按下载量换算24

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills