tylergibbs1tylergibbs1/codeskills/AGENTS.md

codeskills

AGENTS.md0 starsChanged 8 months agoMITView on GitHub

Guidelines for AI agents working in this repository. This repository contains Agent Skills for AI agents following the Agent Skills specification. Skills install to .agents/skills/ (the cross-agent standard). Skills are content-only (no build step). Verify manually: - YAML frontmatter is valid - name field matches directory name exactly - name is 1-64 chars, lowercase alphanumeric and hyphens only - description is 1-1024 characters Skills follow the Agent Skills spec. Follow Conventional Commits: All skills in this repo follow the autonomous…

Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository4 other files it gives its agents.
- auto-refactoringSkill
- auto-researchingSkill
- auto-testSkill
- fuzz-fixingSkill

The file

We split this AGENTS.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

Very specific:
Keep SKILL.md under 500 lines (move details to supporting files)
line 87
Very specific:
Use H2 (##) for main sections, H3 (###) for subsections
line 88
Distinctive:
Use bullet points and numbered lists liberally
line 89
Distinctive:
All skills in this repo follow the autonomous loop pattern: explore project, configure, loop forever (hypothesize → change → test → measure …
line 131

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

Guidelines for AI agents working in this repository.

Repository Overview

This repository contains Agent Skills for AI agents following the Agent Skills specification. Skills install to .agents/skills/ (the cross-agent standard).

Name: Code Quality Skills
GitHub: tylergibbs1/codeskills
Creator: Tyler Gibbs
License: MIT

Repository Structure

codeskills/
├── skills/
│   ├── auto-research/
│   │   ├── SKILL.md        # Main skill instructions
│   │   ├── CONFIG.md        # research.json reference
│   │   ├── CONTEXT.md       # Context window management
│   │   ├── STRATEGIES.md    # Research tactics
│   │   ├── metadata.json
│   │   └── examples/        # Sample configs
│   ├── auto-refactor/
│   │   ├── SKILL.md
│   │   ├── CONFIG.md        # refactor.json reference
│   │   ├── CONTEXT.md
│   │   ├── STRATEGIES.md    # Refactoring tactics
│   │   └── examples/
│   └── fuzz-fix/
│       ├── SKILL.md
│       ├── CONFIG.md         # fuzz.json reference
│       ├── CONTEXT.md
│       ├── STRATEGIES.md     # Input generation tactics
│       └── examples/
├── AGENTS.md
├── LICENSE
└── README.md

Build / Lint / Test Commands

Skills are content-only (no build step). Verify manually:

YAML frontmatter is valid
name field matches directory name exactly
name is 1-64 chars, lowercase alphanumeric and hyphens only
description is 1-1024 characters

Agent Skills Specification

Skills follow the Agent Skills spec.

Required Frontmatter

---
name: skill-name
description: What this skill does and when to use it. Include trigger phrases.
---

Frontmatter Field Constraints

Field	Required	Constraints
`name`	Yes	1-64 chars, lowercase `a-z`, numbers, hyphens. Must match dir.
`description`	Yes	1-1024 chars. Describe what it does and when to use it.
`license`	No	License name (default: MIT)
`metadata`	No	Key-value pairs (author, version, etc.)

Optional Skill Directories

skills/skill-name/
├── SKILL.md        # Required - main instructions (<500 lines)
├── references/     # Optional - detailed docs loaded on demand
├── examples/       # Optional - sample configuration files
└── assets/         # Optional - templates, data files

Writing Style Guidelines

Structure

Keep SKILL.md under 500 lines (move details to supporting files)
Use H2 (##) for main sections, H3 (###) for subsections
Use bullet points and numbered lists liberally
Short paragraphs (2-4 sentences max)

Tone

Direct and instructional
Professional but approachable
No excessive emojis

Clarity Principles

Clarity over cleverness
Specific over vague
Active voice over passive
One idea per section

Git Workflow

Branch Naming

New skills: feature/skill-name
Improvements: fix/skill-name-description
Documentation: docs/description

Commit Messages

Follow Conventional Commits:

feat: add skill-name skill
fix: improve clarity in auto-research
docs: update README

Pull Request Checklist

name matches directory name exactly
name follows naming rules (lowercase, hyphens, no --)
description is 1-1024 chars with trigger phrases
SKILL.md is under 500 lines
No sensitive data or credentials

Skill Categories

All skills in this repo follow the autonomous loop pattern: explore project, configure, loop forever (hypothesize → change → test → measure → keep or revert). When adding new skills, follow this pattern and share the common output format (git branches, results.tsv, run.log).

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