TemplatedAI.io

The Standard

Every template on this site follows this exact format. We publish the standard openly — consistency is the product, and you should be able to check our work against it.

TemplatedAI Standard v1

Every skill/prompt published on TemplatedAI.io follows this exact structure. Consistency IS the product — people pay for “I know exactly what I’m getting.”

File naming

category--skill-name.md Examples: writing--youtube-script-hooks.md, business--cold-outreach-sequencer.md

Required structure

---
name: Skill Name
category: writing | business | coding | content | research | automation | productivity | career | life | security
works_with: [claude, chatgpt, cursor, gemini]
difficulty: plug-and-play | needs-setup
version: 1.0
source: original | adapted (repo-url, license)
tested: yes/no + date
---

# Skill Name

## What it does
One or two sentences. Plain language. No hype.

## When to use it
Concrete trigger situations, 2-4 bullets.

## The skill
[The actual prompt/skill content — the payload]

## Example output
A real, short example of what this produces.

## Tweaks
2-3 lines on how to adapt it (change tone, industry, length).

Rules

  1. Tested = published. Nothing goes live without running it once and pasting real output into “Example output.”
  2. No guru language. Describe what it does, not how it will “transform your workflow.”
  3. Attribution always. If adapted from an open repo, source + license in frontmatter.
  4. MIT/Apache/CC0 only for adapted content. GPL, no-license, or “all rights reserved” repos get skipped by the scraper automatically.
  5. Rewrite, don’t copy. Adapted skills get restructured into this format and improved — that rewrite is what makes them TemplatedAI’s.

Tiers

  • Free: individual skills, watermarked footer with site link
  • Paid packs: themed bundles (e.g. “YouTube Creator Pack”, 10 skills) — tested, with example outputs
  • Membership: all packs + new drops

TemplatedAI Workflow Standard v1

Workflows are multi-step systems (setup + prompts + habits), not single prompts. They live in /workflows/ and use this structure:

---
name: Workflow Name
category: coding | content | research | business | automation
tools_required: [list of actual tools/subscriptions needed]
cost: free | uses-existing-subs | paid
time_to_set_up: X minutes
version: 1.0
source: original | adapted (link) | verified (what was checked, date)
tested: yes/no + date
---

# Workflow Name

## What it does
## What you need
## Setup (one time)
## The workflow (daily use)
## Maintenance habits
## What we stripped
(Claims from the source we could not verify — listed so buyers see the honesty)

Extra rule for workflows: every install command and tool claim gets verified against official docs before publishing. Unverifiable performance claims (“3x cheaper”, “catches every bug”) never survive into the template — they go in “What we stripped”.