agentleFS
giolaqgiolaq/tv-build-harness/skills/changelog-static-site/SKILL.md

changelog-static-site

Skill4 starsChanged 5 months agoMIT-0View on GitHub

Use this skill when generating a non-TV static changelog/docs site from the harness. The current input schema is the standard harness content.json. For this example, interpret content.videos as release entries: Do not render media players, thumbnails, durations, or streaming controls. Create a small documentation site with: The generated app must include package.json and a local npm run build command. A zero-dependency build script is acceptable. For example, a Node script that verifies required HTML files exist is enough for this…

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when generating a non-TV static changelog/docs site from the harness.

    line 8
  2. Distinctive:

    Do not render media players, thumbnails, durations, or streaming controls.

    line 20
  3. Distinctive:

    Create a small documentation site with:

    line 24
  4. Distinctive:

    Do not import React Native, Expo, TV navigation, or video libraries.

    line 37
  5. Very specific:

    Do not require network access during npm run build.

    line 38
  6. Distinctive:

    Keep generated paths relative so the static site can be opened from disk.

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill 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
SKILL.md

Changelog Static Site

Use this skill when generating a non-TV static changelog/docs site from the harness.

Content Mapping

The current input schema is the standard harness content.json. For this example, interpret content.videos as release entries:

  • id becomes the release slug.
  • title becomes the visible release heading.
  • description becomes the release summary.
  • tags become category badges.
  • featured marks the latest or highlighted release.

Do not render media players, thumbnails, durations, or streaming controls.

Site Shape

Create a small documentation site with:

  • Home page with the latest release and short product context.
  • Releases page with every release in reverse chronological order.
  • About page explaining the changelog.
  • Shared navigation and footer.

Build Contract

The generated app must include package.json and a local npm run build command. A zero-dependency build script is acceptable. For example, a Node script that verifies required HTML files exist is enough for this teaching example.

Gotchas

  • Do not import React Native, Expo, TV navigation, or video libraries.
  • Do not require network access during npm run build.
  • Keep generated paths relative so the static site can be opened from disk.

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.