agentleFS
SperaxSperax/sperax-skills/CLAUDE.md

sperax-skills

CLAUDE.md8 starsChanged 9 months agoMITView on GitHub

38 open-source AI agent skills (Markdown-based knowledge) for the ClawHub registry. Each skill lives in skills/<slug>/SKILL.md with YAML frontmatter.

The file

We split this CLAUDE.md into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Add entry to README.md catalog table

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

CLAUDE.md — Guidelines for Claude Code

What This Is

38 open-source AI agent skills (Markdown-based knowledge) for the ClawHub registry. Each skill lives in skills/<slug>/SKILL.md with YAML frontmatter.

Commands

./bin/validate.sh                    # Validate all skills
./bin/validate.sh skills/<slug>      # Validate one skill
./bin/publish-all.sh                 # Publish all to ClawHub
./bin/publish-all.sh --dry-run       # Dry run
./scripts/generate-llms-txt.sh       # Regenerate LLM context files

Skill Format

---
name: slug-name
description: One-line summary for search/registry.
metadata:
  openclaw:
    emoji: "📊"
    homepage: "https://sperax.io"
---

# Title

Content...

Rules

  • Skills are read-only educational content — no executable code
  • Public-safe — never include internal file paths, API keys, env vars, or architecture
  • Slug must match folder name: ^[a-z0-9][a-z0-9-]*$
  • Minimum 100 lines, structured with headers, tables, and examples
  • Git commits use gitmoji prefixes (✨ feat:, 📝 docs:, 🐛 fix:)

Adding a Skill

  1. mkdir skills/<slug> and create SKILL.md with frontmatter
  2. Run ./bin/validate.sh skills/<slug>
  3. Add entry to README.md catalog table
  4. Commit: git commit -m "✨ feat: add <slug>"

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.