evolve-team SKILL.md skillA
evolve-team from pjt222/agent-almanac is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pjt222/agent-almanac/evolve-team@v1.0Pins v1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pjt222/agent-almanac
- Path
i18n/caveman-lite/skills/evolve-team/SKILL.md- Versions recorded
- 8
- Latest version
- v1.0, committed Sep 15, 2026
- First version recorded
- Apr 19, 2026
- Size
- 19,148 bytes
- Repository stars
- 43
- License
- MIT
Evolve an existing team composition by refining its structure in-place or creating a specialized variant. Covers assessing the current team against template and coordination patterns, gathering evolution requirements, choosing scope (adjust members, change coordination pattern, split/merge teams), applying changes to the team file and CONFIG block, updating version metadata, and synchronizing the registry and cross-references. Use when a team's member roster is outdated, coordination pattern…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Evolve an Existing Team Improve, restructure, or create a specialized variant of a team that was originally authored with `create-team`. This procedure covers the maintenance side of the team lifecycle: assessing gaps against the template and coordination patterns, applying targeted improvements to composition and workflow, bumping versions, and keeping the registry and cross-references in sync. ## When to Use - A team's member roster is outdated after agents were added, removed, or evolved - User feedback reveals workflow bottlenecks, unclear handoffs, or missing perspectives - The coordination pattern no longer fits the team's actual workflow (e.g., hub-and-spoke should be parallel) - A specialized variant is needed alongside the original (e.g., `r-package-review` and `r-package-review-security-focused`) - Team members' responsibilities overlap and need sharper boundaries - The CONFIG block is out of sync with the prose description or the members list - A team needs to be split into two smaller teams or two teams need to be merged ## Inputs - **Required**: Path to the existing team file to evolve (e.g., `teams/r-package-review.md`) …
Read the whole file at its exact version.
How to install
mdr add pjt222/agent-almanac/evolve-team@sha256:4075f90651a81fe3The line at the top of this page pins the label v1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ha7ftk3k7f2z2g72)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 8 versions of this file, between Apr 19, 2026 and Sep 15, 2026, about one every 21 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0 latest | 2026-09-15 | 2c29951 | 19,148 B | A | view · diff |
| v1.0 | 2026-09-15 | 2e0867a | 19,008 B | A | view · diff |
| v1.0 | 2026-09-15 | 854ad67 | 19,037 B | A | view · diff |
| v1.0 | 2026-08-17 | a784899 | 19,125 B | A | view · diff |
| v1.0 | 2026-06-05 | 33b561c | 19,096 B | A | view · diff |
| v1.0 | 2026-06-05 | 75ded7a | 19,088 B | A | view · diff |
| v1.0 | 2026-04-24 | 0b91b04 | 19,234 B | A | view · diff |
| v1.0 | 2026-04-19 | e334ebd | 19,313 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (19148 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
pjt222/agent-almanac · 43 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ha7ftk3k7f2z2g72 GET https://markdownregistry.com/api/v1/resolve?ref=pjt222/agent-almanac/evolve-team GET https://markdownregistry.com/api/v1/blob/4075f90651a81fe38dac88d5b13ad2f65a9fab800969614005799bb2cef8dc7d
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.