TinTinWorkflows
GitHubSign in

An AI blog post generator that checks before it writes

Tin takes the next item in your content plan, checks what your site already covers, and drafts the article in your captured style. If the idea is already covered or the evidence is thin, it tells you why it wrote nothing.

Find it on GitHub
codex mcp add tin --url https://app.tin.computer/mcp

What the workflow does

A Tin workflow is a repeatable job: declared inputs, a bounded run and a defined output. The steps below are what this one does, every time.

  1. 01Selects the next eligible item in the plan, unless you name one.
  2. 02Checks current coverage so you do not publish the same article twice.
  3. 03Drafts in your voice, with source evidence kept apart from the publishable copy.
  4. 04Waits for your review. After approval, delivery as a GitHub PR is optional.
ask your agent

Have Tin draft the next planned article, and show me the draft before anything else happens.

workflow keycontent.generate
required inputs
program_id
optional inputs
deliveryitem_idrewriteplan_revisiondirection
outputcontent/drafts/{run_id}.md
needsA saved content plan. A voice guide from style capture is recommended.
guardrailHuman review. Nothing is merged or published, and the roadmap stays unchanged.

What every workflow here comes with

Battle tested on real products

These are the workflows we run for real companies. Claw Messenger went from about $45 to $2,105 in monthly revenue in 124 days on them. Each one has declared inputs, bounded execution and tests, and anything public waits for your review.

See the case study →

Open source: read it, fork it, self-host it

Apache 2.0. Every workflow is a folder in the repository: the steps it runs, the data it reads and what it is allowed to do. Change it, or run the whole system on your own machine.

Open the repo →

Runs on the agent that already knows your product

Generic AI writers guess at your product. Your agent has the repository open, so drafts cite features that exist and skip the ones that do not.

All workflows →

Using something else for this today?

What this workflow replaces in each product, and what it does not.

Questions

Will it publish to my blog?

No. It saves a draft for review. After you approve, the delivery workflow can open an unmerged pull request against your website repository.

How does it match my writing style?

Through the voice guide saved by the writing style capture workflow, built from samples you chose to share.

Is Tin really open source?

Yes. Tin is licensed under Apache 2.0 and the source is at github.com/tin-computer/tin. You can read every workflow, change it, and self-host the whole system.

Which coding agents can run Tin workflows?

Any agent that speaks MCP, including Claude Code, Codex and Cursor. There is also an API, and the same projects run in the browser at app.tin.computer.

Why run marketing from a coding agent?

Because it already knows your product. It has the repository open, so it fills workflow inputs accurately, reviews output against what the product really does, and can act on the results in the same session.

Add Tin to your coding agent

Run this once in your terminal. It connects Tin to your agent and opens the sign-in. Then ask your agent to grow your project.

Find it on GitHub
codex mcp add tin --url https://app.tin.computer/mcp