global/build-in-public
Build in Public — turn GitHub repo activity into authentic developer storytelling posts.
Category: global
Source: workflows/content/build_in_public.py
Input Schema
Section titled “Input Schema”| Field | Type | Default | Description |
|---|---|---|---|
author_context | string | "" | |
author_name | string | "" | |
github_owner | string | "" | |
github_repo | string | "" | |
github_token | object | — | |
num_posts | integer | 5 | |
platforms | string | "twitter,linkedin,threads,tiktok,youtube" | |
regenerate | object | — | When set, this run is a regeneration. Workflows may read direction / keep / extra_instructions to modulate prompts; the engine persists parent_run_id and parent_variant_index as run lineage columns. |
repo_url | string | "" | |
time_range_days | integer | 30 | |
variants | integer | 1 | Number of independent variant executions (1–10). When > 1, the engine runs the workflow N times with different sampling, producing N outputs. |
voice | string | "conversational" |
Output Schema
Section titled “Output Schema”No schema defined.
Task Pipeline
Section titled “Task Pipeline”validate_input → fetch_readme → fetch_releases → fetch_commits → merge_github_data → extract_story_angles → generate_bip_posts → quality_gate_authenticity → bridge_to_platform_texts → validate_and_refine → format_output| Task | Description |
|---|---|
validate_input | Parse the GitHub repo URL and merge user config with defaults. |
fetch_readme | Fetch the repository README via GitHub Contents API. |
fetch_releases | Fetch recent releases (or tags as fallback) from GitHub. |
fetch_commits | Fetch recent commits from GitHub. |
merge_github_data | Merge parallel GitHub fetch branches into unified context. |
extract_story_angles | Find human stories buried in repo data using BIP archetype vocabulary. |
generate_bip_posts | Generate platform-native build-in-public posts from story angles. |
quality_gate_authenticity | Score posts on BIP authenticity in batches to keep LLM output manageable. |
bridge_to_platform_texts | Reshape bip_posts into the platform_texts schema for validate_and_refine. |
validate_and_refine | Validate generated posts against platform constraints and iteratively refine. |
format_output | Structure the final output, stripping internal keys. |
Run-spec example
Section titled “Run-spec example”Save the YAML below as my-run.yaml, edit the values, and run with the CLI or POST it to the API. Required fields are uncommented; optional knobs are documented above the input: block — copy any line under input: and uncomment to set.
workflow: global/build-in-public
# Optional fields — copy any line(s) under `input:` and uncomment to set:# author_context: ""## author_name: ""## github_owner: ""## github_repo: ""## github_token: null## num_posts: 5## platforms: "twitter,linkedin,threads,tiktok,youtube"## repo_url: ""## time_range_days: 30## voice: conversational#
input: {}Run it locally:
fab-workflow --from-file my-run.yamlOr submit over the wire — the same file is the request body:
curl -X POST 'https://gofabric.dev/v1/workflows/runs?name=global/build-in-public' \ -H 'Authorization: Bearer fab_xxx' \ -H 'content-type: application/yaml' \ --data-binary @my-run.yamlEvery workflow also accepts the universal WorkflowInput fields — variants (1–10 fan-out) and regenerate (creative-direction hints with run lineage). See Run-specs (YAML / TOML / JSON) for the full top-level shape (metadata, priority, bundle, parent, etc.).
Warnings
Section titled “Warnings”- Last user task
format_outputhas no Pydantic return type — workflow output schema is null. Declare a WorkflowOutput subclass and pass it to Flow(output=…) for a strict contract. - Task
merge_github_datahas no Pydantic types — contract is opaque to consumers.