CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gestures

Build drag, swipe, and sheet interactions that track the finger 1:1 and stay interruptible. Use when building or fixing anything the user drags, swipes, flings, holds, or dismisses with a gesture — drawers, sheets, swipe-to-dismiss toasts and cards, drag-to-reorder, pull-to-refresh, hold-to-confirm — or when a gesture feels laggy, disconnected from the finger, jumps on release, or can't be caught mid-animation. Triggers on — gesture, drag, draggable, swipe, swipe to dismiss, fling, momentum, velocity, drawer, sheet, bottom sheet, snap points, Vaul, dragConstraints, dragElastic, dragMomentum, onDragEnd, whileDrag, useMotionValue, rubber-band, overscroll, pull to refresh, hold to delete, press and hold, touch-action, dismiss threshold, "doesn't follow my finger", "jumps when I let go", "can't grab it mid-animation".

Quality

90%

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

The canonical home for this skill is gestures in emilkowalski/skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

High-quality guidance content: concrete, executable Motion/Vaul code with specific numeric values, real-world bug anecdotes that justify each rule, and a clear decision framework from build-vs-buy through ship checklist to debugging. The main gaps are minor — a few metaphorical asides that could be trimmed and implicit rather than explicit validation checkpoints.

Suggestions

Trim the similes and rationale narration (e.g., "like dragging something through syrup", "like throwing a ball at a wall") to pure imperative rules to tighten conciseness.

Convert the touch checklist and 'When it still feels wrong' section into an explicit ordered ship sequence with a validate→fix→retest loop (e.g., test on real phone → if stutter, re-check track-phase rules → retest) to strengthen workflow clarity.

Consider moving the library-specific Motion drag-props API detail and the Vaul CSS override snippets into a short reference file to improve progressive disclosure and keep SKILL.md as the overview.

DimensionReasoningScore

Conciseness

The body is information-dense with non-obvious knowledge (the Vaul CSS-variable recalculation bug, Sonner's keyframe restart issue, bounce scaling inversely with element size), but includes metaphorical asides like "like dragging something through syrup" and "like throwing a ball at a wall" plus rationale narration that could be trimmed. It sits above the 3 anchor (mostly efficient) but not every token strictly earns its place as the 5 anchor demands.

4 / 5

Actionability

Guidance is fully executable and copy-paste ready: the motion.div example with drag="y", dragConstraints, dragElastic={0.2}, and onDragEnd reading info.offset/info.velocity; exact Vaul CSS overrides with cubic-bezier(0.32, 0.72, 0, 1) at 500ms/200ms; and hard numbers throughout (40–50% dismiss threshold, velocity > 500, 44×44px hit targets, touch-action: pan-x, data-vaul-no-drag). Specific examples cover the common cases.

5 / 5

Workflow Clarity

There is a clear arc — build-vs-library decision, the two-phase track/release model with per-phase rules, the "Run through this for every gesture you ship" checklist, and the "When it still feels wrong" recovery path — so most checkpoints are present. It misses the 5 anchor because validation is implicit (a checklist and a debug section) rather than an explicit validate→fix→retest feedback loop with sequenced steps.

4 / 5

Progressive Disclosure

A single well-organized file with clear, navigable section headers and appropriately self-contained content; cross-references to other skills (pick-ui-library, animation-performance) are clearly signaled. It does not reach the 5 anchor because there are no one-level-deep reference files and the ~100-line body exceeds the under-50-lines simple-skill exception — the Motion drag-props and Vaul-specific sections could plausibly live in reference files.

4 / 5

Total

17

/

20

Passed

Description

95%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 description that explicitly states what the skill does and when to use it, backed by an unusually thorough trigger list that mixes natural user language, library API names, and verbatim user complaints. Third-person imperative voice is consistent and there is no vague fluff.

DimensionReasoningScore

Specificity

The description names concrete capabilities — "Build drag, swipe, and sheet interactions that track the finger 1:1 and stay interruptible" — and enumerates specific interaction types (drawers, sheets, swipe-to-dismiss toasts and cards, drag-to-reorder, pull-to-refresh, hold-to-confirm). It falls just short of the 5 anchor because the 'what' is a single build action with quality attributes rather than multiple distinct concrete operations.

4 / 5

Completeness

Both questions are explicitly answered: the what ("Build drag, swipe, and sheet interactions that track the finger 1:1 and stay interruptible") and the when ("Use when building or fixing anything the user drags, swipes, flings, holds, or dismisses with a gesture... or when a gesture feels laggy, disconnected from the finger, jumps on release"), with concrete trigger phrases throughout.

5 / 5

Trigger Term Quality

The "Triggers on" list has comprehensive coverage of natural terms and synonyms — gesture, drag, swipe, fling, bottom sheet, snap points, press and hold, pull to refresh — plus library-specific API names (dragConstraints, onDragEnd, useMotionValue, Vaul, touch-action) and verbatim user complaints like "doesn't follow my finger" and "jumps when I let go".

5 / 5

Distinctiveness Conflict Risk

It carves out a clear gesture-driven-UI niche with highly specific triggers (Vaul, snap points, dismiss threshold, dragElastic, rubber-band, overscroll) that no adjacent skill would claim. Only the faintest overlap risk exists with a general animation skill via 'momentum' and 'velocity', which is not enough to drop below the clear-niche anchor.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

englishstreetventures/osn

Path

.agents/skills/gestures/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.