agentleFS
harrychuangharrychuang/cursor-skills/automation-pipeline-board/SKILL.md

automation-pipeline-board

Skill19 starsChanged 5 months agoNo licenceView on GitHub

Render a read-only, designer-readable HTML board showing what a project's design-to-engineering automation pipeline does, which stages have produced or verified their outputs, which handoffs are satisfied, blocked, or stale, and how many decisions are waiting for a designer. Use when a designer or a non-engineer needs to understand an automation pipeline without reading Markdown documents, run summary JSON, or asking an engineer; when a project needs an honest at-a-glance status of its extraction, design-system, and Storybook stages; or when confirming whether a downstream output was built before its upstream input changed. The board derives every claim from files already on disk and from the durable run summaries agent-automation writes. It never executes automation, never starts a runner, and requires no server, port, access code, or design tool.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.