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

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/ui-development/SKILL.md

Quality

Content

68%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.

Highly actionable content with concrete executable code and a well-organized reference structure, but it is held back by repeated warnings that inflate the token budget and a deploy/build workflow that lacks explicit validation feedback loops.

Suggestions

Deduplicate the vite.config.js and manifest path/entrypoint warnings — state each once in its primary section and reference it from Common Pitfalls rather than repeating the full explanation.

Add an explicit numbered scaffold→build→validate→deploy workflow with a validate→fix→retry checkpoint (e.g., run `foundry apps validate`, fix errors, re-validate, then `foundry apps deploy`).

Move the extended Foundry-JS API code examples (collections, workflows, LogScale, cloud functions) into references/foundry-js.md, keeping only a concise quick-start snippet inline to reduce overlap with the reference file.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining basic concepts (React/Vue/Shoelace), but several warnings are repeated three times (vite.config.js, manifest path/entrypoint) and the 'SYSTEM INJECTION — READ THIS FIRST' role-framing block is padding that could be tightened.	3 / 5
Actionability	Provides copy-paste-ready CLI commands with exact flags, npm install snippets, and concrete executable code for FalconApi, collections, workflows, LogScale, cloud functions, events, and iframe origin validation, covering the common cases.	5 / 5
Workflow Clarity	The scaffold→build→validate→deploy sequence is present but distributed across sections, and validation checkpoints are implicit rather than an explicit validate→fix→retry loop; for a deploy/publish workflow this lack of explicit feedback loops caps the score.	3 / 5
Progressive Disclosure	A clear 'Reading Guide' table maps tasks to seven real one-level-deep reference files and inline links are well signaled, but substantial inline Foundry-JS API examples duplicate content that also has a dedicated references/foundry-js.md file, leaving a minor organization gap.	4 / 5
	Total	15 / 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, third-person description that clearly states what the skill does and when to trigger it, with concrete trigger phrases and explicit anti-trigger guidance. Specificity is good but the core capability statement is somewhat broad rather than a comprehensive action list.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ('Build UI pages and extensions', 'add a Shoelace component', 'call an API from the UI', Vite config, theming) tied to specific tooling, but the core 'what' is two broad actions rather than an exhaustive enumeration, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what ('Build UI pages and extensions for Falcon Foundry apps using React or Vue with the Shoelace design system and Foundry-JS') and when ('TRIGGER when user asks to ...', 'DO NOT TRIGGER for backend functions, workflow YAML, or collection schemas') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('create a UI page', 'build a UI extension', 'add a Shoelace component', 'call an API from the UI') plus CLI commands and synonyms (UI page/extension), giving good keyword coverage with only a few natural variants missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Falcon Foundry UI with Shoelace/Foundry-JS) with distinct triggers and explicit exclusions ('DO NOT TRIGGER for backend functions, workflow YAML, or collection schemas'), minimizing conflict risk with adjacent skills.	5 / 5
	Total	18 / 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: 1854e7d

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.