TiangongLocal LLM × Robot Plays
中文
  • Agents
  • Beginner
  • ✓ Tested

Let your Agent publish local-model plays to Tiangong

Turn links and deployment notes into reviewed articles through the Tiangong content API.

Let your Agent publish local-model plays to Tiangong
Tools
HTTP API, Agent
Original source
spark.tlec.top

What this workflow does

Give your Agent links, deployment notes, and local-model experiments. The Agent can turn them into articles, save drafts to Tiangong, and publish through an authenticated HTTP API.

Credentials

Use the Tiangong content token to manage the website. The model provider API key is a separate credential used only by the backend for summarization and translation. Never include either credential in an article or public repository.

Start with your Agent

Ask your Agent to read https://spark.tlec.top/agent.md. Provide its content token through a private local configuration file, then ask it to preserve sources, extract supported steps, and save a draft. Mark an experiment as tested only when you have actually verified it. Give publishing authorization when the draft is ready.

The Agent should read the linked source and supply its text. A URL alone is saved to the inbox; the website does not invent a tutorial from a title.

Use the dashboard

Open Content management and connect with your content token. Paste a source URL and notes into the inbox. When the text model is configured and enough source text is present, the backend can prepare Chinese and English drafts for review.

You can also write a title, an English URL slug, and a Markdown body directly. English is optional; a Chinese-only article can be published.

API sequence

  1. Submit raw material with POST /api/v1/submissions, or a prepared article with POST /api/v1/content.
  2. Read an item with GET /api/v1/content/{id}. Supply its current expectedRevision when updating it.
  3. Request publication with POST /api/v1/content/{id}/publish.
  4. Poll GET /api/v1/jobs/{jobId} until it succeeds or fails. A 202 response only confirms that the job was queued. Open the returned URL after success.

Publishing rebuilds both pages and the search index, then switches to the new release. A failed build keeps the previous live version.

Scheduled collection

Collection runs daily at 08:00 Asia/Taipei using the configured GitHub Releases, RSS, and Hacker News sources. Source URLs are deduplicated. Candidates with sufficient source text can become bilingual drafts; external discoveries require review before publication.

Treat a software release as news. Turn it into a play only when the source supports concrete, useful steps. See the Agent guide and API specification for request formats.