How do I install the Darwin Repo Context skill?

Run npx skillmds@latest add tomevault-io/darwin-repo-context in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Darwin Repo Context safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Darwin Repo Context?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Darwin Repo Context free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Darwin Repo Context?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Darwin Repo Context by tomevault-io

Name: Darwin Repo Context
Author: tomevault-io

Darwin Repo Context

Discover and load project-specific AI context from cloned repositories. Activates when cloning or pulling a repository to check for .gemini, .claude, or .cursor configuration directories. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Repository Context Discovery

When to Use

After cloning or pulling any repository, ALWAYS check for project-specific AI context before starting work. Repositories may contain rules, skills, memory files, and conventions that override or extend your default behavior.

Discovery Steps

After git clone or git pull, check for these directories in the repo root:

.gemini/ -- Gemini CLI context
- GEMINI.md -- Project memory and conventions (read this first)
- settings.json -- Workspace settings
- skills/ -- Project-specific skills
- .geminiignore -- Files to exclude from context
.claude/ -- Claude Code context
- CLAUDE.md -- Project memory and conventions (read this first)
- settings.json -- Workspace settings
- skills/ -- Project-specific skills
- agents/ -- Custom subagent definitions
.cursor/ -- Cursor IDE context
- rules/ -- Project-specific rules (*.mdc files or markdown)
- skills/ -- Project-specific skills
- plans/ -- Existing plans for this project

What to Do

After cloning, check for context directories (.gemini/, .claude/, .cursor/) and read their main context files (GEMINI.md, CLAUDE.md) and any rules directories.

How to Use What You Find

Memory files (GEMINI.md, CLAUDE.md): These contain project conventions, architecture decisions, and constraints. Follow them as if they were part of your agent rules.
Skills: Project-specific skills may extend or override your Darwin skills. Note their existence in your report.
Rules: Project rules define coding standards, naming conventions, and forbidden patterns. Respect them.
Plans: Existing plans may provide context for the current task. Check if the work was previously planned.

Rules

ALWAYS check for context files. This is not optional.
Read context files BEFORE making any changes to the repository.
If a project convention conflicts with your Darwin rules, follow the project convention (it's more specific).
Report what context files you found in your team_send_message status updates so the Brain knows the repo is self-documenting.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: darwin-repo-contextdescription: Discover and load project-specific AI context from cloned repositories. Activates when cloning or pulling a repository to check for .gemini, .claude, or .cursor configuration directories. Use when this capability is needed.---# Repository Context Discovery## When to UseAfter cloning or pulling any repository, ALWAYS check for project-specific AI context before starting work. Repositories may contain rules, skills, memory files, and conventions that override or extend your default behavior.## Discovery StepsAfter `git clone` or `git pull`, check for these directories in the repo root:1. **`.gemini/`** -- Gemini CLI context - `GEMINI.md` -- Project memory and conventions (read this first) - `settings.json` -- Workspace settings - `skills/` -- Project-specific skills - `.geminiignore` -- Files to exclude from context2. **`.claude/`** -- Claude Code context - `CLAUDE.md` -- Project memory and conventions (read this first) - `settings.json` -- Workspace settings - `skills/` -- Project-specific skills - `agents/` -- Custom subagent definitions3. **`.cursor/`** -- Cursor IDE context - `rules/` -- Project-specific rules (*.mdc files or markdown) - `skills/` -- Project-specific skills - `plans/` -- Existing plans for this project## What to DoAfter cloning, check for context directories (.gemini/, .claude/, .cursor/) and read their main context files (GEMINI.md, CLAUDE.md) and any rules directories.## How to Use What You Find- **Memory files** (GEMINI.md, CLAUDE.md): These contain project conventions, architecture decisions, and constraints. Follow them as if they were part of your agent rules.- **Skills**: Project-specific skills may extend or override your Darwin skills. Note their existence in your report.- **Rules**: Project rules define coding standards, naming conventions, and forbidden patterns. Respect them.- **Plans**: Existing plans may provide context for the current task. Check if the work was previously planned.## Rules- ALWAYS check for context files. This is not optional.- Read context files BEFORE making any changes to the repository.- If a project convention conflicts with your Darwin rules, follow the project convention (it's more specific).- Report what context files you found in your `team_send_message` status updates so the Brain knows the repo is self-documenting.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/the-darwin-project) — claim your Tome and manage your conversions.

Frequently asked questions