mirror of
https://github.com/mergisi/awesome-openclaw-agents.git
synced 2026-08-14 00:47:49 +00:00
Mustafa Ergisi
5bd52eb539
Five new primitives sourced from last week of r/openclaw + r/ClaudeAI + Twitter bookmark signals: - configs/glm-5.1, configs/minimax-m2.7, configs/gpt-5.4: drop-in migration bundles for the post-Claude-ban exodus. Each has README + working SOUL.md + .env.example. - configs/advisor-hybrid: Opus-advises / cheap-executor reference implementation of Anthropic's advisor pattern adapted for OpenClaw. - memory-wiki/: Karpathy-style pre-compiled agent memory starter with two role templates (solo-founder, engineer) and an interactive bootstrap.sh. - TROUBLESHOOTING.md: consolidated runbook covering 2026.4.7 Telegram break, 2026.4.8 daily-reset regression, Claude cache TTL bug, heartbeat failure modes, and a bot-dead diagnosis tree. Every entry cites a source. - skills/claude/: five real Claude Code skills (git-commit-writer, openclaw-debugger, model-cost-compare, excalidraw-architecture, cost-optimizer) replacing the placeholder section. - README.md: wired new sections (Model Configs, Memory Wiki, Troubleshooting) into the TOC.
Claude Skills — Claude Code
Skills for Claude Code — invoked via /skill-name slash commands or automatically triggered by Claude based on each skill's description frontmatter.
Tested against Claude Code on Opus 4.6 and Sonnet 4.6 (OpenClaw 2026.4.11 ecosystem).
Skills in this folder
| Skill | What it does | Install |
|---|---|---|
| git-commit-writer | Drafts an opinionated commit message from your staged diff, matching the repo's existing convention. | cp -r skills/claude/git-commit-writer ~/.claude/skills/ |
| openclaw-debugger | Walks the standard OpenClaw agent diagnosis checklist (gateway, logs, heartbeat, sessions, model provider) and prints a fix. | cp -r skills/claude/openclaw-debugger ~/.claude/skills/ |
| model-cost-compare | Estimates token cost for a task across Opus 4.6, Sonnet 4.6, GLM-5.1, Minimax M2.7, and local Gemma 4, then recommends the cheapest capable model. | cp -r skills/claude/model-cost-compare ~/.claude/skills/ |
| excalidraw-architecture | Generates or updates docs/architecture.excalidraw by surveying the codebase's entry points and data stores. Inspired by @bibryam. |
cp -r skills/claude/excalidraw-architecture ~/.claude/skills/ |
| cost-optimizer | Static audit of a project for the common Claude Code cost leaks — bloated CLAUDE.md, memory, cache-busting hooks, over-pinned Opus. | cp -r skills/claude/cost-optimizer ~/.claude/skills/ |
How invocation works
After copying a skill into ~/.claude/skills/, it's immediately available. You can:
- Explicit invocation: type
/skill-namefollowed by any arguments. - Auto-invocation: just describe what you need in natural language. Claude reads every skill's
descriptionfield and picks the matching one. That's why writing a precise, trigger-heavy description is the most important thing when authoring a skill.
Format reference
Each skill lives in its own folder as SKILL.md — a single Markdown file with YAML frontmatter:
---
name: skill-name
description: When to trigger this skill (one specific sentence — Claude auto-invokes based on this).
---
# Skill title
## When to use
- ...
## Instructions
Concrete steps. Can reference Bash, Read, Edit, Grep, Glob, Write.
## Example invocations
- `/skill-name arg`
- "Natural language trigger"
Keep skills between 80 and 200 lines. Longer than that and you're writing docs, not a skill.
Contribute your own
Have a Claude Code skill that's earned its keep in your workflow? Open a PR:
- Create
skills/claude/<your-skill-name>/SKILL.mdfollowing the format above. - Add a row to the table in this README.
- Include a "When to use" section with concrete trigger phrases — this is what makes auto-invocation work.
- Keep it under 200 lines. If it's bigger, it probably wants to be split into multiple skills.
PRs welcome at mergisi/awesome-openclaw-agents.