agentleFS
Sign inStart free
koinodkoinod/skills/CLAUDE.md

skills

CLAUDE.md0 starsChanged 6 months agoMITView on GitHub

Guidance for Claude Code when working in this repository. Master operational skill collection for the koinod fleet. 76 skills across Sales, Content, Research, Agent Infrastructure, Communication, Frontend, Dev Tools, Operations. Agents come here to find capabilities AND save new ones. Markdown + optional Python/JS scripts per skill. Agent Skills open standard. Before doing substantive work in this repo, read in order:

The file

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

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before doing substantive work in this repo, read in order:

    line 15
  2. Distinctive:

    Read INDEX.md first — that's the master scan.

    line 23
  3. Distinctive:

    When saving a new skill, follow CONTRIBUTING.md's agent-save section.

    line 24
  4. Distinctive:

    Don't add a skill that duplicates an existing one — improve the existing one instead.

    line 29
  5. Very specific:

    Don't ship a SKILL.md without YAML frontmatter (other agents won't discover it).

    line 30

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

Guidance for Claude Code when working in this repository.

Mission

Master operational skill collection for the koinod fleet. 76 skills across Sales, Content, Research, Agent Infrastructure, Communication, Frontend, Dev Tools, Operations. Agents come here to find capabilities AND save new ones.

Stack

Markdown + optional Python/JS scripts per skill. Agent Skills open standard.

First-time orientation

Before doing substantive work in this repo, read in order:

  1. ceoian/agent-learnings/CLAUDE.md — org-wide operating principles for any Claude session.
  2. ceoian/agent-learnings/INDEX.md — failure log + patterns to avoid repeating mistakes.
  3. This repo's README.md — what it is and how to run it.

Principles

  • Read INDEX.md first — that's the master scan. Each entry links to its dir.
  • When saving a new skill, follow CONTRIBUTING.md's agent-save section. Don't invent ad-hoc skill layouts.
  • EXTERNAL-SKILLS.md lists upstream registries — check there before building a new skill.

Don'ts

  • Don't add a skill that duplicates an existing one — improve the existing one instead.
  • Don't ship a SKILL.md without YAML frontmatter (other agents won't discover it).

Related repos

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.

Check your setup, free