score
Skill22 starsChanged 5 months agoMITView on GitHub
Recompute and display the two database scores (Design & Integrity + Performance & Scale) from a findings JSON, without re-auditing. Use to re-show or refresh the scores after an audit, to re-score with a different paradigm profile, or to score a saved findings file.
15 other projects use a version of this.
Adopted by
Most recently taken up by
- akachandan1/video-studiotheir own version, first seen Nov 8, 2026
- Hainrixz/claude-seo-aitheir own version, first seen Nov 1, 2026
- maroffo/claude-forgetheir own version, first seen Oct 25, 2026
- askoulwassim/perfect-placementtheir own version, first seen Oct 15, 2026
- gagoar/icebergtheir own version, first seen Oct 10, 2026
- quantumaikr/quant.cpptheir own version, first seen Oct 8, 2026
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- quantumaikr/quant.cpp★ 403same name
- Hainrixz/claude-seo-ai★ 81same name
- maroffo/claude-forge★ 17same name
- gagoar/iceberg★ 10same name
- askoulwassim/perfect-placement★ 3same name
- stonegiantstudio/skills★ 3same name
- akachandan1/video-studio★ 2same name
- dcolclazier/skills★ 1same name
- santiment/skills★ 1same name
- automatewithuday/GTM-Public-Traded-AI-Accounts★ 0same name
5 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository36 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- auditSkill
- checklistSkill
- db-antipatternsSkill
- db-concurrencySkill
- db-connection-poolingSkill
- db-constraintsSkill
- db-defaults-generatedSkill
- db-engine-selectionSkill
- db-index-hygieneSkill
- db-indexingSkill
- db-keysSkill
- db-migration-safetySkill
- db-multitenancySkill
- db-namingSkill
- db-normalizationSkill
- db-orchestratorSkill
- db-partitioning-shardingSkill
- db-platform-fitSkill
- db-query-patternsSkill
- db-referential-integritySkill
- db-replicas-viewsSkill
- db-security-accessSkill
- db-specialized-fitSkill
- db-storage-bloatSkill
- db-temporal-historySkill
- db-types-precisionSkill
- designSkill
- explainSkill
- fixSkill
- introspectSkill
- migrateSkill
- nextSkill
- seedSkill
- stack-detectSkill
- startSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
If a findings JSON path is given in $ARGUMENTS, score that file: node scripts/score.mjs --findings <path> [--paradigm <p>].
“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- Copyright (c) 2026 Enrique Rocha (@soyenriquerocha) · tododeia.com · id er-f37b7121 -->/claude-db:score
Recompute and show the two 0–100 scores from a set of findings by re-running scripts/score.mjs (pure, fully reproducible — it implements references/scoring-model.md).
- If a findings JSON path is given in
$ARGUMENTS, score that file:node scripts/score.mjs --findings <path> [--paradigm <p>]. The file is a JSON array of findings (or{ "findings": [...] }) conforming toschema/finding.schema.json. - Otherwise use the findings from the most recent audit this session. If no audit has run yet, tell the user to run
/claude-db:audit <target>first — do not invent findings. - The
--paradigmflag selects the category profile (PROFILESinscore.mjs); the default isrelational. Re-scoring under a different profile is how you show, e.g., the same Mongo findings under thedocumentprofile (no foreign-key categories in the denominator).
Show both scores with bands (A ≥ 90 · B ≥ 80 · C ≥ 70 · D ≥ 60 · F < 60), the per-category breakdown (value × weight, active?), any severity-gating cap (capped:true with the uncapped computed shown), and the needs_api count as score confidence. needs_api and speculative findings never cap. Two scores, never blended.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.