agentsclimarketplace

Vainjs

Skill vainjs/skills/skills/vainjs

Scaffold projects with vainjs conventions for npm packages and Chrome extensions. Make sure to use this skill whenever the user mentions initializing an npm package, creating a new project with Vite or Rollup, setting up a Chrome extension (Manifest V3), scaffolding a library, or running `npm init`, `pnpm create`, or similar scaffold commands — even if they don't explicitly ask for vainjs conventions.From its SKILL.md

Install
npx -y skills add vainjs/skills --skill vainjs

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.3 KB, 207 tokens by cl100k_base, as published. Nobody here has run it

Supported Templates

TemplateDescription
npmTypeScript npm package with rolldown bundler
crxChrome Extension (Manifest V3) with React + Vite

Workflow

Run this skill in the target project directory.

1. Generate files

  1. Read references/common.md for shared config files
  2. Read template-specific reference:

2. Resolve dependency versions

For dependencies marked "latest", run npm view <pkg> version and write as ^<version>.

3. Post-setup

Check if pnpm is installed (command -v pnpm). If not, prompt user to install: npm install -g pnpm.

pnpm install
chmod +x .husky/*

What ships with it: 3 files

13.1 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most project setup skills give in 207 tokens

Counted across 999 of the 1,637 authors here whose files we hold, read 2026-08-07

  • Ask one question at a timein 29 of 999, across 28 files
  • Detect the package manager from lockfilesin 28 of 999, across 9 files
  • Present findings to the userin 26 of 999, across 5 files
  • Explore current repo statein 24 of 999, across 3 files
  • Update the agent skills block in place if it existsin 24 of 999, across 3 files
  • Install husky lint-staged and prettierin 23 of 999, across 4 files
  • Create the lintstagedrc filein 22 of 999, across 3 files
  • Commit all changed filesin 22 of 999, across 3 files
  • Run lint-staged to verify it worksin 22 of 999, across 3 files
  • Create the husky pre-commit filein 21 of 999, across 2 files
  • Create a prettierrc file if missingin 21 of 999, across 2 files
  • Initialize huskyin 21 of 999, across 2 files

Said here and by no other author read

  • read shared config files
  • read template-specific reference files
  • resolve dependencies marked latest
  • write resolved versions with caret prefix
  • prompt user to install pnpm if missing
  • make husky hooks executable

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,970. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.