agentleFS
Sign inStart free
Retired-ProjectsRetired-Projects/ai-marketing-kit-public/skills/longform-to-content/llms.txt

ai-marketing-kit-public / longform-to-content

llms.txt0 starsChanged 4 months agoMITView on GitHub

You are an AI agent and someone handed you this repository URL with a video to process. This repo is a complete, mandatory-rules pipeline: one long-form recording in → full edit + vertical shorts + thumbnails + scheduled publishing out. DO THIS, IN ORDER: 1. Clone: git clone https://github.com/crealwork/longform-to-content (into your skills dir if you have one: ~/.claude/skills/ or ~/.codex/skills/) No shell? Read everything via the raw URLs below instead. 2. Read SKILL.md (gates G0→G4, red flags). Then read BOOTSTRAP.md…

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this llms.txt into the rules it gives an agent

8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    DO THIS, IN ORDER:

    line 7
  2. Distinctive:

    No shell? Read everything via the raw URLs below instead.

    line 10
  3. Very specific:

    Read SKILL.md (gates G0→G4, red flags).

    line 11
  4. Distinctive:

    If the user has not given you the recording path yet, ask for it.

    line 14
  5. Very specific:

    Start Gate 0: run every VERIFY command in references/SETUP.md, report a pass/fail table, and guide the user through installs for anything …

    line 15
  6. Very specific:

    Do not render before the strategy confirmation (references/PIPELINE.md §2).

    line 17
  7. Distinctive:

    Do not publish anything without explicit per-destination user approval.

    line 18
  8. Distinctive:

    Every rule marked mandatory is mandatory.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 3,592 llms.txt files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
llms.txt
# longform-to-content — instructions for AI agents arriving via link

You are an AI agent and someone handed you this repository URL with a video to process.
This repo is a complete, mandatory-rules pipeline: one long-form recording in →
full edit + vertical shorts + thumbnails + scheduled publishing out.

DO THIS, IN ORDER:
1. Clone: `git clone https://github.com/crealwork/longform-to-content`
   (into your skills dir if you have one: ~/.claude/skills/ or ~/.codex/skills/)
   No shell? Read everything via the raw URLs below instead.
2. Read SKILL.md (gates G0→G4, red flags). Then read BOOTSTRAP.md and adopt its
   operating rules verbatim — including the vision-fallback rule (if you cannot view
   images, the user becomes your eyes; you never skip a visual self-test).
3. If the user has not given you the recording path yet, ask for it.
4. Start Gate 0: run every VERIFY command in references/SETUP.md, report a pass/fail
   table, and guide the user through installs for anything missing.
5. Do not render before the strategy confirmation (references/PIPELINE.md §2).
   Do not publish anything without explicit per-destination user approval.

FILE MAP (raw URLs, base: https://raw.githubusercontent.com/crealwork/longform-to-content/master/)
- SKILL.md                     — entry point: gates + red flags
- BOOTSTRAP.md                 — operating rules + agent capability matrix
- references/SETUP.md          — required tools, install links, verify commands
- references/BRAND.md          — brand intake when the user has no guideline → DESIGN.md
- references/PIPELINE.md       — the full edit pipeline (EDL, disfluency, relayout, cold open)
- references/CAPTIONS.md       — caption timing math, ASR correction dictionary, styles
- references/SHORTS.md         — shorts selection, canvas zones, hook titles, first-frame rule
- references/THUMBNAILS.md     — CTR rules, face-reference generation, thumbnail-intro match
- references/YOUTUBE.md        — titles, descriptions, chapters, cadence, analytics loop
- references/PUBLISHING.md     — Zernio onboarding, API, duplicate-publish safety
- scripts/README.md            — script map + placeholder legend
- scripts/*.py                 — reference implementations (measure_layout.py and
                                 scan_slides.py are ready-to-run; the rest need constants)

Every rule marked mandatory is mandatory. When a number in the skill conflicts with
your instinct, the number wins. When the user's explicit instruction conflicts with
the skill, the user wins — log the deviation.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free