gaia-publish

Generate GitHub-ready README analysis from compiled Gaia knowledge packages.

32|9|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/SiliconEinstein/Gaia --skill gaia-publish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gaia-publish
Source: https://github.com/SiliconEinstein/Gaia/tree/main/gaia/_skills/gaia-publish
Command: npx skills add https://github.com/SiliconEinstein/Gaia --skill gaia-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turns a compiled and inferred Gaia knowledge package into a polished GitHub-ready README that communicates scientific conclusions clearly, including evidence strength and internal weak links, without requiring the author to manually restructure or rewrite the outputs from scratch.

Core Features & Use Cases

  • README generation from graph evidence: Produces a per-conclusion evidence-assessment narrative grounded in the latest render outputs, including belief-informed verdicts and structurally coherent ordering.
  • Weak Points and Evidence Gaps authoring guidance: Guides writing focused on internal nodes and uncertainties (not exported conclusions), with thematic grouping to support practical critique and next-step research.
  • Targeted outputs for GitHub vs docs: Uses a single disciplined render verb to generate GitHub README content and a docs-oriented detailed reasoning page, keeping attribution and disclaimers consistent.

Quick Start

Run the GitHub render workflow for your package so it outputs a README skeleton and the structured inputs needed to write the per-conclusion narrative and publish the updated files to your repository.

Frequently Asked Questions about gaia-publish

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

FAQPage Schema
How do I generate a GitHub README from a knowledge graph?

Generate a GitHub README from a knowledge graph by running a render workflow on compiled and inferred knowledge packages, producing narrative conclusions, evidence assessments, and weak link mappings for publication-ready scientific communication.

What is the best way to document evidence gaps and reasoning uncertainties for a domain audience?

Documenting evidence gaps and reasoning uncertainties involves authoring thematic groupings of internal nodes and weak links from inferred knowledge packages, guiding practical critique and identifying next-step research directions for domain audiences.

Can I preserve custom README wrappers when updating documentation from inferred results?

Yes, updating documentation from inferred results preserves user-curated README wrappers during the render step, ensuring custom formatting and introductory sections remain intact while structured scientific conclusions are appended.

How does a reasoning graph translate into structured, evidence-grounded scientific writing?

A reasoning graph translates into structured scientific writing by converting probabilistic reasoning outputs into per-conclusion narratives, belief-informed verdicts, and structurally coherent ordering based on the latest compiled render data.

Do I need a fresh compile and infer step before publishing a knowledge package analysis?

Yes, a fresh compile and infer step is required before publishing a knowledge package analysis, providing the necessary render inputs to generate narrative conclusions, graph data, and evidence assessments for the GitHub README output.

What distinguishes a GitHub README render from a detailed docs-oriented reasoning page?

A GitHub README render focuses on summarized publication-ready scientific communication, while a docs-oriented reasoning page provides detailed reasoning graph data and evidence assessments using the same disciplined render verb for consistent attribution.