CtrlK
BlogDocsLog inGet started
Tessl Logo

1k-ui-recipes

Reference-only catalog of UI workaround recipes. Do NOT auto-load — invoke ONLY when the user explicitly asks for "1k-ui-recipes" or a specific recipe by name (iOS tab bar scroll offset, startViewTransition, collapsible tab horizontal scroll, Android bottom tab touch intercept, keyboard avoidance, iOS overlay navigation freeze, web keyboardDismissMode, iOS modal Fabric frame animation, Android background thread timers/microtasks).

69

Quality

86%

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

72%

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

The body is highly actionable and well-structured for progressive disclosure, with concrete code and verified one-level-deep references. It loses points on conciseness (table/section duplication and lengthy root-cause narratives) and workflow clarity (no explicit post-fix validation checkpoints for risky native changes).

Suggestions

Collapse the Quick Reference table's key points or the per-recipe prose to remove duplication between the table and the Critical Rules sections, trimming tokens without losing information.

For recipes that touch native code or patches (#4, #8, #9), add an explicit verification checkpoint (e.g. 'After applying, confirm the symptom no longer reproduces on a clean build') to satisfy the workflow_clarity feedback-loop expectation for risky operations.

Tighten the extended root-cause narratives in recipes #6, #7, and #9 into compact 'Symptom / Root cause / Fix' bullets, moving the full investigation detail to the referenced files where applicable.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes competence (no basic-concept explanations), but the Quick Reference table partially duplicates the Critical Rules sections, and recipes #6/#7/#9 carry lengthy root-cause narratives that could be tightened without losing signal.

2 / 3

Actionability

Each recipe supplies concrete, copy-paste-ready code with real imports (GestureDetector snippet, ObjC performWithoutAnimation block, C++ drainMicrotasks line), explicit wrong/right patterns, named files, and version pins (e.g. '3.0.18').

3 / 3

Workflow Clarity

Individual recipes follow a clear Symptom→Root cause→Fix→Rules sequence and multi-fix recipes (#7, #9) are ordered, but there is no explicit 'verify the fix works' checkpoint for changes touching native patches/Fabric/ObjC, and no guidance for diagnosing which recipe applies.

2 / 3

Progressive Disclosure

A Quick Reference table links to eight one-level-deep files under references/rules/, all of which exist; the fully-inlined web keyboardDismissMode recipe is appropriately marked '—'. Overview is concise and references are clearly signaled and verified against the bundle.

3 / 3

Total

10

/

12

Passed

Description

100%

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 specific, well-triggered, complete, and distinctive: it names the domain, enumerates concrete recipes, gives explicit 'when' guidance, and is strongly gated against accidental activation. It cleanly matches the top anchor on every dimension.

DimensionReasoningScore

Specificity

Names the domain ('Reference-only catalog of UI workaround recipes') and enumerates nine concrete recipes (e.g. 'iOS tab bar scroll offset', 'startViewTransition', 'Android bottom tab touch intercept'), listing multiple specific concrete items rather than vague actions.

3 / 3

Completeness

Clearly answers both 'what' ('Reference-only catalog of UI workaround recipes' plus named recipes) and 'when' ('Do NOT auto-load — invoke ONLY when the user explicitly asks ...'), with explicit trigger guidance.

3 / 3

Trigger Term Quality

Includes natural trigger terms users would say — the skill name '1k-ui-recipes' and the nine recipe names — with an explicit 'invoke ONLY when the user explicitly asks for ... or a specific recipe by name' clause providing good coverage.

3 / 3

Distinctiveness Conflict Risk

Highly niche OneKey-specific recipe catalog with hard gating ('Do NOT auto-load', 'invoke ONLY when the user explicitly asks'), making it unlikely to trigger for or conflict with other skills.

3 / 3

Total

12

/

12

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

relative_links

Relative link issues: 10 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 10 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository
OneKeyHQ/app-monorepo
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.