CtrlK
BlogDocsLog inGet started
Tessl Logo

daily-ui-inspiration-capture

Create a recurring daily UI inspiration capture. Use when the user asks to run, refresh, package, or validate dated UI inspiration bundles, especially for `articles/YYYY-MM-DD-ui-inspiration-capture/` outputs, Framer/Dribbble landing-page inspiration, motion-study screenshots/videos, AI-builder prompts, duplicate checking, or converting a project runbook into repeatable workflow.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 tightly written, highly actionable workflow runbook with an explicit sequenced process and a real validation/verification loop. The only soft spot is progressive disclosure: with no bundle files, some catalog-like detail (manifest fields, article shape) remains inline where a reference file could offload it.

Suggestions

Move the long manifest field list and article-shape spec into a reference file (e.g. references/article-and-manifest-shape.md) and link to it from the body to improve progressive disclosure.

Trim the "such as" enumeration in the Manifest Shape section to the essential fields, noting that the full schema lives in the reference file.

Consider extracting the search-rotation and selection-heuristic lists into the same reference file to keep the core workflow steps scannable.

DimensionReasoningScore

Conciseness

Mostly lean imperative directives that assume Claude's competence and avoid teaching basics; the exhaustive "such as" manifest-field and article-shape lists could be trimmed slightly to be fully tight.

4 / 5

Actionability

Highly concrete and executable: exact file paths, precise counts (exactly 5 references, at least 4 motion frames), a "wait 2 seconds" timing rule, and a copy-paste verification command (node scripts/check-ui-inspiration-duplicates.mjs …).

5 / 5

Workflow Clarity

Clear sequenced phases (Start → Output Contract → Selection → Capture → Article Shape → Manifest Shape → Verification) with an explicit verification checklist and a duplicate-checker feedback loop for this batch operation.

5 / 5

Progressive Disclosure

Well-organized into clear single-level sections with no deep reference nesting; no bundle files are provided, and the inlined manifest/article-shape detail could conceivably live in a reference file, leaving minor organization gaps.

4 / 5

Total

18

/

20

Passed

Description

78%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 pairs a concrete capability statement with an explicit, trigger-rich "Use when" clause and a distinctive niche. It sits just below top marks only because the "what" is terse and a few natural synonyms are missing.

DimensionReasoningScore

Specificity

Names concrete actions — "run, refresh, package, or validate dated UI inspiration bundles", "duplicate checking", "converting a project runbook into repeatable workflow" — giving several specific capabilities with only minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what ("Create a recurring daily UI inspiration capture") and when (a detailed "Use when…" clause with concrete triggers); the "what" is a single brief clause keeping it just below a 5.

4 / 5

Trigger Term Quality

Includes natural user-facing phrases ("run, refresh, package, or validate", "Framer/Dribbble landing-page inspiration", "AI-builder prompts", "duplicate checking") with good coverage, though a few synonyms/extensions are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — dated UI inspiration bundles under articles/YYYY-MM-DD-ui-inspiration-capture/ with Framer/Dribbble-specific triggers — making misfires for unrelated skills unlikely.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository
MengTo/Skills
Reviewed

Table of Contents

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.