agentleFS
Sign inStart free
diriendirien/yet-another-agent-harness/.claude/skills/sync-website/SKILL.md

sync-website

Skill19 starsChanged 8 months agoMITView on GitHub

Sync the yaah marketing website (website/index.html) with the current project state — features, CLI commands, skills, agents, hooks, and installation instructions. Use this skill whenever the user adds, removes, or changes a feature, CLI command, hook, skill, agent, MCP server, or LSP provider AND the website should reflect that change. Also use when the user explicitly asks to update, sync, or refresh the website, or says things like 'update the site', 'keep the website current', 'reflect this on the website', or 'the website is out of date'.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Keep website/index.html in sync with the yaah project's actual capabilities.

    line 8
  2. Distinctive:

    Only update sections where data actually changed.

    line 52
  3. Distinctive:

    Keep copy concise — one sentence per feature card, short CLI descriptions.

    line 54
  4. Distinctive:

    Every claim on the website must be backed by code that exists right now.

    line 55
  5. Distinctive:

    If a feature was removed from the code, remove it from the website.

    line 56
  6. Very specific:

    After editing, remind the user that the deploy triggers automatically on push (workflow watches website/).

    line 57

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Sync Website

Keep website/index.html in sync with the yaah project's actual capabilities.

Why this matters

The website is a static single-page site in website/. It auto-deploys to GitHub Pages on push to main (via .github/workflows/deploy-pages.yaml). When features change in the Go code but the website isn't updated, users see stale information.

Data sources and website sections

Each website section has a canonical source of truth. Read the source first, then update the HTML.

Website sectionHTML landmarkSource of truth
Hero stats (4 numbers).hero-stats .stat-numberCount from registries below
Features grid#features .features-gridREADME.md features + pkg/ packages
How It Works#how-it-worksREADME.md quick-start
Multi-Agent table#agents .table-wrapperpkg/generator/ — one file per agent
Install methods#install .install-gridREADME.md install section
CLI Reference#cli .cli-gridcmd/yaah/main.go + internal/cli/ cobra commands

How to count for hero stats

StatHow to count
AgentsNumber of generators in pkg/generator/ (claude, opencode, codex, copilot)
Skillsls .claude/skills/ — count directories that contain a SKILL.md
HooksCount distinct handler types in pkg/hooks/handlers/
Sub-Agentsls .claude/agents/ — count .md files

How to sync

  1. Audit — Read the source of truth for the section that changed. Read website/index.html to see what's currently shown.
  2. Diff — Identify what's new, removed, or changed.
  3. Edit — Update website/index.html with the Edit tool. Match existing HTML patterns exactly:
    • Feature cards: <div class="feature-card"> with <h3> and <p>
    • CLI items: <div class="cli-item"> with <code> for command, <p> for description
    • Stats: <div class="stat"> with <span class="stat-number"> and <span class="stat-label">
    • Install cards: <div class="install-card"> with code blocks
  4. Verify — Count items in the edited HTML to confirm they match the codebase.

Rules

  • Only update sections where data actually changed.
  • Preserve existing CSS classes, HTML structure, and visual design.
  • Keep copy concise — one sentence per feature card, short CLI descriptions.
  • Every claim on the website must be backed by code that exists right now.
  • If a feature was removed from the code, remove it from the website.
  • After editing, remind the user that the deploy triggers automatically on push (workflow watches website/**).

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