close

星标5

分支1

更新时间2026年7月7日 21:21

Close an acquisition: create the Deal + Business + Interface(s) (GATE 2: go/no-go is the user's).

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

来源

Play-New

Play-New/bending-spoons-ontology

打开 GitHub 仓库查看创作者相关仓库

下载

相关职业SOC

基于 SOC 职业分类

财务和投资分析师商业与金融运营类职业·SOC 13-2051

SKILL.md

readonly

name	close
description	Close an acquisition: create the Deal + Business + Interface(s) (GATE 2: go/no-go is the user's).

Execute the close verb of the Bending Spoons world model, per its contract.

Read the contract: capabilities/actions/deal-diligence.md — parameters, submission criteria, gate. Follow it exactly.
Gather the parameters from the user/context (ask only for what the contract requires and you cannot read from the model itself). Before proposing, prefer running the deal-diligence agent (it ranks and verifies the assumptions behind the approved walk-away price and drafts the exact close params).
Propose (phase 1 — writes nothing): python3 -c "import sys; sys.path.insert(0,'mcp'); import engine, json; print(json.dumps(engine.propose('close', PARAMS), indent=2))" If the engine REFUSES, report the refusal verbatim — it is a submission criterion firing (a will constraint or an invariant), not an error to work around.
Show the user: the checks, the gate, and the exact diff. GATE 2: the go/no-go is the user's; consider running the deal-diligence agent first.
Only on the user's explicit yes, apply (phase 2): python3 -c "import sys; sys.path.insert(0,'mcp'); import engine; print(engine.apply('PROPOSAL_ID', 'USER_NAME'))" The engine runs the audit and commits if green; report the outcome. Never edit the csvs directly.

同仓库更多 Skills

同仓库

radar-sweep

Play-New/bending-spoons-ontology

The market-radar's sensing pass — sweep recent public signal (HN + Reddit, free, recency-windowed) on a company or theme and bucket every hit against the contract's watch signals (distress, ownership, momentum, valuation, AI-pressure). Use to scout a candidate or refresh the pipeline.

2026-07-085

bsp-audit

Play-New/bending-spoons-ontology

Run the model's audit (the model's audit service, mechanical subset) and summarize — green/red, defects with the invariant each violates. Run after any batch of edits.

2026-07-075

deal-desk

Play-New/bending-spoons-ontology

The desk over the whole deal machine — pipeline status, pending proposals, and which verb applies next. Start here ("/deal-desk") to see the state and be guided to the right action skill.

2026-07-075

hire

Play-New/bending-spoons-ontology

The hiring assistant — run a candidate through Bending Spoons' selection funnel and score them against the disclosed gates. Read-only, advisory: it drafts a recommendation; the committee decides. The people-side twin of screen-target.

2026-07-075

screen

Play-New/bending-spoons-ontology

Screen a Target against the hard gates (the screen verb). Applies auto — the write IS the screen.

2026-07-075

source

Play-New/bending-spoons-ontology

Create a new Target in the pipeline (the source verb). Human-gated: admission needs the user's approval.

2026-07-075

name	close
description	Close an acquisition: create the Deal + Business + Interface(s) (GATE 2: go/no-go is the user's).

Execute the close verb of the Bending Spoons world model, per its contract.

Read the contract: capabilities/actions/deal-diligence.md — parameters, submission criteria, gate. Follow it exactly.
Gather the parameters from the user/context (ask only for what the contract requires and you cannot read from the model itself). Before proposing, prefer running the deal-diligence agent (it ranks and verifies the assumptions behind the approved walk-away price and drafts the exact close params).
Propose (phase 1 — writes nothing): python3 -c "import sys; sys.path.insert(0,'mcp'); import engine, json; print(json.dumps(engine.propose('close', PARAMS), indent=2))" If the engine REFUSES, report the refusal verbatim — it is a submission criterion firing (a will constraint or an invariant), not an error to work around.
Show the user: the checks, the gate, and the exact diff. GATE 2: the go/no-go is the user's; consider running the deal-diligence agent first.
Only on the user's explicit yes, apply (phase 2): python3 -c "import sys; sys.path.insert(0,'mcp'); import engine; print(engine.apply('PROPOSAL_ID', 'USER_NAME'))" The engine runs the audit and commits if green; report the outcome. Never edit the csvs directly.