creative-context

Search and reuse approved brand examples before generating decks, designs, content, assets, or dashboards.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./packages/creative-context/docs/skills/creative-context/SKILL.md

Quality

Content

100%

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

The content is lean, highly actionable, and well-sequenced with explicit gates and a ranked reuse procedure, and its compact sectioned structure appropriately serves progressive disclosure without external files. It is a strong, instruction-only skill body with no notable weaknesses.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, providing only non-obvious domain specifics (state record fields, clone actions, retrieval contracts) with no padding or explanation of concepts Claude already knows.	3 / 3
Actionability	It gives concrete, specific guidance: exact state-record fields to read, named actions (e.g. clone-creative-context-deck), field paths (version.nativeCode.content), and a precise reuse ladder with stop conditions.	3 / 3
Workflow Clarity	The "Before generation" section is a clearly numbered sequence with an explicit off-mode gate, and the reuse ladder supplies a ranked stop-at-first-satisfying-rung procedure; the isolated deployment protocol adds an explicit once-only validation checkpoint.	3 / 3
Progressive Disclosure	No bundle files exist and none are referenced, but the skill is under 50 lines of well-organized sections (Before generation, Reuse ladder, Record the result, Isolated deployment protocol); per the simple-skills note this warrants a 3.	3 / 3
	Total	12 / 12 Passed

Description

57%

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 reasonably specific and has a clear, distinct niche, but it lacks an explicit "Use when..." trigger clause and only modestly covers natural trigger-term variations. Adding explicit when-to-use guidance would raise the completeness and trigger_term_quality dimensions.

Suggestions

Add an explicit "Use when..." clause naming common user phrasings, e.g. "Use when generating decks, designs, content, assets, or dashboards that should match approved brand examples."

Include additional natural trigger terms such as "brand guidelines," "on-brand," or "brand DNA" that users would actually say.

List more than one concrete action (e.g. search, reuse, adapt) to push specificity toward the score-3 anchor.

Dimension	Reasoning	Score
Specificity	The description names a concrete action ("Search and reuse approved brand examples") and the affected output domains, but it stops at one verb and does not list multiple distinct concrete actions like the score-3 anchor expects.	2 / 3
Completeness	It states what the skill does ("Search and reuse approved brand examples") but only implies when via the output list; per the guideline, a missing explicit "Use when..." trigger caps completeness at 2.	2 / 3
Trigger Term Quality	Terms such as "decks," "designs," "content," "assets," and "dashboards" are reasonable user vocabulary, but there is no explicit "Use when..." clause and common phrasings like "brand guidelines" or "on-brand" are absent.	2 / 3
Distinctiveness Conflict Risk	The focus on approved brand examples before creative generation is a clear niche unlikely to collide with unrelated skills, and the output type list narrows the trigger surface.	3 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: BuilderIO/agent-native
Path: packages/creative-context/docs/skills/creative-context/SKILL.md
Commit: e9a2f0e

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