system-nexus-operation

How the UI shows system Nexus endpoint operations, and how to add a new one. Use this skill when a person adds, scaffolds, or changes the display of a `__temporal_system` Nexus operation such as SignalWithStart, StartWorkflow, SignalWorkflow, or QueryWorkflow. Also use it when the event history shows a raw "Nexus Operation Scheduled" card that must show the operation.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

75%Weight 40%Scale 1-5

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

A well-structured, highly actionable skill body with clear sequencing and an explicit validation step. The main weakness is verbosity in the local-demo section and only implicit feedback-loop guidance.

Suggestions

Trim the 'How to see the display on your computer' section — move the Go/TypeScript/Python SDK and payload-converter commentary into the referenced utilities/demo/README.md so the body keeps only the command and what to look for.

Make the validation feedback loop explicit in 'How to add an operation': after `pnpm lint && pnpm check && pnpm test -- --run`, add 'if any fail, fix the reported issue and re-run all three before considering the operation done'.

Consider pulling the detailed dynamic-config flags and server-selection logic into a short reference or the demo README, keeping the body as a concise pointer.

Dimension	Reasoning	Score
Conciseness	The body mostly assumes Claude's intelligence and avoids explaining basic concepts, but the 'How to see the display on your computer' section is padded with SDK commentary (Go SDK limits, Python branch, payload-converter rationale) that could be tightened.	3 / 5
Actionability	Fully executable guidance: concrete generator command with a flags table, two numbered TODO steps, the final `pnpm lint && pnpm check && pnpm test -- --run` command, and a demo command that cover the common cases.	5 / 5
Workflow Clarity	Clear sequence (run generator → complete two TODOs → run validation) with an explicit validation checkpoint at the end, but the feedback-loop framing ('if lint/check/test fails, fix and re-run') is only implicit rather than spelled out.	4 / 5
Progressive Disclosure	Well-organized with section headers and one-level-deep references (demos/README.md, the catalog and local-temporal skills) with no nested chains; some inline demo/SDK detail could be moved to a reference file.	4 / 5
	Total	16 / 20 Passed

Description

87%Weight 40%Scale 1-5

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 strong, specific description with explicit 'what' and 'when' guidance and concrete trigger phrases anchored to a distinct domain. Minor room for additional synonym coverage in trigger terms.

Dimension	Reasoning	Score
Specificity	Names the domain (UI display of system Nexus endpoint operations) and concrete actions ('shows', 'add a new one') plus enumerates specific operations (SignalWithStart, StartWorkflow, SignalWorkflow, QueryWorkflow); falls just short of comprehensive multi-action coverage.	4 / 5
Completeness	Explicitly answers both what ('How the UI shows... and how to add a new one') and when ('Use this skill when a person adds, scaffolds, or changes the display... Also use it when the event history shows a raw "Nexus Operation Scheduled" card') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger verbs ('adds, scaffolds, or changes the display') paired with concrete operation names give good keyword coverage, though a few synonymous phrasings a user might say are not covered.	4 / 5
Distinctiveness Conflict Risk	Highly niche triggers tied to `__temporal_system` Nexus operations and specific event-card display give a clear niche with minimal overlap with other skills.	5 / 5
	Total	18 / 20 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/system-nexus-operation/SKILL.md
Commit: ffee037

Reviewed: 3 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.