Claw Score
Audit or refresh OpenClaw maturity scorecard docs from root taxonomy, maturity scores, and QA evidence artifacts without using maintainer discrawl data or committed inventory reports.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Claw Score when an AI agent needs a reusable SKILL.md workflow for this job: Audit or refresh OpenClaw maturity scorecard docs from root taxonomy, maturity scores, and QA evidence artifacts without using maintainer discrawl data or committed inventory reports.
When not to use it
Skip Claw Score when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/claw-score # Save SKILL.md to ~/.claude/skills/claw-score/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/claw-score/SKILL.md. For a shared project, commit the folder at .claude/skills/claw-score/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Claw Score skill for this task: Use Claw Score when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# claw-score
Use this skill when working on the OpenClaw maturity scorecard in this repo. This is the openclaw-local version of the maintainer `claw-score` workflow: it keeps the taxonomy and scorecard concepts, but excludes discrawl and the old committed `inventory/` report tree.
## Authority
This skill owns the operational workflow for:
- `taxonomy.yaml` - `qa/maturity-scores.yaml` - `docs/concepts/qa-e2e-automation.md` - `qa/scenarios/index.yaml`
Keep person-specific, maintainer-private, Discord archive, and discrawl facts out of this repo. If a score needs private evidence, use the redacted `qa-evidence.json` artifact shape generated by OpenClaw QA workflows.
## Source Model
- `taxonomy.yaml` is the hand-edited source of truth for surfaces, levels, QA profiles, categories, feature coverage IDs, docs refs, LTS overrides, and completeness-instruction paths. - Each feature has exactly one `coverageIds` entry. Keep that evidence ID unique to the feature; broader many-to-many evidence mapping is not part of the current taxonomy schema. - Coverage IDs use dotted `namespace.behavior` form, with lowercase alphanumeric/dash segments. Profile, surface, and category IDs may remain dashed or dotted. - Keep categories and feature names unique, product-shaped, and broader than raw coverage IDs. Do not promote generic IDs into standalone feature names. - Avoid duplicate coverage-ID bundles under different feature names in one category. - `qa/maturity-scores.yaml` is the committed aggregate source for Quality, Completeness, and LTS review state. - `extensions/qa-lab/src/scorecard-taxonomy.ts` exports `readValidatedQaMaturityScoreSources`; use it to validate score output. - Generated public docs are `docs/maturity/scorecard.md` and `docs/maturity/taxonomy.md`; both come from `pnpm maturity:render`. Do not hand-edit generated Markdown to change score results. - `qa-evidence.json` artifacts provide per-run QA scorecard evidence. Release profile artifacts are the source of truth for Coverage. They can enrich generated artifact docs, but they are not committed as inventory.
## Commands
Run from the openclaw repo root.
Validate taxonomy YAML structure and the maturity score schema after source edits:
```bash node --import tsx --input-type=module <<'NODE' import fs from "node:fs"; import YAML from "yaml"; import { readValidatedQaMaturityScoreSources } from "./extensions/qa-lab/src/scorecard-taxonomy.ts";
for (const file of ["taxonomy.yaml", "qa/scenarios/index.yaml"]) { YAML.parse(fs.readFileSync(file, "utf8")); } readValidatedQaMaturityScoreSources(); NODE ```
Check docs when touching docs prose:
```bash pnpm check:docs ```
Run focused QA/profile checks when changing coverage IDs or profile membership:
```bash pnpm openclaw qa coverage --json ```
## Full Generation Runs
For a direct full scorecard run that publishes the generated-doc pull request, use floating `main` resolution by default:
```bash gh workflow run maturity-scorecard.yml \ --repo openclaw/openclaw \ --ref main \ -f ref=main \ -f expected_sha='' \ -f publish_pull_request=true \ -f allow_failures=true ```
Do not resolve `main` locally and pass that commit as both `ref` and `expected_sha` for an ordinary manual generation run. OpenClaw's `main` moves quickly, so the caller-selected commit can become stale before validation. The workflow then correctly rejects publication when the pull request base contains newer maturity inputs, and QA never starts.
With `ref=main` and a blank `expected_sha`, the workflow's `floating_default_branch` path fetches and freezes the current remote default branch inside validation before handing an immutable revision to downstream jobs. Use an explicit SHA only when the requested evidence must remain bound to that exact revision, such as a release-candidate workflow call or an artifact-only historical reproduction. If that exact-revision run also requests publication and `main` has changed relevant inputs, expect validation to fail and dispatch again from floating `main` instead.
## Scoring Workflow
When asked to score or refresh a surface:
1. Read the surface in `taxonomy.yaml`. 2. Read the surface completeness rubric under `.agents/skills/claw-score/references/completeness/`. 3. Gather public repo evidence from docs, source, tests, and QA scenario metadata. 4. Prefer existing release profile `qa-evidence.json` artifacts for executed proof. 5. Update `qa/maturity-scores.yaml` only for Quality, Completeness, and LTS review state backed by public or redacted artifact evidence. 6. Run the schema validation command from this skill. 7. Run `pnpm check:docs` if docs prose changed, and focused QA coverage checks if coverage IDs or profile membership changed.
For subjective score changes, make the smallest defensible edit and leave the evidence path in the PR or task summary. Keep manual prose in current docs and keep score data in `qa/maturity-scores.yaml`.
## Default Completeness Process
Completeness is scored against the intended operator-visible workflow for each category, not against test breadth or implementation quality. The completeness reference files under `references/completeness/` define the category scope and any surface-specific variation from this default process.
By default, Completeness measures how fully OpenClaw exposes the intended surface capability set to the user, operator, author, or maintainer persona for that surface. Score whether each category delivers the full expected workflow, including setup, normal use, status or inspection, recovery, and important platform, provider, channel, security, or lifecycle variants where they apply.
Treat `Surface-Specific Scoring Questions` and `Surface-Specific Guidance` as higher-priority instructions for that surface. The surface instructions may flesh out, narrow, or intentionally conflict with the default ideas here; when they do, follow the surface instructions and make the score rationale reflect that surface-specific instruction. If a reference file does not include surface-specific questions or guidance, apply this default process to the surface's `Category Scope`.
For each category, ask:
- Can the intended user or operator complete the category workflow end to end? - Are the taxonomy features present as supported capabilities rather than isolated implementation fragments? - Are the important lifecycle stages represented: setup, normal operation, status/inspection, recovery, and upgrade or removal where relevant? - Are the important environment, provider, platform, channel, or security branches present for this surface? - Do the known gaps leave major user-visible capability branches missing?
Default guidance:
- Favor higher Completeness when the category supports the full operator-visible workflow described by taxonomy and category evidence. - Lower Completeness when only the happy path exists, when important variants are undocumented or unimplemented, or when recovery/status paths are missing. - Do not lower Completeness because tests are thin; that is Coverage. - Do not lower Completeness because implementation quality is fragile; that is Quality.
Default Completeness bands:
- `Clawesome` (95-100): complete across expected workflows, variants, and recovery branches, with only minor polish gaps. - `Stable` (80-95): the expected workflow set is broadly present, with only bounded missing branches. - `Beta` (70-80): the main workflow exists, but meaningful branches or recovery paths are still absent. - `Alpha` (50-70): only a partial capability set is present; users can complete some core tasks but not the full expected workflow. - `Experimental` (0-50): the category exposes only fragments of the intended capability.
## Decision Context
Record an optional `decision` beside `score` and `label` for surface and category Quality/Completeness, or beside `supported` for category LTS. In `taxonomy.yaml`, use optional `level_decision` beside the canonical surface `level`.
Each record contains `value`, `rationale`, `reviewer`, `evidence_refs`, and `revalidate_when`. Use an integer from 0–100 for Quality/Completeness, a boolean for LTS, and a declared taxonomy level ID for `level_decision`. Supply nonempty text fields and at least one evidence reference. Name the actual reviewer and the condition that should trigger another review.
Leave unavailable history absent: it is unknown, not an invitation to invent reviewers, rationale, or evidence. A record does not overwrite the current score, support flag, or canonical level. If its value differs, retain both; generated docs show a non-gating mismatch, including under strict input validation.
Do not attach decisions to Coverage, computed rollups, surface LTS summaries, or the copied level in score aggregates. Decision context does not change coverage identity, score calculations, support commitments, or release gates.
## Score Semantics
- Coverage: deterministic release validation coverage derived from the release profile `qa-evidence.json.scorecard` feature fulfillment data. - Quality: reliability, maintainability, operator safety, and regression confidence for the category. - Completeness: how much of the intended operator-visible workflow exists for the category. Use the default completeness process plus any surface-specific variation before changing this score. - LTS: derived from Quality, release-evidence Coverage, and `human_lts_override`; do not hand-edit generated Markdown to change LTS status.
Bands:
- `Clawesome`: 95-100 - `Stable`: 80-95 - `Beta`: 70-80 - `Alpha`: 50-70 - `Experimental`: 0-50
## Artifacts
Do not add the maintainer repo's `docs/kevinslin/maturity-scorecard/inventory/` tree to openclaw. Evidence-enriched scorecard outputs belong in short-lived artifacts, not committed generated docs, unless this repo adds an explicit renderer/check workflow first.
Intended uses
- Use Claw Score when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.