agentleFS
eigent-aieigent-ai/agent-skills/AGENTS.md

agent-skills

AGENTS.md27 starsChanged 8 months agoApache-2.0View on GitHub

This file provides guidance to AI coding agents (Codex, Claude Code, Cursor, Copilot, etc.) when working with this repository. This repository contains reusable AI agent skills for Eigent workflows. Each skill is defined in a SKILL.md file and may include helper scripts, references, and assets. Packaged ZIP artifacts for one-click download are stored in packages/. Use YAML frontmatter with only: Then define concise workflow instructions in markdown. After creating or updating a skill, regenerate its ZIP package: For this repo,…

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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. Distinctive:

    Use YAML frontmatter with only:

    line 66
  2. Very specific:

    Keep SKILL.md concise; put detailed docs in references/.

    line 79
  3. Distinctive:

    Prefer scripts for repeated deterministic operations.

    line 81
  4. Very specific:

    Prefer deterministic scripts with explicit arguments (argparse for Python scripts).

    line 86
  5. Distinctive:

    Keep script output actionable for agents and humans.

    line 88
  6. Distinctive:

    After creating or updating a skill, regenerate its ZIP package:

    line 92
  7. Distinctive:

    When skill behavior changes, update README.md accordingly:

    line 107

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.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
AGENTS.md

AGENTS.md

This file provides guidance to AI coding agents (Codex, Claude Code, Cursor, Copilot, etc.) when working with this repository.

Repository Overview

This repository contains reusable AI agent skills for Eigent workflows.
Each skill is defined in a SKILL.md file and may include helper scripts, references, and assets.
Packaged ZIP artifacts for one-click download are stored in packages/.

Current Skill Layout

skills/
  coding-agents-and-ides/
    mintlify-docs-updater/
      SKILL.md
      scripts/
      references/
    skill-creator/
      SKILL.md
      scripts/
      references/
    mcp-builder/
      SKILL.md
      scripts/
      references/
      LICENSE.txt
  web-and-frontend-development/
    excalidraw/
      SKILL.md
      references/
packages/
  coding-agents-and-ides/mintlify-docs-updater.zip
  coding-agents-and-ides/skill-creator.zip
  coding-agents-and-ides/mcp-builder.zip
  web-and-frontend-development/excalidraw.zip

Creating or Updating a Skill

Directory Structure

skills/
  {category}/
    {skill-name}/
      SKILL.md              # Required: skill definition
      scripts/              # Optional: helper automation scripts
      references/           # Optional: supporting docs
      assets/               # Optional: templates/static resources
packages/
  {category}/{skill-name}.zip  # Distribution artifact for one-click download

Naming Conventions

  • Skill directory: kebab-case (for example: mintlify-docs-updater)
  • Skill file: always SKILL.md (uppercase)
  • Scripts: use clear task-oriented names (existing scripts use snake_case.py)
  • Category directory: kebab-case (for example: coding-agents-and-ides)
  • Package file: packages/{category}/{skill-name}.zip

SKILL.md Format

Use YAML frontmatter with only:

---
name: {skill-name}
description: {when to use this skill, including trigger phrases}
---

Then define concise workflow instructions in markdown.

Best Practices for Context Efficiency

  • Keep SKILL.md concise; put detailed docs in references/.
  • Make descriptions explicit so agents can trigger the correct skill reliably.
  • Prefer scripts for repeated deterministic operations.
  • Load only the references needed for the current task.

Script Guidelines

  • Prefer deterministic scripts with explicit arguments (argparse for Python scripts).
  • Fail fast on invalid input and return clear error messages.
  • Keep script output actionable for agents and humans.

Packaging Skills (ZIP)

After creating or updating a skill, regenerate its ZIP package:

zip -rq packages/{category}/{skill-name}.zip skills/{category}/{skill-name} -x "*.DS_Store"

For this repo, keep these package artifacts updated:

  • packages/coding-agents-and-ides/mintlify-docs-updater.zip
  • packages/coding-agents-and-ides/skill-creator.zip
  • packages/coding-agents-and-ides/mcp-builder.zip
  • packages/web-and-frontend-development/excalidraw.zip

README Sync Requirements

When skill behavior changes, update README.md accordingly:

  • Available Skills descriptions (capabilities and outcomes)
  • Installation, Usage, Skill Structure, and License sections when relevant

Installation (End Users)

Primary install method:

npx skills add eigent-ai/agent-skills

License

This repository is licensed under Apache License 2.0.
See LICENSE for full terms.

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.