solo-stream
Skill18 starsChanged 4 months agoMITView on GitHub
Use when "help me decide", "should I do this", "evaluate decision", "STREAM analysis", "run decision framework", "pros and cons", or facing a high-stakes founder choice. Do NOT use for idea validation with PRD (/validate).
In this repository62 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- solo-android-releaseSkill
- solo-apple-app-iconSkill
- solo-auditSkill
- solo-boardSkill
- solo-buildSkill
- solo-community-outreachSkill
- solo-content-genSkill
- solo-creator-growthSkill
- solo-customer-finderSkill
- solo-deep-researchSkill
- solo-deploySkill
- solo-diagnoseSkill
- solo-domainSkill
- solo-factorySkill
- solo-github-outreachSkill
- solo-gmail-cliSkill
- solo-grillSkill
- solo-hackathonSkill
- solo-humanizeSkill
- solo-i18nSkill
- solo-index-youtubeSkill
- solo-initSkill
- solo-ios-devSkill
- solo-ios-releaseSkill
- solo-kaggle-gpuSkill
- solo-kindleSkill
- solo-knowledgeSkill
- solo-landing-genSkill
- solo-launchSkill
- solo-legalSkill
- solo-memory-auditSkill
- solo-metrics-trackSkill
- solo-mirrorSkill
- solo-model-shrinkSkill
- solo-music-reels-cutSkill
- solo-open-datasetSkill
- solo-paperSkill
- solo-pdf-printSkill
- solo-pipelineSkill
- solo-planSkill
- solo-redditSkill
- solo-researchSkill
- solo-retroSkill
- solo-reviewSkill
- solo-scaffoldSkill
- solo-secretsSkill
- solo-seo-auditSkill
- solo-seo-cliSkill
- solo-setupSkill
- solo-sgrSkill
- solo-skill-auditSkill
- solo-skill-shelfSkill
- solo-stem-splitSkill
- solo-supervoxSkill
- solo-swiftui-design-systemSkill
- solo-transcribeSkill
- solo-validateSkill
- solo-video-editSkill
- solo-video-promoSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
If MCP kb_search available: kb_search(query="STREAM framework", n_results=3) for full framework details.
- Very specific: line 72
Write to docs/decisions/ in the current project directory
- Distinctive: line 107
Fix: Start with a concrete decision statement: "Should I [action] given [context]?" not just "What should I do?"
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/stream
Interactive wizard that walks any decision through the STREAM 6-layer framework. Designed for founders making high-stakes choices under uncertainty.
Steps
- Parse the decision from
$ARGUMENTS. If empty, ask: "What decision or dilemma do you want to analyze?" - Load framework context (optional enhancement):
- If MCP
kb_searchavailable:kb_search(query="STREAM framework", n_results=3)for full framework details. - Otherwise, the framework is embedded below.
- If MCP
- Walk through 6 layers interactively. For each layer, explain the concept, ask a clarifying question via AskUserQuestion, then provide assessment.
Layer 1 — Epistemological (Knowledge)
- Is this within your circle of competence?
- What assumptions are unproven?
- What would change your mind?
- Ask: "What do you know for certain about this space? What are you assuming?"
Layer 2 — Temporal (Time)
- What's the time horizon for results?
- Is this Lindy-compliant (will it matter in 10 years)?
- Reversibility: can you undo this in 6 months?
- Ask: "What's your timeline? Is this a 3-month experiment or a 3-year commitment?"
Layer 3 — Action (Minimum Viable)
- What's the smallest possible first step?
- What are second-order effects?
- Can you test this in a weekend?
- Ask: "What's the minimum viable version you could ship in 1-2 weeks?"
Layer 4 — Stakes (Risk/Reward)
- Asymmetric upside? (small downside, large upside)
- Survivable worst case?
- Opportunity cost of NOT doing this?
- Ask: "What's the worst realistic outcome? Can you survive it financially and emotionally?"
Layer 5 — Social (Network)
- Reputation impact on your network?
- Network effects or viral potential?
- Does this build social capital?
- Ask: "Who benefits besides you? Who might be hurt?"
Layer 6 — Meta (Mortality Filter)
- Is this worth your finite time on earth?
- Does this align with your values?
- Will you regret NOT trying this?
- Ask: "If you had only 5 years left, would you still do this?"
- Synthesize verdict:
- Score each layer 1-10
- Overall STREAM score (weighted average)
- GO (score > 7) / PAUSE (5-7) / NO-GO (< 5)
- Key risk to mitigate
- Recommended first action
- Capture the decision (optional): Offer to save the decision record. If user wants to save:
- Write to
docs/decisions/in the current project directory - Format: date + decision summary + verdict
- Write to
- Output structured decision journal:
## Decision: [topic] **Date:** [today] **Framework:** STREAM 6-layer ### Analysis Summary | Layer | Score | Key Finding | |-------|-------|-------------| | Epistemological | X/10 | ... | | Temporal | X/10 | ... | | Action | X/10 | ... | | Stakes | X/10 | ... | | Social | X/10 | ... | | Meta | X/10 | ... | **Overall STREAM Score: X/10 — GO/PAUSE/NO-GO** ### Recommendation [Clear recommendation with reasoning] ### Next Actions 1. [action] 2. [action] 3. [action]
Common Issues
Questions feel too abstract
Cause: Decision not specific enough. Fix: Start with a concrete decision statement: "Should I [action] given [context]?" not just "What should I do?"
Score seems wrong
Cause: Layers weighted equally but some matter more for this decision. Fix: The overall score is a starting point. Pay more attention to the layers most relevant to your situation (e.g., Stakes for financial decisions, Meta for life choices).
Want to save the decision record
Cause: Running in a project without a docs/decisions/ directory.
Fix: Skill saves to docs/decisions/ in the current project. Create the directory if needed.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

