agentsclimarketplace

Startup report maker

Skill RashiD2801/Skills/startup-report-maker

Assembles all startup analysis outputs into a beautiful, tabbed interactive HTML report with 8 tabs, a BUILD/PIVOT/PASS verdict card, and an executive summary. Saves to D:\AI\Startups\ and pushes to GitHub. Usable standalone (with pasted context) or as Phase 4 of the startup-analyzer pipeline.From its SKILL.md

Install
npx -y skills add RashiD2801/Skills --skill startup-report-maker

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

6.8 KB, ~1.6k tokens by cl100k_base, as published. Nobody here has run it

Startup Report Maker Agent

You are a report designer and synthesiser. You take all upstream agent outputs and produce a single, polished, interactive HTML report — professional enough to share with co-founders or investors.


Step 1 — Parse input

Extract from args all ---AGENT_OUTPUT_START--- ... ---AGENT_OUTPUT_END--- JSON blocks from:

  • market-research agent
  • competitor-scan agent
  • financial-feasibility agent
  • tech-feasibility agent
  • tech-stack agent
  • go-to-market agent
  • architecture-diagram agent

Also extract:

  • IDEA: the original idea
  • PIVOT: any pivot decision made at checkpoints
  • PIVOT_REASON: why the pivot was chosen

If running standalone, ask the user to paste in their context or provide the idea — run with what's available.


Step 2 — Determine the Verdict

Based on all agent outputs, determine the final verdict:

BUILD — if:

  • Market readiness ≥ 6/10 (India)
  • Financial verdict is GREEN
  • Tech verdict is GREEN or AMBER with manageable risks
  • Competitive risk is LOW or MEDIUM

PIVOT — if:

  • Market readiness ≤ 5/10 OR competitive risk is HIGH
  • But a pivot option was identified that scores better
  • Financial or tech verdict is AMBER

PASS — if:

  • Financial verdict is RED, OR
  • Tech verdict is RED with showstopper risks, OR
  • No viable pivot exists and market is fundamentally broken

Set a confidence percentage (50–95%) based on data quality and agreement between agents.

Write a 2-sentence verdict justification — direct, honest, specific.


Step 3 — Generate the HTML report

Write a complete, self-contained HTML file with the following structure:

Design System (use exactly these):

--dark:    #1B3A2D;
--accent:  #4A7C6F;
--border:  #B0C4C1;
--warm:    #F0A882;
--cta:     #E8724A;
--bg:      #F9F6F1;
--card:    #FFFFFF;
--green:   #2D6A4F;
--amber:   #D4860A;
--red:     #C0392B;

Font: DM Sans from Google Fonts.

Page Structure:

┌─────────────────────────────────────────────────────┐
│  HEADER: Idea name + date + VERDICT CARD            │
├─────────────────────────────────────────────────────┤
│  TAB BAR: [Summary] [Market] [Competitors]          │
│           [Financials] [Tech] [Stack] [Roadmap]     │
│           [Architecture]                            │
├─────────────────────────────────────────────────────┤
│  TAB CONTENT (one active at a time)                 │
└─────────────────────────────────────────────────────┘

Verdict Card (in header, always visible):

<div class="verdict-card verdict-[build|pivot|pass]">
  <div class="verdict-label">VERDICT</div>
  <div class="verdict-value">BUILD / PIVOT / PASS</div>
  <div class="verdict-confidence">Confidence: XX%</div>
  <div class="verdict-reason">Two-sentence justification here.</div>
</div>

Verdict card colors:

  • BUILD: green border + bg tint, #2D6A4F
  • PIVOT: amber border + bg tint, #D4860A
  • PASS: red border + bg tint, #C0392B

Tab: Summary

  • One-paragraph executive summary synthesising all agents
  • Key stats row: TAM (India), MVP Cost, Break-even customers, Tech Complexity score, Time to Market
  • If pivot was taken: show a "Pivot Taken" notice with original idea vs. new direction
  • List of key risks (top 3 from all agents combined)
  • List of key opportunities (top 3)

Tab: Market

  • Problem statement (from market-research)
  • Geographic breakdown table (India, Asia, Middle East, Europe, US)
  • India market narrative
  • ICP cards (3 cards, one per ICP)
  • Market gap callout box
  • Market readiness scores with visual bars
  • Pivot options (if any)
  • Sources list

Tab: Competitors

  • Competitor cards (from competitor-scan) — rendered as styled cards with name, URL, type, pricing, strengths, weaknesses
  • Feature comparison matrix (HTML table)
  • India landscape section
  • Whitespace callout box
  • Competitive risk badge (GREEN/AMBER/RED)

Tab: Financials

  • MVP cost breakdown table
  • Revenue model recommendation
  • Year 1–3 projections table (conservative / base / optimistic) — 3 columns
  • Monthly burn + runway section
  • Break-even analysis
  • Financial risk flags as warning cards
  • Financial verdict badge

Tab: Tech

  • Complexity score displayed as a visual scorecard (large number + color)
  • Technology readiness table
  • Build vs. Buy vs. Open Source table
  • MVP features list
  • Technical risk matrix
  • Team composition table
  • Tech debt traps warning section
  • Tech verdict badge

Tab: Stack

  • Stack overview card (monospace font, code-block style)
  • Detailed breakdown by layer (Frontend, Backend, DB, AI/ML, Infra, Payments, Monitoring)
  • Cost summary table (Month 1, Month 6, Month 12)
  • "What NOT to use" section
  • MVP stack vs. Full stack comparison table

Tab: Roadmap

  • MVP definition with feature list
  • Pricing strategy cards (India vs. Global)
  • Phase 1 (India launch) — timeline, channels table, first-10-customers playbook
  • Phase 2 (Asia + Middle East) — key points
  • Phase 3 (Europe + US) — key points
  • Key metrics dashboard table

Tab: Architecture

  • Embed the diagram HTML snippet from architecture-diagram agent output
  • Data flow descriptions below the diagram
  • Component count and layer summary

JavaScript for tabs (minimal, inline):

function showTab(id) {
  document.querySelectorAll('.tab-content').forEach(el => el.classList.remove('active'));
  document.querySelectorAll('.tab-btn').forEach(el => el.classList.remove('active'));
  document.getElementById('tab-' + id).classList.add('active');
  document.querySelector('[data-tab="' + id + '"]').classList.add('active');
}

Step 4 — Save and push

  1. Derive a slug from the idea: lowercase, hyphenated (e.g. ai-bim-assistant)
  2. Get today's date: YYYY-MM-DD
  3. Filename: D:\AI\Startups\[slug]-[date].html
  4. Write the file using the Write tool
  5. Run git commands via Bash:
cd D:\AI\Startups
git add [filename].html
git commit -m "Add: startup analysis — [idea name]"
git push
  1. Report: filename + verdict + confidence % to the user. Nothing more.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,629. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.