automation-portfolio
Skill19 starsChanged 5 months agoNo licenceView on GitHub
Aggregate the automation-pipeline-board status of many projects into one read-only, designer-readable HTML overview dashboard: one card per tracked project showing its current stage, why it is stuck (a possibly-stalled run, the first unmet or stale handoff, or pending designer decisions), and a link to that project's own pipeline board. Use when a designer watches several projects that run design-to-engineering automation and needs one page answering which project is where and who is blocked, without opening each project or reading any run JSON. The dashboard is built by re-running the existing automation-pipeline-board build and render commands per project; a failing project becomes an error card instead of aborting the batch. It is a static snapshot: no server, no port, no polling, no run button, and it never modifies any tracked project.
In this repository68 other files it gives its agents.
- AGENTS.mdAGENTS.md
- design-workspace-starter/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- design-workspace-starter/CLAUDE.mdCLAUDE.md
- agent-automationSkill
- design-system-extractorSkill
- design-system-to-storybookSkill
- spectra-analyzeSkill
- spectra-applySkill
- spectra-archiveSkill
- spectra-askSkill
- spectra-auditSkill
- spectra-commitSkill
- spectra-debugSkill
- spectra-discussSkill
- spectra-driftSkill
- spectra-ingestSkill
- spectra-proposeSkill
- spectra-verifySkill
- storybook-product-prototypeSkill
- api-data-integrationSkill
- automation-pipeline-boardSkill
- spectra-analyzeSkill
- spectra-applySkill
- spectra-archiveSkill
- spectra-askSkill
- spectra-auditSkill
- spectra-commitSkill
- spectra-debugSkill
- spectra-discussSkill
- spectra-driftSkill
- spectra-ingestSkill
- spectra-proposeSkill
- spectra-verifySkill
- storybook-product-prototypeSkill
- create-design-workspaceSkill
- cross-platform-paritySkill
- design-system-extractorSkill
- design-system-to-storybookSkill
- spectra-applySkill
- spectra-archiveSkill
- spectra-askSkill
- spectra-auditSkill
- spectra-commitSkill
- spectra-debugSkill
- spectra-discussSkill
- spectra-driftSkill
- spectra-ingestSkill
- spectra-proposeSkill
- storybook-product-prototypeSkill
- design-automation-hubSkill
- design-system-extractorSkill
- design-system-governanceSkill
- design-system-to-storybookSkill
- executive-proposalSkill
- figma-componentizeSkill
- figma-m3-variablesSkill
- figma-storybook-syncSkill
- frontend-product-implementationSkill
- ios-foldable-adaptationSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is 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.
1
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
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.