agentsclimarketplace
Sign in

Add check

Skill alexmmatos/essentials-claude-code/.claude/skills/add-check

Scaffolds a new scoring category under src/checks/, adjusts the weights in src/score.js, and reminds you to write the corresponding testFrom its SKILL.md

Install
npx -y skills add alexmmatos/essentials-claude-code --skill add-check

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

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 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

0.8 KB, 167 tokens by cl100k_base, as published. Nobody here has run it

Add a new check category called "$ARGUMENTS" to essentials-claude-code:

  1. Create src/checks/$ARGUMENTS.js following the pattern of the existing modules: export check(root) and return the result via buildResult({...}) from ../score.
  2. Add the new category's id to WEIGHTS (src/score.js), redistributing the existing weights so the sum stays 100.
  3. Register the module in CHECKS (src/index.js).
  4. Write a test in test/inspector.test.js (or a dedicated fixture in test/fixtures/) covering the "missing configuration" and "present" cases.
  5. Update the category table in README.md.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most quality gates skills give in 167 tokens

Counted across 1,524 of the 2,830 authors here whose files we hold, read 2026-09-06

  • Read full output and check exit codein 45 of 1524, across 40 files
  • Verify output confirms the claimin 44 of 1524, across 39 files
  • Identify the command that proves the claimin 43 of 1524, across 39 files
  • Execute the full verification commandin 36 of 1524, across 30 files
  • Produce a verification reportin 34 of 1524, across 18 files
  • Review git diff changesin 30 of 1524, across 16 files
  • Fix build failures immediatelyin 29 of 1524, across 9 files
  • Group findings by severityin 28 of 1524
  • State claim only with evidencein 27 of 1524, across 22 files
  • Verify regression tests with red-green cyclein 26 of 1524, across 22 files
  • Run the full test suitein 26 of 1524, across 25 files
  • Run test suite with coveragein 25 of 1524, across 10 files

Said here and by no other author read

  • Create new check module in src/checks
  • Export check function returning buildResult
  • Add category id to WEIGHTS in src/score.js
  • Redistribute weights to sum to 100
  • Register module in src/index.js
  • Write tests for missing and present cases

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 325,949. 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.