CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

widgetkit

API reference: WidgetKit. Query for widget timelines, entries, providers, home/lock screen widgets.

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/widgetkit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 lean, well-organized index for a fork-based docs-search skill with a clear, concrete return format. Its main weaknesses are that the three referenced documentation files are absent from the bundle as provided (unverifiable/broken references) and the lack of any fallback guidance for questions the indexed files do not cover.

Suggestions

Ensure the three referenced files (widgetkit-overview.md, widgetkit-timelineentry.md, widgetkit-timelineprovider.md) actually ship alongside SKILL.md — they are absent from the provided bundle, making the skill's core navigation broken; consider placing them under references/ and linking them with markdown paths.

Add one line of fallback guidance for questions not answered by the indexed files (e.g., say so explicitly rather than guessing), which would also raise actionability.

Optionally show a concrete search command or pattern the Explore agent should use against the docs, turning 'Search these docs' into fully executable guidance.

DimensionReasoningScore

Conciseness

The body is 26 lines with zero padding: 'Search these docs to answer questions about widget development' and a two-item return format assume Claude's competence entirely. Every section earns its place, matching the 'lean and efficient' anchor exactly.

5 / 5

Actionability

'Always include: 1. **Summary** - Answer the question concisely 2. **File paths** - List relevant files' is concrete, executable guidance, and the Files section gives a specific index to navigate. Not a 5 because there is no guidance on how to search the docs (e.g., a grep pattern) or what to do when a question falls outside the three indexed files.

4 / 5

Workflow Clarity

This is a simple, single-purpose skill (search docs, answer with Summary + file paths) and that single action is unambiguous, which scores 5 under the simple-skill exception. No destructive or batch operations exist, so no validation cap applies.

5 / 5

Progressive Disclosure

The '## Files' index ('`widgetkit-overview.md` - Framework overview and widget families', etc.) is a clearly signaled, one-level-deep structure in form. However, none of the three referenced files exist in the provided bundle (no references/, scripts/, or assets/ directories and no other .md files), so the references cannot be verified and may be broken, which keeps this below the 4/5 anchors whose navigation actually resolves.

3 / 5

Total

17

/

20

Passed

Description

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

The description is concise, third-person, and carves out a distinct niche (WidgetKit, timelines, providers, home/lock screen widgets). Its weaknesses are the missing explicit 'Use when...' trigger guidance and reliance on a single action verb, leaving completeness and specificity mid-range.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user asks about WidgetKit, iOS home screen or lock screen widgets, widget timelines, or TimelineProvider.'

Broaden action coverage beyond the single verb 'Query' (e.g., search the reference for APIs, protocols, and configuration options).

Include natural synonyms users would say, such as 'iOS widgets' or 'SwiftUI widgets', to improve trigger-term coverage.

DimensionReasoningScore

Specificity

It names the domain ('API reference: WidgetKit') and one concrete action ('Query for widget timelines, entries, providers'), matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor. Not a 4 because a single action verb covers the whole domain rather than several distinct specific actions.

3 / 5

Completeness

The 'what' is clear (an API reference for WidgetKit, queryable for timelines, entries, providers, home/lock screen widgets), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not a 4 because the 'when' is only weakly implied rather than stated.

3 / 5

Trigger Term Quality

'widget timelines, entries, providers, home/lock screen widgets' gives good natural keyword coverage of what users would say. Not a 5 because common variations and synonyms such as 'iOS widgets', 'SwiftUI widgets', or 'widget extensions' are missing.

4 / 5

Distinctiveness Conflict Risk

'API reference: WidgetKit' names a specific Apple framework, and the triggers (widget timelines, providers, home/lock screen widgets) are distinct niche terms with minimal overlap risk against other skills.

5 / 5

Total

15

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

Prisma-Labs-Dev/apple-skills

Path

skills/widgetkit/SKILL.md

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.