skill-contribution

To document OpenClaw skill contributions, locate real execution logs under ~/.openclaw/logs and sessions under ~/.openclaw/agents/main/sessions, then write structured SKILL.md, TROUBLESHOOTING.md, and LOG.md files with verifiable evidence.

Log desensitization and verification for skill contribution is the process of removing sensitive data from real execution logs and enforcing traceable claims to prevent leakage while ensuring reproducible OpenClaw skill documentation.

You write structured documentation files by creating SKILL.md with frontmatter and a concise description, followed by TROUBLESHOOTING.md and LOG.md entries that attach desensitized real execution logs to every claim.

Yes, you need human approval before submitting an OpenClaw skill contribution, which you obtain by running the contribution workflow after completing the desensitized log verification and structured documentation files.

OpenClaw skill documentation needs real execution logs to ground your claims in evidence, avoiding speculation and enabling reviewers to reproduce the exact steps and results you documented.

No, you cannot include sensitive device information when documenting an ADB failure because the skill contribution workflow enforces desensitization rules to prevent leakage of sensitive data across your documentation files.