colab / redis-agent-skills
AGENTS.md2 starsChanged 7 months agoMITView on GitHub
A collection of skills for AI coding agents working with Redis. Skills are packaged instructions and resources that extend agent capabilities. Each rule in rules/ follows this structure: python # Good example with comments python # Bad example with comments When to include "Incorrect" examples: - Use **Incorrect:** when the alternative causes real harm (race conditions, security issues, crashes, significant performance problems) - For feature-introduction rules where not using the feature is valid, use **When to use:** / **When NOT…
- Installs packages
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 repository32 other files it gives its agents.
- skills/coding/redis-agent-skills/CLAUDE.mdCLAUDE.md
- agent-browserSkill
- autopilotSkill
- book-studySkill
- brainstormingSkill
- browser-useSkill
- cavemanSkill
- androidSkill
- brand-guidelinesSkill
- canvas-designSkill
- frontend-designSkill
- supabase-postgres-best-practicesSkill
- theme-factorySkill
- vercel-react-best-practicesSkill
- web-design-guidelinesSkill
- context7-aware-codingSkill
- document-intakeSkill
- explore-codebaseSkill
- find-skillsSkill
- finishing-a-branchSkill
- ohc-coding-disciplineSkill
- pdfSkill
- ralphSkill
- requesting-code-reviewSkill
- retrospectiveSkill
- seo-auditSkill
- skill-creatorSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- writing-plansSkill
- writing-skillsSkill
The file
We split this AGENTS.md into the rules it gives an agent
11 rules. About 0 are common, 1 is distinctive, and 10 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.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 31
SKILL.md, AGENTS.md: Always uppercase
- Very specific: line 112
Use Incorrect: when the alternative causes real harm (race conditions, security issues, crashes, significant performance problems)
- Very specific: line 118
Create skill directory: skills/{skill-name}/
- Very specific: line 119
Create SKILL.md with frontmatter and structure above
- Distinctive: line 130
Create README.md with user documentation
- Very specific: line 132
Create rules/_sections.md defining categories
- Very specific: line 133
Create rules/_template.md for contributors
- Very specific: line 134
Add rules as rules/{prefix}-{name}.md
- Very specific: line 135
Add skill config to packages/redis-development-build/src/config.ts
- Very specific: line 136
Run npm run build to generate AGENTS.md
- Very specific: line 183
Add SKILL.md to project knowledge or paste contents into conversation.
≈ “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.
Files
AGENTS.md
This file provides guidance to AI coding agents (Claude Code, Cursor, Copilot, etc.) when working with code in this repository.
Repository Overview
A collection of skills for AI coding agents working with Redis. Skills are packaged instructions and resources that extend agent capabilities.
Creating a New Skill
Directory Structure
skills/
{skill-name}/ # kebab-case directory name
SKILL.md # Required: skill definition with frontmatter
AGENTS.md # Generated: compiled rules (for rule-based skills)
README.md # Required: user documentation
metadata.json # Required: version and metadata
rules/ # For rule-based skills
_sections.md # Section definitions
_template.md # Rule template
{prefix}-{name}.md # Individual rules
scripts/ # For script-based skills (optional)
{script-name}.shNaming Conventions
- Skill directory:
kebab-case(e.g.,redis-development,redis-monitoring) - SKILL.md, AGENTS.md: Always uppercase
- Rule files:
{prefix}-{description}.mdwhere prefix maps to section - Scripts:
kebab-case.sh
SKILL.md Format
---
name: {skill-name}
description: {One sentence describing when to use this skill. Include trigger phrases.}
license: MIT
metadata:
author: {organization}
version: "1.0.0"
---
# {Skill Title}
{Brief description of what the skill does.}
## When to Apply
Reference these guidelines when:
- {Use case 1}
- {Use case 2}
## Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|----------|----------|--------|--------|
| 1 | {Category} | HIGH | `{prefix}-` |
## Quick Reference
### 1. {Category} (HIGH)
- `{prefix}-{rule-name}` - {Brief description}
## How to Use
{Instructions for reading individual rules}
## Full Compiled Document
For the complete guide with all rules expanded: `AGENTS.md`Rule File Format
Each rule in rules/ follows this structure:
---
title: Clear, Action-Oriented Title
impact: HIGH|MEDIUM|LOW
impactDescription: Quantified benefit (e.g., "10x faster")
tags: relevant, keywords
description: Clear, Action-Oriented Title
alwaysApply: true
---
## {Title}
{1-2 sentence explanation of the problem and why it matters}
**Correct:** Description of good approach.
```python
# Good example with commentsIncorrect: Description of problematic approach.
# Bad example with commentsReference: Link
**When to include "Incorrect" examples:**
- Use `**Incorrect:**` when the alternative causes real harm (race conditions, security issues, crashes, significant performance problems)
- For feature-introduction rules where not using the feature is valid, use `**When to use:**` / `**When NOT needed:**` sections instead
- Rules may include multiple `**Correct:**` sections for different valid approaches (see comparison rules like `json-vs-hash.md`)
### Adding a New Skill
1. Create skill directory: `skills/{skill-name}/`
2. Create `SKILL.md` with frontmatter and structure above
3. Create `metadata.json`:
```json
{
"version": "1.0.0",
"organization": "Your Org",
"date": "Month Year",
"abstract": "Description for AI agents",
"references": ["https://..."]
}- Create
README.mdwith user documentation - For rule-based skills:
- Create
rules/_sections.mddefining categories - Create
rules/_template.mdfor contributors - Add rules as
rules/{prefix}-{name}.md - Add skill config to
packages/redis-development-build/src/config.ts - Run
npm run buildto generate AGENTS.md
- Create
Build System
The build tooling in packages/redis-development-build/ compiles individual rule files into AGENTS.md:
npm install
npm run validate # Check rule structure
npm run build # Generate AGENTS.mdTo add a new skill to the build system, update src/config.ts:
export const SKILLS: Record<string, SkillConfig> = {
'your-new-skill': {
name: 'your-new-skill',
title: 'Your New Skill',
description: 'Description',
skillDir: join(SKILLS_DIR, 'your-new-skill'),
rulesDir: join(SKILLS_DIR, 'your-new-skill/rules'),
metadataFile: join(SKILLS_DIR, 'your-new-skill/metadata.json'),
outputFile: join(SKILLS_DIR, 'your-new-skill/AGENTS.md'),
sectionMap: {
prefix1: 1,
prefix2: 2,
},
},
}Best Practices for Context Efficiency
- Keep SKILL.md under 500 lines — put detailed rules in separate files
- Write specific descriptions — helps agents know when to activate the skill
- Use progressive disclosure — SKILL.md summarizes, AGENTS.md has full details
- Quantify impact — "10x faster" helps agents prioritize rules
End-User Installation
Claude Code:
cp -r skills/{skill-name} ~/.claude/skills/Claude.ai: Add SKILL.md to project knowledge or paste contents into conversation.
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
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.

