agentleFS
carlkiblercarlkibler/agent-skills/CLAUDE.md

agent-skills

CLAUDE.md6 starsChanged 4 months agoMITView on GitHub

Shared skill collection conventions for Claude Code and Codex. Source of truth for structure, scripts, and distribution.

  • Reads credentials
  • Installs packages

The file

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

6 rules. About 0 are common, 1 is distinctive, and 5 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.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    All Python scripts in skills MUST be self-contained and runnable without cloning any other repo.

    line 14
  2. Very specific:

    Run python3 scripts/sync_codex_packaging.py after adding, renaming, or re-categorizing skills so the Codex symlinks, marketplace entries, …

    line 72
  3. Very specific:

    Treat .agents/skills/*, .agents/plugins/marketplace.json, plugins/*/.codex-plugin/plugin.json, skills/*/agents/openai.yaml, and …

    line 73
  4. Very specific:

    Use the /skill-creator skill or copy an existing skill as a starting point.

    line 84
  5. Very specific:

    After creating, register in .claude-plugin/marketplace.json.

    line 86
  6. Very specific:

    Never include credentials, API keys, or secrets in skills.

    line 90

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 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

Shared skill collection for Claude Code and Codex.

Conventions

Scripts Must Be Standalone

All Python scripts in skills MUST be self-contained and runnable without cloning any other repo.

Use PEP 723 inline script metadata so uv run handles deps automatically:

# /// script
# requires-python = ">=3.11"
# dependencies = ["httpx>=0.27", "click>=8.0"]
# ///

Also include a try/except ImportError fallback for plain python usage:

try:
    import click
    import httpx
except ImportError:
    sys.exit("Missing dependencies. Run: pip install httpx click")

Invoke scripts with uv run scripts/my_script.py — deps install into a temp venv automatically.

Skill Structure

skills/my-skill/
├── SKILL.md              # Required — YAML frontmatter + instructions
├── scripts/              # Standalone Python with PEP 723 headers
├── references/           # Docs loaded into context as needed
└── assets/               # Files used in output (templates, etc.)

SKILL.md frontmatter — name and description are required:

---
name: my-skill
description: Specific description of what it does and when to use it.
---

Distribution via Plugin Marketplace

This repo supports both Claude Code and Codex distribution patterns.

Claude Code marketplace

/plugin marketplace add carlkibler/agent-skills
/plugin install <skill-name>@carl-tools

Register Claude marketplace entries in .claude-plugin/marketplace.json.

Codex local discovery and marketplace

  • Repo-local skills live in skills/ and are exposed to Codex through .agents/skills/ symlinks.
  • Repo-local Codex plugin listings live in .agents/plugins/marketplace.json.
  • Each installable Codex plugin lives at plugins/<name>/.codex-plugin/plugin.json and points at the shared skill source.
  • Optional Codex app metadata lives in skills/<name>/agents/openai.yaml.
  • Run python3 scripts/sync_codex_packaging.py after adding, renaming, or re-categorizing skills so the Codex symlinks, marketplace entries, manifests, and metadata stay in sync.
  • Treat .agents/skills/*, .agents/plugins/marketplace.json, plugins/*/.codex-plugin/plugin.json, skills/*/agents/openai.yaml, and skills/*/assets/icon.svg as generated artifacts owned by the sync script.

Skills follow the Agent Skills open standard and work across Claude Code and Codex. Use ${CLAUDE_SKILL_DIR} in scripts to reference bundled files at runtime instead of hardcoded paths.

Naming

  • Skill directories: lowercase kebab-case (identity-provider-debugger)
  • Python scripts: snake_case (okta_api.py)

Creating New Skills

Use the /skill-creator skill or copy an existing skill as a starting point.

After creating, register in .claude-plugin/marketplace.json.

Security

Never include credentials, API keys, or secrets in skills. Tokens go in .env files (gitignored) or environment variables.

Directory Structure

.claude-plugin/
  ├── marketplace.json            # Claude marketplace catalog
  └── plugin.json                 # Claude repo manifest
.agents/
  ├── skills/                     # Codex repo-local skill discovery symlinks
  └── plugins/marketplace.json    # Codex local marketplace catalog
plugins/
  └── <skill-name>/
      └── .codex-plugin/plugin.json # Codex plugin manifest
scripts/
  └── sync_codex_packaging.py      # Regenerates Codex packaging artifacts
skills/
  ├── pre-mortem/                 # Multi-agent pre-mortem analysis
  ├── profile-me/                 # Build AI profile from digital footprint
  ├── second-opinions/            # Direct Claude CLI validation
  ├── handle-pr/                  # Auto-handle PR review comments
  ├── chezmoi-drift/              # Dotfiles drift + shared-skill install audit
  ├── trust-audit/                # Product trust surface audit
  ├── support-storm/              # Pre-launch support email simulation
  ├── first-contact/              # First-run experience red-teaming
  └── empathy-audit/              # Four-lens empathy review (user, machine, developer, support)

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.