screen

Étoiles5

Forks1

Mis à jour7 juillet 2026 à 21:21

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

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

Play-New

Play-New/bending-spoons-ontology

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes financiers et en placementsProfessions des affaires et des opérations financières·SOC 13-2051

SKILL.md

readonly

name	screen
description	Screen a Target against the hard gates (the screen verb). Applies auto — the write IS the screen.
disable-model-invocation	true

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

Read the contract: capabilities/actions/screen-target.md — parameters, submission criteria, gate. Follow it exactly.
ESTIMATE THE GATES with the radar's structured tiers before asking the user anything:
- US-listed candidate → python3 .claude/skills/radar-sweep/scripts/radar_sweep.py "TKR" --gates (revenue band · HQ · sector, [derived] from EDGAR)
- EU-listed / unknown → ... "Legal Name" --company (GLEIF → ESEF chain; honest n.d. for privates)
- private → the press recipes in the radar-sweep skill (triangulate ≥2 sources; everything [to-validate — press only]) + --loyalty "Brand" as the predictable-earnings proxy (rating base · interest trend · community) Fill the nine gate values from these, marked by provenance; ask the user only for what remains.
Propose (phase 1 — writes nothing): python3 -c "import sys; sys.path.insert(0,'mcp'); import engine, json; print(json.dumps(engine.propose('screen', 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. screen applies auto (no approver needed): the write is the screen itself; admission to underwriting stays human.
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.

Plus depuis ce dépôt

même dépôt

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

Play-New/bending-spoons-ontology

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

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

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	screen
description	Screen a Target against the hard gates (the screen verb). Applies auto — the write IS the screen.
disable-model-invocation	true

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

Read the contract: capabilities/actions/screen-target.md — parameters, submission criteria, gate. Follow it exactly.
ESTIMATE THE GATES with the radar's structured tiers before asking the user anything:
- US-listed candidate → python3 .claude/skills/radar-sweep/scripts/radar_sweep.py "TKR" --gates (revenue band · HQ · sector, [derived] from EDGAR)
- EU-listed / unknown → ... "Legal Name" --company (GLEIF → ESEF chain; honest n.d. for privates)
- private → the press recipes in the radar-sweep skill (triangulate ≥2 sources; everything [to-validate — press only]) + --loyalty "Brand" as the predictable-earnings proxy (rating base · interest trend · community) Fill the nine gate values from these, marked by provenance; ask the user only for what remains.
Propose (phase 1 — writes nothing): python3 -c "import sys; sys.path.insert(0,'mcp'); import engine, json; print(json.dumps(engine.propose('screen', 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. screen applies auto (no approver needed): the write is the screen itself; admission to underwriting stays human.
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.