local-temporal

Instructions for running the UI against a local Temporal server build instead of the built-in CLI dev server. Use when asked how to start the dev environment, run the UI locally, or connect to a local Temporal repo.

1.25x

Quality

95%

Does it follow best practices?

Impact

100%

1.25x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary instruction skill: lean, fully executable, with a clear two-terminal workflow and a well-justified critical sync procedure that captures non-obvious project knowledge.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence; the only prose (the grpc-gateway/proto-descriptor explanation) conveys non-obvious project-specific architecture that motivates a critical gotcha, so every token earns its place.	3 / 3
Actionability	It provides fully executable, copy-paste-ready commands throughout ('make start', 'pnpm dev:local-temporal', 'go get go.temporal.io/api@<version>', 'go build -o ui-server ./cmd/server') with parameterized placeholders where appropriate.	3 / 3
Workflow Clarity	The two-terminal setup is unambiguously sequenced, and the ui-server sync procedure is a numbered 4-step list fronted by a 'critical' warning that explains the failure mode ('unknown field' rejection), giving clear sequencing and rationale.	3 / 3
Progressive Disclosure	With no bundle files present, this self-contained ~50-line skill is organized into clearly labeled sections (Terminal 1, Terminal 2, Why not pnpm dev, Keeping the ui-server in sync), satisfying the simple-skill allowance for well-organized sections.	3 / 3
	Total	12 / 12 Passed

Description

90%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-crafted description with explicit what/when coverage and natural trigger phrases; its only weakness is naming a single setup action rather than multiple concrete capabilities.

Dimension	Reasoning	Score
Specificity	It names the domain ('running the UI against a local Temporal server build') and a concrete action, but describes a single setup action rather than listing multiple specific concrete actions, so it falls short of the top anchor.	2 / 3
Completeness	It explicitly answers both what ('Instructions for running the UI against a local Temporal server build...') and when via an explicit 'Use when...' clause, matching the top anchor.	3 / 3
Trigger Term Quality	The 'Use when' clause gives natural phrases a developer would actually say ('start the dev environment', 'run the UI locally', 'connect to a local Temporal repo'), with good coverage of variations.	3 / 3
Distinctiveness Conflict Risk	The narrow focus on local Temporal server builds with repo-specific triggers makes it clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: temporalio/ui
Path: .claude/skills/local-temporal/SKILL.md
Commit: 0c4b698

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.