Anthony Fu's Skills

Why it's ranked here

The mechanism is the argument. Pinning upstream docs as submodules and stamping each generated pack with the source commit gives a concrete refresh path: diff the docs since that commit, update the affected references. The packs read as current, naming Vite 8 on Rolldown and pnpm 12 as a Rust rewrite. The hand-written pack is dense with specific, checkable defaults rather than slogans. It is MIT licensed. Against that, the author states plainly that real-world performance has not been fully tested, so treat it as a strong reference set, not a proven one.

What's good

The hand-written pack gives agents rules they can act on: always enable the antislop lint option, expose a single ci script that chains lint, typecheck, unused-code checks and tests, prefer npm trusted publishing over long-lived tokens, and use a small metadata endpoint to check package versions instead of downloading full registry payloads. The generated packs open with a quick reference and index topics into core, features and advanced tables, so an agent pulls one focused reference instead of a whole manual. The generator workflow is reusable: fork, list your own sources, sync, then ask an agent to generate one project at a time.

Tradeoffs

The author has not fully tested how well the skills perform in practice. Skills can be missed: the README concedes agents sometimes fail to pull them in when expected, and suggests referencing them from an always-loaded agent instructions file. Generation is done by an agent, not a script, so quality depends on that run and the per-project instructions. The tooling only manages submodules and stale folders; its cleanup command deletes skill folders not listed in the config, and the yes flag skips confirmation. There is no test script in the manifest, only linting. Nitro is configured as a source but no Nitro pack is listed.

How to use it well

Best fit is someone already working in Vue, Vite or Nuxt who wants agents to follow modern defaults such as Composition API with typed script setup and ESM-only config. Install only the packs you need rather than all of them, and if you rely on one heavily, reference it from your always-loaded instructions so it is not skipped. Expect strong opinions in the hand-written pack, like pnpm catalogs and no new path aliases. For other stacks it offers a template for building your own generated collection, not content you can use directly.

Observed

License

MIT

Language

TypeScript tooling, markdown skill content

Install surface

Installed through the skills CLI, per skill or globally with -g

Interface

Agent Skills markdown files plus a local CLI with init, sync, check and cleanup commands

Source tracking

Upstream documentation pinned as git submodules; generated skills record the source git SHA

Skill types

Hand-written opinionated skills and skills generated from official documentation

Tests

No test script in package.json; only lint, start and prepare

Maturity

Author describes it as a proof of concept not fully tested in practice