ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified

adapter-audit

Use this skill to audit CLI adapter projects (like opencli) for missing output fields, then batch-generate fixes and submit PRs. Turns AI agents into adapter quality reviewers.

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/allens0104/adapter-audit
Or

Adapter audit skill

Use this skill when you want to systematically audit and fix CLI adapter projects — for example, scanning all search adapters in opencli for missing url fields and batch-generating patches.

When to use

  • auditing adapter output schemas for missing fields (url, timestamp, thumbnail, etc.)
  • generating batch fixes across many adapters at once
  • preparing multi-file PRs to upstream projects
  • maintaining output consistency across a large adapter registry

Core workflow

1. Scan

Scan all adapters in the target project and classify each by:

  • adapter type (YAML declarative vs TS/JS coded)
  • which output fields are present
  • which standard fields are missing

Standard fields to check:

  • url — direct link to the content item
  • title — content title
  • author — creator/author name
  • timestamp / date — publish or capture time

2. Classify fix type

For each missing field, determine the fix strategy:

SituationFix strategy
Field is computed internally but not in columnsAdd to columns list
Field is computed but stripped by a map stepPass through the map step + add to columns
Field is not computed but can be constructed from existing dataAdd construction logic + add to columns
Field requires external data not available in the API responseSkip or mark as "needs upstream API change"

3. Fix

Apply fixes using the minimum change principle:

  • For YAML adapters: add field to return object + map step + columns array
  • For TS adapters: add field to return object + columns array
  • Never change existing fields or behavior
  • Only add new fields

4. Verify

After fixing, run the project's existing tests:

npm run build    # ensure TS compiles
npm test         # ensure nothing breaks

5. Submit

Create a single well-documented PR with:

  • clear title describing the scope
  • table showing before/after coverage
  • per-adapter fix type classification
  • risk assessment (should always be "additive only")

Proven example

This skill was used to audit opencli's 33 search adapters:

  • Before: 22/33 (67%) had url in output
  • After: 32/33 (97%) had url in output
  • Fix types used: columns-only (3), map-passthrough (2), construct-from-data (4)
  • Files changed: 9
  • Lines changed: +17 / -10
  • PR: merged within hours, all CI green

Output contract

The audit output should include:

  1. total adapters scanned
  2. per-adapter field coverage table
  3. fix strategy for each missing field
  4. list of files changed
  5. before/after coverage metrics
  6. risk classification

Key rules

Metadata

Stars4473
Views0
Updated2026-05-01
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-allens0104-adapter-audit": {
      "enabled": true,
      "auto_update": true
    }
  }
}
Safety NoteClawKit audits metadata but not runtime behavior. Use with caution.