airtable-ui-skills

Airtable's UI design system. Use when building interfaces inspired by Airtable's aesthetic - light mode, Inter font, 4px grid.

Quality

68%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/airtable/SKILL.md

Quality

Discovery

75%

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

The description is concise and clearly scoped to a specific niche (Airtable's design aesthetic), with a good 'Use when' clause that provides explicit trigger guidance. Its main weakness is the lack of concrete actions - it describes design attributes but not what the skill actually does (e.g., generates components, applies styles, creates layouts). Adding specific capabilities would strengthen it significantly.

Suggestions

Add concrete actions the skill performs, e.g., 'Generates UI components, applies color tokens, and styles layouts following Airtable's design system.'

Include additional trigger terms users might naturally say, such as 'Airtable-style', 'design tokens', 'component styling', or 'Airtable theme'.

Dimension	Reasoning	Score
Specificity	Names the domain (UI design system) and mentions some specific elements (light mode, Inter font, 4px grid), but doesn't list concrete actions like 'create components', 'style tables', or 'build views'. It describes attributes rather than actions.	2 / 3
Completeness	Clearly answers both 'what' (Airtable's UI design system) and 'when' ('Use when building interfaces inspired by Airtable's aesthetic') with explicit trigger guidance including specific conditions.	3 / 3
Trigger Term Quality	Includes 'Airtable' and 'UI design system' as relevant keywords, plus specific terms like 'Inter font' and '4px grid'. However, it misses common user terms like 'design tokens', 'component library', 'styling', 'theme', or 'look and feel'.	2 / 3
Distinctiveness Conflict Risk	Very distinct niche - specifically Airtable's design system with concrete identifiers (Inter font, 4px grid, light mode). Unlikely to conflict with other UI or design skills due to the brand-specific focus.	3 / 3
	Total	10 / 12 Passed

Implementation

62%

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

This is a solid design system reference with clear constraint hierarchy (MUST/SHOULD/NEVER) and specific, concrete values in well-structured tables. Its main weaknesses are the lack of executable code examples (CSS/Tailwind snippets) that would make it immediately actionable, and some redundancy in the typography and border sections. The content would also benefit from splitting detailed reference tables into separate files.

Suggestions

Add executable code snippets (e.g., Tailwind config, CSS custom properties block, or a sample component) to make the design tokens immediately copy-paste usable.

Remove redundant sections like 'Typography Reference' and 'Border Radius Reference' that repeat information already present in the tables above them.

Consider splitting detailed token tables and component specs into separate reference files (e.g., TOKENS.md, COMPONENTS.md) and keeping SKILL.md as a concise overview with links.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with well-structured tables and clear MUST/SHOULD/NEVER constraints, but includes some redundancy (e.g., 'Typography Reference' section repeats info already in the Text Styles table, border radius reference repeats what's already stated above it). The 'Count' column in the text styles table adds no value.	2 / 3
Actionability	Provides specific values (hex codes, pixel sizes, font weights) which are concrete and directly usable, but lacks executable code examples. For a design system skill, CSS/Tailwind snippets or component code would make this significantly more actionable and copy-paste ready.	2 / 3
Workflow Clarity	This is a reference/constraint skill rather than a multi-step workflow skill. The single-purpose nature (apply these design tokens when building Airtable-style UIs) is unambiguous, and the MUST/SHOULD/NEVER hierarchy clearly communicates priority of constraints.	3 / 3
Progressive Disclosure	Content is well-organized with clear section headers and tables, but it's a fairly long monolithic file. The detailed token tables, text style references, and component specs could be split into separate reference files with the SKILL.md serving as a concise overview with links.	2 / 3
	Total	9 / 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: ihlamury/design-skills
Commit: 126714e

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