红杉资本投资决策框架
v1.0.0用红杉资本体系系统评估投资机会，包括赛道规模、创始人能力、时机把握、单位经济和生态网络效应分析。
⭐ 0· 55·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description (Sequoia investment framework) match the included SKILL.md and supporting docs. The skill is purely educational/analytical and declares no binaries, installs, config paths, or credentials — appropriate for an advisory checklist.
Instruction Scope
SKILL.md contains decision models, checklists, case studies, and usage guidance. It does not instruct the agent to read unrelated system files, access environment variables, perform network exfiltration, or call external endpoints outside normal agent capabilities. Instructions stay within the stated purpose of analyzing investment opportunities.
Install Mechanism
No install spec and no code files beyond static markdown — lowest-risk delivery model (instruction-only). Nothing will be written to disk by an installer as part of the skill itself.
Credentials
The skill requests no environment variables, credentials, or config paths. The scope of requested access (none) is proportionate to an informational investment-framework skill.
Persistence & Privilege
always:false and default autonomous invocation allowed (normal). The skill does not request persistent system privileges or modifications to other skills. Autonomous invocation combined with no credentials or installs does not create disproportionate risk.
Assessment
This skill is an informational/framework pack (checklists, models, case studies). Before installing, note: 1) It appears to be a third‑party distillation and is not an official Sequoia product — verify attribution/licensing if that matters. 2) Treat outputs as decision-support only (not financial, legal, or compliance advice); validate conclusions with your own diligence. 3) Because the skill can be invoked autonomously by default, avoid granting it additional runtime permissions or hooking it to live systems (banking, signing, deployment) without reviewing any future changes that add network calls or credential requirements. 4) Periodically check the content for staleness or factual errors (case studies and metrics may be dated).Like a lobster shell, security has layers — review code before you run it.
latestvk972x1t5bjnn0ch3yh5vh5td65848bkv
License
MIT-0
Free to use, modify, and redistribute. No attribution required.