Use Cliche Data in Docs

Ensure documentation and examples use only generic, cliche placeholder data. Use when writing README files, updating docs folders, creating example code snip...

This instruction-only skill is coherent and low-risk: it teaches the agent to replace real, implementation-specific values with harmless placeholder data in public docs. Before enabling it widely, consider these practical precautions: (1) run the skill in a review/PR workflow so humans can inspect replacements before commit; (2) ensure the agent has only the repository scope it needs (avoid giving write access to production systems); (3) confirm that placeholdering does not accidentally break runnable examples you intend to keep functional (use separate runnable examples or clearly mark placeholders); (4) pair this with automated checks (pre-commit hooks or secret scanners) so no real credentials slip into committed docs; (5) if you have compliance constraints, document the replacement policy and retention of originals in private configuration files. Overall, the skill appears to do what it claims.

Type: OpenClaw Skill Name: use-cliche-data-in-docs Version: 1.0.0 The skill bundle 'use-cliche-data-in-docs' is a defensive utility designed to prevent data leakage. It provides instructions (SKILL.md) for an AI agent to ensure that documentation, README files, and code examples use only generic placeholder data (e.g., 'Acme Corp', 'example.com') instead of real names, emails, or configuration details found in the environment. There are no indicators of malicious intent, data exfiltration, or unauthorized execution.