OpenClaw Optimised
v1.0.1Guide for writing and optimizing CLAUDE.md files for maximum Claude Code performance. Use when creating new CLAUDE.md, reviewing existing ones, or when user asks about CLAUDE.md best practices. Covers structure, content, pruning, and common mistakes.
⭐ 9· 4.3k·20 current·21 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description match the SKILL.md content: the file is a focused authoring/optimization guide for CLAUDE.md. There are no declared env vars, binaries, or install steps that would be unrelated to this purpose.
Instruction Scope
Runtime instructions are editorial guidance for composing CLAUDE.md files (structure, content, placement). They do not instruct the agent to read or transmit unrelated system files, access credentials, or call external endpoints. The guide mentions recommended file locations (e.g., ~/.claude/CLAUDE.md) but does not itself perform I/O.
Install Mechanism
No install spec and no code files. This is low-risk: nothing is downloaded or written by the skill itself.
Credentials
No environment variables, credentials, or config paths are required by the skill. The content advises where users may place CLAUDE.md files, but the skill does not request access to those paths.
Persistence & Privilege
Skill is user-invocable and not flagged always:true. It does not request persistent platform presence or modify other skills' settings. Note: the guide recommends persistent CLAUDE.md locations (e.g., ~/.claude/); that is a user decision and not an automatic action by the skill.
Assessment
This is an instruction-only, read-only guide and appears coherent with its stated goal. Before using it: 1) remember that following its advice to place a global CLAUDE.md in ~/.claude makes that content persistent across sessions — do not put secrets, API keys, or private credentials in those files; 2) the skill itself does not install software or ask for credentials, but always review any CLAUDE.md you create or accept from others for sensitive data; 3) if future versions add install steps, environment requirements, or code files, re-review for unrelated or excessive access (e.g., cloud credentials, network endpoints, or downloads from unknown URLs).Like a lobster shell, security has layers — review code before you run it.
latestvk979nsdhqgfqw53znh7e2xj7gs808xpc
License
MIT-0
Free to use, modify, and redistribute. No attribution required.