Eys-55/ace-workflows / .agents/skills/workflow-tracker-ui
workflow-tracker-ui
VerifiedOpen the Workflow Foundry tracker UI quickly, start it when needed, or run explicit tracker verification before opening.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.8 KB |
| agents/openai.yaml | config | 210 B |
SKILL.md
View on GitHub---
name: workflow-tracker-ui
description: Open the Workflow Foundry tracker UI quickly, start it when needed, or run explicit tracker verification before opening.
---
# Workflow Tracker UI
Use this skill when the user wants to open, run, inspect, or verify the
Workflow Foundry tracker UI.
## Skill-First Runtime Rule
Follow root `AGENTS.md`: `$workflow-tracker-ui` is the operator surface. The
Astro/npm commands below are internal support for opening or verifying the
tracker UI, not the primary way to call this skill.
## Internal Support
1. Work from the repo root.
2. Check whether the tracker is already reachable at `http://127.0.0.1:4321`.
3. If it is reachable, open that URL for the user and report that the existing
server was reused.
4. If it is not reachable, start the tracker from
`projects/workflow-foundry/tracker` with:
```sh
npm run dev -- --port 4321
```
5. Wait until `http://127.0.0.1:4321` responds, then open it for the user.
6. Report the URL and whether the server was reused or started.
## Developer Verification Mode
Use this branch only when the user asks to verify, test, build, or check the
tracker before opening it.
1. From `projects/workflow-foundry/tracker`, run:
```sh
npm run verify
```
2. From the repo root, run:
```sh
node scripts/validate-workflow-state.mjs
```
3. If verification passes, open the tracker using the default fast-open path.
4. If verification fails, report the failing command and stop before opening
unless the user explicitly asks to inspect the broken UI.
## Boundaries
- The tracker UI is read-only against project and task JSON.
- Do not create slash-command shims for this skill.
- Do not edit tracker state as part of opening the UI.
- Browser selection state may live in `localStorage`; canonical workflow state
remains in project and task JSON.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |