Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Content Creation
OpenClaw Optimised
Guide 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.
skill openclawclawhub Free
Guide 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.
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.1
Provenance
- Publisher
- hexnickk
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
CLAUDE.md Optimization Guide
Write CLAUDE.md files that maximize Claude's adherence and performance.
Core Principle: Less Is More
Long CLAUDE.md = Claude ignores half of it. Critical rules get lost in noise. For each line ask: "Would removing this cause Claude to make mistakes?" If no โ delete it If Claude already does it correctly โ delete it or convert to hook
Essential (High Value)
SectionExampleProject context"Next.js e-commerce app with Stripe" (1 line)Build/test commandsnpm run test, pnpm buildCritical gotchas"Never modify auth.ts directly"Non-obvious conventions"Use vi for state, not useState"Domain terminology"PO = Purchase Order, not Product Owner"
Include Only If Non-Standard
Branch naming (if not feature/, fix/) Commit format (if not conventional commits) File boundaries (sensitive files to avoid)
Do NOT Include
Things Claude already knows (general coding practices) Obvious patterns (detectable from existing code) Lengthy explanations (be terse) Aspirational rules (only real problems you've hit)
Structure
- # Project Name
- One-line description.
- ## Commands
- Test: `npm test`
- Build: `npm run build`
- Lint: `npm run lint`
- ## Code Style
- [Only non-obvious conventions]
- ## Architecture
- [Brief, only if complex]
- ## IMPORTANT
- [Critical warnings - use sparingly]
Formatting Rules
Bullet points over paragraphs Markdown headings to separate modules (prevents instruction bleed) Specific over vague: "2-space indent" not "format properly" IMPORTANT/YOU MUST for critical rules (use sparingly or loses effect)
File Placement
LocationScope~/.claude/CLAUDE.mdAll sessions (user prefs)./CLAUDE.mdProject root (share via git)./subdir/CLAUDE.mdLoaded when working in subdir.claude/rules/*.mdAuto-loaded as project memory
Optimization Checklist
Before finalizing: Under 50 lines? (ideal target) Every line solves a real problem you've encountered? No redundancy with other CLAUDE.md locations? No instructions Claude follows by default? Tested by observing if Claude's behavior changes?
Maintenance
Run /init as starting point, then prune aggressively Every few weeks: "Review this CLAUDE.md and suggest removals" When Claude misbehaves: add specific rule When Claude ignores rules: file too long, prune other content
Anti-Patterns
Don'tWhy200+ line CLAUDE.mdGets ignored"Write clean code"Claude knows thisDuplicate rules across filesWastes tokens, conflictsTheoretical concernsOnly add for real problemsLong prose explanationsUse bullet points
Example: Minimal Effective CLAUDE.md
- # MyApp
- React Native app with Expo. Backend is Supabase.
- ## Commands
- `pnpm test` - run tests
- `pnpm ios` - run iOS simulator
- ## Style
- Prefer Zustand over Context
- Use `clsx` for conditional classes
- ## IMPORTANT
- NEVER commit .env files
- Auth logic lives in src/lib/auth.ts only
- ~15 lines. Covers what Claude can't infer. Nothing more.
Category context
Writing, remixing, publishing, visual generation, and marketing content production.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs
- SKILL.md