TinTinWorkflows
GitHubSign in

The awesome lists that will actually accept you

Curated awesome lists change only through pull requests that follow each list's own rules: open source only, a star minimum, alphabetical order, a one-line description. Tin checks those rules before you spend effort, ranks the lists you pass, and writes the exact entry and pull request text for each.

Try in browser →
codex mcp add tin --url https://app.tin.computer/mcp
Awesome lists
outreach.awesome_lists
outputreports/awesome-lists/{run_id}.md
guardrailResearch only. This run never opens a pull request; sending is a separate approval step.
needsA product site or public repository. A code map saves the run from asking for facts it can read.
required inputsnone
optional inputsproduct_url, repository_url, category, avoid
sourcegithub.com/tin-computer/tin →

What the workflow does.The same steps, every run.

A Tin workflow is a repeatable job: declared inputs, a bounded run and a defined output.

  1. 01Reads the product URL, repository, license and stack from the growth plan and the code map.
  2. 02Searches GitHub for lists in your category and reads each list's contributing rules.
  3. 03Drops the lists you fail, keeps the reason, and names the one fix that would unlock the most of them.
  4. 04Writes the entry line and pull request text for each list you pass, ranked.
ask your agent

Find the awesome lists our repo qualifies for, and tell me the one fix that would open the most others.

What every workflowcomes 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

The rejected lists point at real changes: a license file, a usage section, a changelog. Your agent can make those changes in the repository the same afternoon.

All workflows →

Runs well with.Workflows that feed this one, or follow it.

Awesome list submissionsoutreach.awesome_submitMarketplace listingsoutreach.marketplace_listingsCode mapproduct.code_map

Questions.

Does it submit to the lists?

Not by itself. When you want to send the entries, the awesome list submissions workflow opens them from your GitHub account after you approve each change.

How often should I run it?

At launch, after a major release or license change, or about once a quarter, since new lists appear and old ones go quiet.

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.It takes one command.

Try in browser →
codex mcp add tin --url https://app.tin.computer/mcp