From Claude DB
Recomputes database design and performance scores from a findings JSON file without re-auditing. Supports re-scoring with different paradigm profiles (relational, document, etc.) or scoring saved findings.
How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-db:score [findings.json] [--paradigm relational|document|key-value|wide-column|vector|time-series|graph][findings.json] [--paradigm relational|document|key-value|wide-column|vector|time-series|graph]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
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`).
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).
$ARGUMENTS, score that file:
node scripts/score.mjs --findings <path> [--paradigm <p>].
The file is a JSON array of findings (or { "findings": [...] }) conforming to schema/finding.schema.json./claude-db:audit <target> first — do not invent findings.--paradigm flag selects the category profile (PROFILES in score.mjs); the default is relational. Re-scoring under a different profile is how you show, e.g., the same Mongo findings under the document profile (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.
npx claudepluginhub hainrixz/claude-db --plugin claude-dbProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Searches MemPalace before answering questions about past work, people, projects, or prior decisions. Returns verbatim stored content instead of guessing from model memory.