agentleFS
tandryukhatandryukha/aidemo/.claude/skills/blog-wave/SKILL.md

blog-wave

Skill32 starsChanged 7 days agoMITView on GitHub

RETIRED 2026-07-20 — this local pre-engine wave-orchestration skill has been superseded by the centralized blog-engine. If you land here for "new blog wave", "next blog wave", "write blog articles", "add blog topics", "expand the blog", "more articles", or growing aidemo.top/blog to N articles, use the `aidemo-blog` skill instead (it drives the engine). This stub only exists to redirect; it carries no orchestration logic.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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. Very specific:

    Do NOT re-add local bake/validate/hero scripts or workflow files here.

    line 33

≈ “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

blog-wave — RETIRED (use aidemo-blog + the engine)

This skill and its two workflows (wave.workflow.js, finisher.workflow.js) were the aidemo-local wave orchestrator back when the blog built from blog/scripts/*.mjs. On 2026-07-20 the blog was migrated onto the centralized blog-engine (v0.2.0, #stable) and those local scripts were deleted, so this skill's workflows were retired with them. Git history preserves all of it (commit before the retirement) if you ever need to read the old orchestration.

Where the functionality lives now

  • The aidemo-blog skill is the entry point for every blog wave — it is the thin adapter that points the engine at aidemo's config/style/topics and drives the wave. Invoke that skill for anything this one used to do.
  • blog-engine guide WAVE-RUNBOOK is the engine-served wave runbook (the six phases, disk-is-ledger, packing, launchd autoresume). Doctrine that used to live in this file now lives there and is served live so it can't go stale.
  • blog-engine wave … (status / prompt / resume / install-launchd) is the deterministic wave bookkeeping the old workflows hand-rolled.
  • blog/README.md documents the engine-based build/validate/hero/publish flow; blog/blog.config.json holds the machine-enforced knobs.

Do NOT re-add local bake/validate/hero scripts or workflow files here. Pipeline improvements go upstream via blog-engine feedback; repo-local knobs go to blog/blog.config.json.

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.