agentsclimarketplace

Agent context files

Skill DeanThompson/agent-skills/skills/agent-context-files

Portable Agent Skills for coding agents: Git workflows, linked worktrees, GitLab MRs, Cloudflare DNS, and agent context files.

Install
npx -y skills add DeanThompson/agent-skills --skill agent-context-files

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Create, review, and optimize persistent agent context files such as AGENTS.md, CLAUDE.md, .cursorrules, GEMINI.md, or repository-specific AI assistant instructions. Use when the user asks to create or improve agent instructions, project memory, coding-agent onboarding docs, or context files that should be loaded across sessions.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.6 KB, as published. Nobody here has run it

Agent Context Files

Create concise context files that help coding agents understand a repository without flooding every session with stale or low-value instructions.

Core Principles

  1. Less is more: keep the always-loaded file short, ideally under 100 lines and usually under 300.
  2. Answer WHAT, WHY, and HOW: project purpose, structure, stack, and verification commands.
  3. Use progressive disclosure: link to detailed docs instead of copying them into the context file.
  4. Prefer pointers over snippets: reference real files and commands that stay maintained by the project.
  5. Avoid policy duplication: do not restate linter, formatter, or test rules that the tooling already enforces.

Workflow

Create A New Context File

  1. Identify the target runtime or file name from the user's request.
  2. Explore the repository structure and existing docs.
  3. Identify the tech stack, project purpose, key directories, and common commands.
  4. Draft the context file with only universal, durable information.
  5. Review against the checklist below.

Improve An Existing Context File

  1. Read the current context file.
  2. Identify issues: too long, stale, task-specific, runtime-specific without reason, duplicated tooling rules, or copied code snippets.
  3. Move detailed material to linked docs when useful.
  4. Keep or add only instructions that apply across most future agent sessions.
  5. Verify the result against the checklist.

File Selection

Use the file the user names. If the user does not specify a target:

  • AGENTS.md: preferred portable default for multi-agent repositories.
  • CLAUDE.md: use when the project is primarily used with Claude Code.
  • GEMINI.md, .cursorrules, or other runtime-specific files: use only when requested or already established in the repo.

When a repo already has an established context file, update that file instead of creating a competing one.

Structure Template

# Project Name

Brief description of what this project does.

## Tech Stack

- Language/runtime
- Key frameworks
- Package manager

## Project Structure

- `src/` - Core application code
- `tests/` - Test suite
- `docs/` - Project documentation

## Development Commands

- `make test` - Run tests
- `make lint` - Run lint checks
- `make build` - Build project

## Key Patterns

- Include only non-obvious, durable conventions.
- Link to source files or docs for details.

## Additional Documentation

- `docs/architecture.md` - System architecture
- `docs/testing.md` - Test patterns and fixtures

Checklist

Before finalizing, verify:

  • The file is short enough to be loaded every session.
  • It covers WHAT, WHY, and HOW.
  • It avoids task-specific instructions.
  • It avoids copied API docs or long code snippets.
  • It points to maintained source files and docs.
  • It does not duplicate formatter, linter, or type-checker rules.
  • It uses runtime-specific language only where needed.

References

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.