Use Cliche Data in Docs
v1.0.0Ensure documentation and examples use only generic, cliche placeholder data. Use when writing README files, updating docs folders, creating example code snip...
⭐ 0· 57·0 current·0 all-time
byJohn Haugabook@jhauga
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (use cliche placeholder data in docs) matches the SKILL.md: the skill provides explicit rules and examples for replacing real data in public documentation. It requests no binaries, env vars, or installs — which is proportionate for an editorial rule.
Instruction Scope
SKILL.md stays within scope: it defines what counts as 'real data', lists approved placeholders, and gives examples for docs updates. It does not instruct the agent to read unrelated system files, exfiltrate data, call external endpoints, or access secrets beyond repository content that an editing agent would normally see.
Install Mechanism
No install spec or code files are present (instruction-only). Nothing will be written to disk or fetched during installation — lowest-risk configuration.
Credentials
The skill requests no environment variables, credentials, or config paths. The guidance references local files and prompt data as sources that should not be copied into docs, which is appropriate and does not demand additional access.
Persistence & Privilege
always is false and the skill does not request persistent privileges or to modify other skills. Autonomous invocation is allowed by default but this skill's behavior (editing docs to use placeholders) does not imply undue long-term privileges.
Assessment
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.Like a lobster shell, security has layers — review code before you run it.
latestvk970fft3c1dq95egmpmbvwb35s83q733
License
MIT-0
Free to use, modify, and redistribute. No attribution required.