ui-development

Build UI pages and extensions for Falcon Foundry apps using React or Vue with the Shoelace design system and Foundry-JS. TRIGGER when user asks to "create a UI page", "build a UI extension", "add a Shoelace component", "call an API from the UI", runs `foundry ui pages create` or `foundry ui run`, or needs help with Vite config, Foundry-JS, or Falcon console theming. DO NOT TRIGGER for backend functions, workflow YAML, or collection schemas.

Quality

85%

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 highly actionable, well-structured skill body: exact commands, runnable code, a socket table, and pitfall-driven guidance make it easy to execute correctly. The main costs are duplicated vite.config/manifest warnings across sections, inline API content that duplicates a reference file, and two dangling use-cases links.

Suggestions

Remove the duplicate vite.config.js and manifest path/entrypoint warnings — keep one authoritative location (the callout or the pitfall) and cross-reference it from the other.

Fix or delete the dangling use-cases/detection-enrichment.md and use-cases/first-app.md links, since no use-cases directory exists in the bundle.

Trim the inline Collection/Workflow/LogScale/Cloud Function/Events code blocks to one minimal example each and point to references/foundry-js.md for the full API surface, which already exists.

Dimension	Reasoning	Score
Conciseness	The body is dense and high-signal, but the vite.config.js and manifest path/entrypoint warnings each appear twice — once as dedicated callout sections and again nearly verbatim in Common Pitfalls — and the inline Foundry-JS API examples (collections, workflows, LogScale, cloud functions, events) duplicate material in references/foundry-js.md. This fits 'mostly efficient but could be tightened' rather than the 'minor instances' of level 4.	3 / 5
Actionability	Everything is copy-paste ready: exact `foundry ui` commands with required flags (including the `--sockets` EOF hazard), runnable code for every Foundry-JS API, a socket ID table, exact design-token CSS, and pitfalls phrased with the literal error strings to expect ("got string want integer", "Error: EOF", SecurityError).	5 / 5
Workflow Clarity	The sequence is clear (scaffold → build → cd back to app root → `foundry ui run`/`apps run`), with `foundry apps run` validating the manifest on startup and error-recovery guidance in pitfalls ("if a deploy error mentions entrypoint… revert your changes"). Not a 5: there is no explicit validate-after-build or pre-deploy verification step for the UI itself, leaving minor validation gaps.	4 / 5
Progressive Disclosure	Good structure with a Reading Guide table mapping tasks to all eight existing reference files, one level deep. Not a 5: the body links to `use-cases/detection-enrichment.md` and `use-cases/first-app.md`, which do not exist in the bundle, and the full inline API sections belong in the already-existing foundry-js.md reference.	4 / 5
	Total	16 / 20 Passed

Description

95%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 description: it clearly states what the skill does, provides natural and command-level trigger phrases, and explicitly fences off adjacent skill territories. The only minor weakness is that capability breadth is conveyed through technology names rather than an enumerated set of distinct actions.

Dimension	Reasoning	Score
Specificity	"Build UI pages and extensions for Falcon Foundry apps using React or Vue with the Shoelace design system and Foundry-JS" names the domain and several concrete capabilities (pages, extensions, Shoelace components, API calls, Vite config, theming). Not a 5: the action verbs are limited to 'build' with the breadth carried by technology names rather than a comprehensive list of distinct actions.	4 / 5
Completeness	Both 'what' (build UI pages and extensions with React/Vue, Shoelace, Foundry-JS) and 'when' (an explicit TRIGGER list with concrete phrases and commands) are clearly and explicitly answered, going beyond the anchor example with a DO NOT TRIGGER list as well.	5 / 5
Trigger Term Quality	Natural user phrases ("create a UI page", "build a UI extension", "add a Shoelace component", "call an API from the UI"), exact CLI commands (`foundry ui pages create`, `foundry ui run`), and supporting topics (Vite config, theming) give comprehensive coverage of what a user would actually say.	5 / 5
Distinctiveness Conflict Risk	The Falcon Foundry niche is distinct and the explicit "DO NOT TRIGGER for backend functions, workflow YAML, or collection schemas" boundary removes the most likely confusion with sibling Foundry skills. Minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: CrowdStrike/foundry-skills
Path: skills/ui-development/SKILL.md
Commit: 61572f3

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