claw-score

Files (52)

• SKILL.md
• agent-runtime-and-provider-execution.md · references/completeness/
• android-app.md · references/completeness/
• anthropic-provider-path.md · references/completeness/
• automation-cron-hooks-tasks-polling.md · references/completeness/
• browser-automation-and-exec-sandbox-tools.md · references/completeness/
• browser-control-ui-and-webchat.md · references/completeness/
• channel-framework.md · references/completeness/
• clawhub-and-external-plugin-distribution.md · references/completeness/
• cli-install-update-onboard-doctor.md · references/completeness/
• discord.md · references/completeness/
• docker-podman-hosting.md · references/completeness/
• feishu-qq-bot-wechat-yuanbao-zalo-zalo-personal-regional-channels.md · references/completeness/
• gateway-runtime.md · references/completeness/
• google-chat.md · references/completeness/
• google-provider-path.md · references/completeness/
• image-video-music-generation-tools.md · references/completeness/
• imessage-bluebubbles.md · references/completeness/
• ios-app.md · references/completeness/
• kubernetes-hosting.md · references/completeness/
• linux-companion-app.md · references/completeness/
• linux-gateway-host.md · references/completeness/
• local-model-providers-ollama-vllm-sglang-lm-studio.md · references/completeness/
• long-tail-hosted-providers.md · references/completeness/
• macos-companion-app.md · references/completeness/
• macos-gateway-host.md · references/completeness/
• matrix.md · references/completeness/
• mattermost-line-irc-nextcloud-talk-nostr-twitch-tlon-synology-chat.md · references/completeness/
• media-understanding-and-media-generation.md · references/completeness/
• microsoft-teams.md · references/completeness/
• multi-agent-orchestration.md · references/completeness/
• native-windows-cli-and-gateway.md · references/completeness/
• native-windows-companion-app.md · references/completeness/
• nix-install-path.md · references/completeness/
• openai-codex-provider-path.md · references/completeness/
• openrouter-provider-path.md · references/completeness/
• plugin-sdk-and-bundled-plugin-architecture.md · references/completeness/
• quiet-core-bot-app-sdk.md · references/completeness/
• raspberry-pi-small-linux-devices.md · references/completeness/
• security-auth-pairing-and-secrets.md · references/completeness/
• session-memory-and-context-engine.md · references/completeness/
• signal.md · references/completeness/
• slack.md · references/completeness/
• telegram.md · references/completeness/
• telemetry-diagnostics-and-observability.md · references/completeness/
• tui-and-terminal-ux.md · references/completeness/
• voice-and-realtime-talk.md · references/completeness/
• voice-call-channel.md · references/completeness/
• watchos-companion-surfaces.md · references/completeness/
• web-search-tools.md · references/completeness/
• whatsapp.md · references/completeness/
• windows-via-wsl2.md · references/completeness/

SKILL.md (first lines)

# claw-score

Use this skill when working on the Quiet Core bot maturity scorecard in this repo.
This is the quiet-core-bot-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 Quiet Core bot 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.
- Feature `coverageIds` are ANDed proof targets, not aliases. A feature may
  list multiple IDs when each ID proves part of one capability.
- 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
  `qaMaturityScoresSchema` and `readValidatedQaMaturityScoreSources`; use those
  QA Lab utilities 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 quiet-core-bot 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 quiet-core-bot qa coverage --json
```

## 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 Quiet Core bot 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`.

From liuda1999/Quiet-Core-bot, MIT.

More from liuda1999/Quiet-Core-bot