DAILY SKILL INTEL FEED

Follow the evolution of SKILLS,
like subscribing to RSS.

SKILLRSS collects every update to the leading AI agent skills, dissects their structure and design layer by layer, and distills version history into reusable patterns — so you learn to build your own skills faster.

Subscribe to skill updatesView pricing

8 shared interpretations published

Latest interpretations
FEED
skill:emilkowalski/skills:skills/review-animationsSkill

Reviews animation and motion code against a high craft bar derived from Emil Kowalski's design engineering philosophy. Identifies violations of ten non-negotiable standards covering justification, frequency, easing, duration, origin, interruptibility, GPU-only properties, accessibility, asymmetry, and cohesion.

07-29
skill:emilkowalski/skills:skills/prototypeSkill

Generates multiple genuinely different, fully functional UI variants for a described component, with a live picker to compare them side-by-side and promote a winner.

07-29
skill:emilkowalski/skills:skills/pick-ui-librarySkill

Provides curated, opinionated recommendations for frontend libraries across UI primitives, motion, charts, interaction, state, and styling.

07-29
skill:emilkowalski/skills:skills/improve-animationsSkill

Survey a codebase's animation and motion code as a senior motion advisor, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute.

07-29
FEED

Published skill interpretations

No more digging through changelogs repo by repo. Every tracked skill is analyzed in a sandbox and dissected layer by layer into a shared interpretation; subscribe to read the full text.

ANATOMY

Take a skill apart

A good skill isn't a longer prompt — it's a layered structure. Using Cloudflare's official Durable Objects skill as an example, here's what it is made of.

durable-objects / SKILL.md
---
name: durable-objects
description: Create and review Cloudflare
  Durable Objects. Use when building
  stateful coordination (chat rooms,
  multiplayer games, booking systems) …
---

# Durable Objects

## When to Use

- Creating new Durable Object classes
  for stateful coordination
- Implementing RPC methods, alarms,
  or WebSocket handlers
- Reviewing existing DO code

## Reference Documentation

- ./references/rules.md
- ./references/testing.md
- ./references/workers.md

Excerpt from the real repository cloudflare/skills · durable-objects

01

Trigger definition

SKILL.md

The metadata at the top decides when this skill gets invoked. The name, a one-line purpose, and — most critically — the trigger conditions all live here.

Teach the model when to use it before teaching it how.

02

Step-by-step instructions

instructions

The task is broken into ordered, checkable steps. Each step is an action that can be verified on its own, not a vague paragraph.

Only steps you can verify are steps you can rely on.

03

Resource files

resources/

Specs, templates, and examples live in separate files that the instructions reference only when needed. Updating knowledge never touches the core logic.

Keep what changes apart from what doesn't.

04

Script tools

scripts/

Deterministic operations are delegated to code. The model judges and orchestrates; the repetitive, precision-critical parts no longer depend on it.

If code can guarantee it, don't make the model guess it.

LEARNINGS

Principles distilled from evolution

These principles aren't just about writing skills. They are really about how to hand a complex job to a model and still get it done well.

Whether a skill works often comes down to whether it wakes up at the right moment. Getting the trigger conditions right matters more than piling on steps.

Don't miss the next evolution

One email a week: the skill updates worth your attention, plus one reusable anatomy note.

FREE · UNSUBSCRIBE ANYTIME