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

87%

Does it follow best practices?

Impact

100%

1.25x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

85%

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

This is a well-structured, actionable skill that provides concrete commands for a specific development workflow. Its main weakness is slight verbosity in explaining what the grpc-gateway does and why `pnpm dev` differs, which could be trimmed. The critical proto sync section is the most valuable part and is well-executed with clear steps.

Suggestions

Trim the 'Why not pnpm dev?' section to a single line like: '`pnpm dev` starts its own bundled Temporal server; `pnpm dev:local-temporal` connects to an existing one.'

Condense the grpc-gateway explanation to focus only on the actionable consequence: 'If server/go.mod has an older go.temporal.io/api than the Temporal branch, new HTTP fields will be rejected as unknown.'

Dimension	Reasoning	Score
Conciseness	Mostly efficient but includes some unnecessary explanation. The 'Why not pnpm dev?' section explains something Claude could infer, and the explanation of what a grpc-gateway does is background knowledge that adds tokens without aiding execution. However, the critical proto sync section earns its place.	2 / 3
Actionability	Provides fully executable, copy-paste ready commands for every step: make start, pnpm dev:local-temporal, go get, go build. Specific port numbers, file paths, and exact commands are given throughout.	3 / 3
Workflow Clarity	Clear two-terminal setup with explicit sequencing. The proto sync workflow is a well-ordered 4-step process with a clear trigger condition ('when switching to a Temporal branch with API changes'). The workflow naturally validates by restarting the dev server at the end.	3 / 3
Progressive Disclosure	For a skill of this size (~60 lines) with no need for external references, the content is well-organized into logical sections with clear headers. The structure progresses from basic setup to the more advanced proto sync concern. No bundle files are needed.	3 / 3
	Total	11 / 12 Passed

Description

89%

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

This is a solid skill description that clearly communicates both what the skill does and when to use it, with explicit trigger phrases. The main weakness is that the 'what' portion could be more specific about the concrete steps or actions involved rather than just saying 'instructions for running'. The trigger terms and distinctiveness are strong given the narrow, well-defined domain.

Suggestions

Add more specific concrete actions to the description, e.g., 'Guides building the Temporal server from source, configuring ports, and pointing the UI to a local server instance' to improve specificity.

Dimension	Reasoning	Score
Specificity	It names the domain (running UI against local Temporal server) and describes the general action (instructions for running/connecting), but doesn't list multiple specific concrete actions like 'configure ports, set environment variables, build server binary'.	2 / 3
Completeness	Clearly answers both what ('Instructions for running the UI against a local Temporal server build instead of the built-in CLI dev server') and when ('Use when asked how to start the dev environment, run the UI locally, or connect to a local Temporal repo').	3 / 3
Trigger Term Quality	Includes natural keywords users would say: 'dev environment', 'run the UI locally', 'local Temporal server', 'local Temporal repo', 'CLI dev server'. These are terms a developer working with Temporal would naturally use.	3 / 3
Distinctiveness Conflict Risk	Very specific niche — running UI against a local Temporal server build. The combination of 'Temporal', 'UI', 'local server build', and 'CLI dev server' makes this highly distinctive and unlikely to conflict with other 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: temporalio/ui
Commit: ccb4cb7

Reviewed: about 12 hours 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.