forbotsake

Translate technical founder context into a repeatable go-to-market pipeline.

5|1|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/forbotsake/forbotsake --skill forbotsake
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forbotsake
Source: https://github.com/forbotsake/forbotsake/tree/main
Command: npx skills add https://github.com/forbotsake/forbotsake --skill forbotsake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turns a complex GTM workflow into a repeatable system that starts from your codebase context and generates strategy, ICP, content, and publish-ready artifacts.

Core Features & Use Cases

  • Strategy generation from repo context
  • Competitor research, ICP deep dive, and content planning
  • One-command go: run the pipeline end-to-end from any starting state
  • Built-in quality gates and adversarial checks to ensure publish-ready output

Quick Start

Run /forbotsake-go to start the end-to-end GTM pipeline from your current state.

Frequently Asked Questions about forbotsake

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate my go-to-market pipeline from codebase context to published content?

A single-command GTM pipeline automates the end-to-end workflow by translating your codebase context into strategy, ICP definitions, content planning, and publish-ready assets without manual orchestration.

What is the best way to generate an ideal customer profile from a technical repository?

An automated GTM pipeline extracts your repository context, runs competitor research and ICP deep dives, and outputs a structured ideal customer profile ready for content planning and publishing.

Can I run an end-to-end content strategy workflow starting from an incomplete pipeline state?

Yes, the GTM pipeline auto-detects your current pipeline state and executes the remaining stages sequentially to generate strategy, content, and publish-ready artifacts from any starting point.

How does orchestration handle quality control when generating publish-ready marketing assets?

Orchestration enforces quality control by applying built-in gates and adversarial checks across pipeline stages to ensure generated strategy, ICP, and content are traceable and publish-ready.

Does this GTM automation require manual configuration of content calendars and strategy stages?

No manual configuration is required; the pipeline orchestrates strategy generation, content calendar planning, and publishing sub-skills automatically from your initial repository context.

Why use a single-command GTM system instead of separate tools for strategy, ICP, and content publishing?

A single-command GTM system maintains traceability and quality gates across all stages, whereas separate tools break workflow context and require manual orchestration to connect strategy, ICP, and content.