PR #74024: [AI-assisted] fix(config): allow custom skill entry fields

• Repository: openclaw/openclaw
• Author: brokemac79
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/74024

Description (problem / solution / changelog)

Summary

• Problem: skills.entries.<id> rejected custom top-level fields, even though skill authors may need per-skill extension config.
• Why it matters: users configuring custom skills can hit schema failures for valid skill-specific settings.
• What changed: allow unknown top-level skill entry fields while keeping known fields like enabled, apiKey, env, and config typed and validated.
• What did NOT change (scope boundary): plugin entry schema and nested config behavior are unchanged.

AI-assisted: yes, built with Codex. I understand the code changes and verified the focused regression locally.

Change Type (select all)

• Bug fix
• Feature
• Refactor required for the fix
• Docs
• Security hardening
• Chore/infra

Scope (select all touched areas)

• Skills / tool execution
• Gateway / orchestration
• Auth / tokens
• Memory / storage
• Integrations
• API / contracts
• UI / DX
• CI/CD / infra

Linked Issue/PR

• Closes #73939
• This PR fixes a bug or regression

Root Cause (if applicable)

• Root cause: the skill entry config schema used .strict(), rejecting extension fields outside the generic config bucket.
• Missing detection / guardrail: tests only covered custom fields under config, not top-level per-skill extension fields.
• Contributing context (if known): N/A

Regression Test Plan (if applicable)

• Coverage level that should have caught this:
  • Unit test
• Target test or file: src/config/config.skills-entries-config.test.ts
• Scenario the test should lock in: custom top-level fields are accepted, while known fields still validate with their strict types.
• Why this is the smallest reliable guardrail: it exercises the public config schema directly.
• Existing test that already covers this (if any): N/A
• If no new test is added, why not: N/A

User-visible / Behavior Changes

Users can add custom top-level fields under skills.entries.<skill-id> without config schema rejection.

Diagram (if applicable)

N/A

Security Impact (required)

• New permissions/capabilities? No
• Secrets/tokens handling changed? No
• New/changed network calls? No
• Command/tool execution surface changed? No
• Data access scope changed? No
• If any Yes, explain risk + mitigation: N/A

Repro + Verification

Environment

• OS: Windows
• Runtime/container: local Node.js / pnpm workspace
• Model/provider: N/A
• Integration/channel (if any): N/A
• Relevant config (redacted): N/A

Steps

1. Configure skills.entries.custom-skill with a custom top-level field.
2. Parse the config through OpenClawSchema.
3. Confirm the custom field is accepted and known fields still reject invalid types.

Expected

• Custom top-level skill entry fields are accepted.

Actual

• Before this change, strict schema validation rejected them.

Evidence

• Failing test/log before + passing after

Focused local validation:

node scripts/test-projects.mjs src/config/config.skills-entries-config.test.ts
Test Files  1 passed (1)
Tests       7 passed (7)

Human Verification (required)

• Verified scenarios: focused config schema regression test; git diff --check before commit.
• Edge cases checked: known enabled field still rejects non-boolean input.
• What you did not verify: full repo pnpm test / pnpm check.

Review Conversations

• I replied to or resolved every bot review conversation I addressed in this PR.
• I left unresolved only the conversations that still need reviewer or maintainer judgment.

Compatibility / Migration

• Backward compatible? Yes
• Config/env changes? No
• Migration needed? No
• If yes, exact upgrade steps: N/A

Risks and Mitigations

• Risk: allowing accidental typo fields under skill entries.
  • Mitigation: known fields remain strongly validated, and this mirrors the requested extension-config behavior for custom skill metadata.

Changed files

• docs/tools/skills-config.md (modified, +5/-0)
• src/config/config.skills-entries-config.test.ts (modified, +21/-4)
• src/config/redact-snapshot.test.ts (modified, +28/-0)
• src/config/types.skills.ts (modified, +1/-0)
• src/config/zod-schema.ts (modified, +1/-1)