AGENT SKILL
product-business-kit
Use when making a product a full business package.
- License 许可
- MIT
- 最近更新
- 2026-08-16
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- product-business-kit
- author
- Hermes curator
- license
- MIT
- version
- 1.0.0
- metadata
- { "hermes": { "tags": [ "business", "market-research", "brand", "pitch-deck", "content", "audience", "go-to-market" ], "related_skills": [ "brand-symbol-design", "pitch-deck-builder", "underoos-briefing" ] } }
- platforms
- [ "linux", "macos", "windows" ]
- description
- Use when making a product a full business package.
02 资源文件 3
- 参考文档references/drive-dataroom-sync.md2.5 KB
- 参考文档references/siafu-package-v1.md4.8 KB
- 脚本templates/sync_to_drive.sh2.2 KB
03 SKILL.md 正文
Product Business Kit (full package)
When to Use
- "Make X a full brand and business", "prepare the pitch deck and all the assets", "find market and the pain point and the customers", "find me audience for my product".
- Ibrahim's products (Siafu, Olive, JengaConnect, Ghost, KukuPlus...) that need the complete package: research → brand → deck → content → audience → delivery index.
Build a complete business package for a product from repo truth: research → brand → deck → content → audience → delivery index.
Workflow (8 phases, in order)
- Product truth first — read the repo's README + design docs + BOM before any research. Never invent specs; quote the design doc (dimensions, BOM cost, sensors, algorithm names, current status table). This grounds every later claim.
- Parallel market research — batch 6–8 firecrawl searches in ONE turn: market size (category + adjacent), competitor pricing (name + $ per unit + business model), regional problem statistics, regional funding, education/adjacent markets. Distill to a table, don't dump raw results. Always note source + year per figure.
- Write
BUSINESS-RESEARCH.md— fixed structure: exec summary table → product truth (specs, status) → market size + problem quantified → competition (price-gap table: competitor price vs our BOM) → 5 customer segments each with pain points + how to sell → revenue model (3 phases) + unit economics → go-to-market (90-day plan, risks) → funding map → KPI targets. Flag figures that vary across firms. - Brand kit — delegate to
brand-symbol-designskill: 3 directions → geometry-first SVG → color/mono/reversed variants → size-test strip (96→24px) → pixel-probe verification (all probes must PASS before delivery). Brand doc: name story (incl. local proverb if the name is Kiswahili), taglines, voice rules, palette, symbol rationale + usage rules. - Pitch deck — delegate to
pitch-deck-builder: 12-slide arc (Title → Problem → Market → Why-now → Solution → Product → Revenue → Competition → Why-now-rails → Customers → Roadmap → Close), dark title/close, footer citations on every content slide. Runqa_pptx.py; then re-export a PDF preview explicitly (see pitfall below). - Content pack — 4 content pillars (problem / technology / story / business), 15 ready-to-post pieces spanning X threads, TikTok/Reel scripts, LinkedIn posts; platform cadence table; 30-day calendar; caption skeleton; brand-voice rules.
- Audience map — segments → channels matrix (where each segment lives online + how to reach), communities to join, influencer/account engagement targets, events calendar, copy-paste outreach email templates per segment, funnel + KPIs, and a "where the money actually is" priority order.
- README index + delivery — README.md table of every file, 3-line pitch, next-actions checklist (with real deadlines). Deliver with absolute paths + MEDIA: links for the key files (research doc, deck pptx+pdf, symbol png).
- Landing page (promo sites) — single-file 3D scroll page via
scroll-driven-3d-websites(hero-variant pattern: OrbitControls + procedural product model + entrance cascade +gsap.matchMedia()for mobile/reduced-motion). Use the product's Phalanx-style symbol as inline-SVG favicon/nav/logo data URIs. If the user supplies a Sketchfab embed, include it with attribution intact. Verify: nodenew Functionsyntax check on the module script, serve on localhost,open_preview+read_previewto confirm render. Ship aslanding/index.htmlin the package. - Google Drive data-room sync — search for the existing data room FIRST (
drive search "data room"), respect its numbered-folder structure, add the product as one self-contained project folder. Generatescripts/sync_drive.sh(pattern inreferences/drive-dataroom-sync.md, starter intemplates/sync_to_drive.sh), run it, then VERIFY by listing each folder back from Drive. Add the folder link + resync command to the README and the folder IDs to memory.
Pitfalls
qa_pptx.pydeletes its PDF — it renders to a temp dir (mkdtemp) that's removed on exit, so the deck folder gets no PDF. To deliver a PDF preview: re-run the LibreOffice conversion explicitly with--outdir <deckdir>(soffice wrapper from the pptx skill:env -u PYTHONPATH python3 ~/.hermes/skills/pptx/scripts/office/soffice.py --headless --convert-to pdf --outdir . Deck.pptx), thenpdftotextgrep for key claims to verify.- Vision provider may reject images (
unknown variant 'image_url') — do NOT retry in a loop. Fall back to deterministic pixel probes (brand-symbol-design has the script pattern) + text-layer checks. - Dates rot — funding deadlines (e.g. Milken-Motsepe Aug 13 2026) and market figures age. Always carry source + date with every number; re-verify deadlines before quoting in a fresh session.
- Check the vault first —
search_filesthe Maarifu vault for an existing product note/brief before starting; the pitch-deck-builder skill mines01. Companies/<Product>/and08 Research Lab/Market Research/. - Keep the generators — build_symbol.py and build_deck.js stay in the package dir so revisions regenerate from the same script (brand-symbol-design + pitch-deck-builder both require this).
- Memory is the pointer, not the package — record only the package path in memory (
~/Projects/<product>-business/); the docs themselves live in the package. - Drive JSON is a dict, not an object — parsing
google_api.pyoutput in bash helpers:json.load(sys.stdin).idraisesAttributeError: 'dict' object has no attribute 'id'; use subscriptjson.load(sys.stdin)['id']. Write the helper right the first time. - Drive rate limits on rapid loops — tight sequential
drive search/uploadcalls return EMPTY responses →JSONDecodeError: Expecting value. Space calls (sleep 2–3between) or batch per command. - Verify by listing back — "upload ok" is not proof. After sync, query each folder (
'<folder_id>' in parentsraw query) and confirm counts/names from Drive itself before telling the user it's synced. - Trash, never permanent, for test folders — if debugging left a stray folder,
drive delete(default trash) is reversible; don't use--permanenton an accident.
Support files
references/siafu-package-v1.md— Siafu v1 case: verified market figures with sources, competitor pricing, problem stats, segment structure, funding map, deliverable paths.references/drive-dataroom-sync.md— the Drive data-room sync workflow: folder discovery, structure rules, sync-script pattern, verification, rate-limit + JSON-parse gotchas.templates/sync_to_drive.sh— known-good idempotent sync script (folder creation + upload) to copy and adapt per product.
04 同仓库更多 Skills
web-ui-verification
Verify web UIs via headless Chrome CDP, no vision needed.
★ 0
test-driven-development
TDD: enforce RED-GREEN-REFACTOR, tests before code.
★ 0
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
★ 0
spike
Throwaway experiments to validate an idea before build.
★ 0
simplify-code
Parallel 4-agent cleanup of recent code changes.
★ 0
scroll-driven-3d-websites
Scroll-scrubbed 3D promo sites (Three.js + GSAP).
★ 0