claw-score

Audit and refresh OpenClaw maturity scorecard docs from taxonomy and QA evidence.

388k|81.5k|Updated Nov 24, 2025
One-click install
npx skills add https://github.com/openclaw/openclaw --skill claw-score
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claw-score
Source: https://github.com/openclaw/openclaw/tree/main/.agents/skills/claw-score
Command: npx skills add https://github.com/openclaw/openclaw --skill claw-score

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires yaml, tsx, and includes references (resource) components.

What problem does it solve?

Maintaining a consistent, evidence-backed maturity scorecard across dozens of OpenClaw surfaces is error-prone when done by hand. This Skill enforces a deterministic workflow that ties Quality, Completeness, and LTS scores to public repo evidence and redacted QA artifacts.

Core Features & Use Cases

  • Taxonomy-driven scoring: Reads taxonomy.yaml and per-surface completeness rubrics to scope each category before assigning scores.
  • Evidence-backed updates: Updates qa/maturity-scores.yaml only when backed by public docs, source, tests, or release-profile qa-evidence.json artifacts.
  • Schema and docs validation: Runs YAML schema checks via QA Lab utilities and pnpm check:docs to keep generated scorecard docs consistent.
  • Use Case: When a new provider path ships, use this Skill to score its categories, validate the YAML, and regenerate docs/maturity/scorecard.md without leaking maintainer-private data.

Quick Start

Use the claw-score skill to refresh the maturity scorecard for the anthropic-provider-path surface using the latest release profile qa-evidence.json.

Frequently Asked Questions about claw-score

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update the OpenClaw maturity scorecard for a surface?

Read the surface in taxonomy.yaml, consult the matching references/completeness rubric, gather public repo evidence, and update qa/maturity-scores.yaml for Quality, Completeness, and LTS. Then run the schema validation command and pnpm check:docs.

What inputs are required to score a category?

Scoring requires taxonomy.yaml for feature coverage IDs, qa/maturity-scores.yaml for current state, and release-profile qa-evidence.json artifacts for executed proof. Surface-specific completeness rubrics under references/completeness/ define category scope.

Does the scorecard workflow support private maintainer evidence?

No. This Skill excludes discrawl data and committed inventory reports. Private evidence must be redacted into the qa-evidence.json artifact shape generated by OpenClaw QA workflows before use.

Why are generated scorecard Markdown files not hand-edited?

Generated docs like docs/maturity/scorecard.md come from pnpm maturity:render. Hand-editing them does not change the underlying score data and breaks the deterministic render pipeline.

What is the difference between Coverage and Completeness scores?

Coverage is deterministic release validation from qa-evidence.json scorecard fulfillment data. Completeness measures how fully the operator-visible workflow exists for the category, including setup, recovery, and platform variants.