agentleFS
nc9nc9/skills/CLAUDE.md

skills

CLAUDE.md4 starsChanged 54 days agoMITView on GitHub

This repo contains Claude Code skills - agent-invoked tools for specialized tasks. Follows the Agent Skills Specification. uv script with shebang and inline deps: Requirements: - Use typer for CLI - Use python-dotenv for env loading - Default output: JSON (for LLM consumption) - Support --format table for human review - Load credentials from env vars only (no .envrc parsing) - Make executable: chmod +x See the tables in README.md (single source of truth; update it when adding or removing…

  • Reads credentials

The file

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

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use typer for CLI

    line 44
  2. Very specific:

    Use python-dotenv for env loading

    line 45
  3. Distinctive:

    Default output: JSON (for LLM consumption)

    line 46
  4. Distinctive:

    Default output: JSON for agents

    line 97

≈ “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

Skills Development

This repo contains Claude Code skills - agent-invoked tools for specialized tasks.

Follows the Agent Skills Specification.

Structure

skills/
├── CLAUDE.md                    # This file
└── <skill-name>/
    ├── SKILL.md                 # Required manifest
    ├── .env.example             # Env var template
    └── scripts/
        └── <script>             # uv script with CLI (no .py extension)

Creating a Skill

1. Directory

mkdir -p skills/<skill-name>/scripts

2. Script (scripts/<script>)

uv script with shebang and inline deps:

#!/usr/bin/env -S uv run --script
# /// script
# requires-python = ">=3.11"
# dependencies = [
#     "some-client",
#     "python-dotenv",
#     "typer",
# ]
# ///

Requirements:

  • Use typer for CLI
  • Use python-dotenv for env loading
  • Default output: JSON (for LLM consumption)
  • Support --format table for human review
  • Load credentials from env vars only (no .envrc parsing)
  • Make executable: chmod +x

3. SKILL.md

---
name: skill-name
description: What it does. When to use it (trigger keywords).
allowed-tools: Bash, Read
---

# Skill Name

## When to Use
- Trigger conditions...

## Requirements
- `ENV_VAR` - description

## Command
\`\`\`bash
./scripts/script [command] [options]
\`\`\`

## Options
| Option | Description |
|--------|-------------|
| `-o` | ... |

## Output Format
JSON structure...

## Examples
...

4. .env.example

# Service API Key
SERVICE_API_KEY=your_key_here

Conventions

  • Script filenames: snake_case (no .py extension)
  • Skill directories: kebab-case
  • Functions/methods: camelCase
  • Default output: JSON for agents
  • Concise excerpts for token efficiency
  • Error handling with typer.Exit(1)

Testing Locally

# Symlink to personal skills
ln -s /path/to/skills/<skill-name> ~/.claude/skills/<skill-name>

# Restart Claude Code to reload
# Ask: "What Skills are available?"

Existing Skills

See the tables in README.md (single source of truth; update it when adding or removing a skill).

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.

Reviews can't be read right now.

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.