playbooks

home / skills / laurigates / claude-plugins / meta-assimilate

meta-assimilate skill

/agent-patterns-plugin/skills/meta-assimilate

This skill analyzes and assimilates project Claude configurations to enhance user scoped agents and commands by generalizing and integrating them.

npx playbooks add skill laurigates/claude-plugins --skill meta-assimilate

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
566 B
---
model: opus
created: 2025-12-16
modified: 2025-12-16
reviewed: 2025-12-16
allowed-tools: Read, Write, Edit, MultiEdit, Glob, Grep, TodoWrite
argument-hint: <project-path>
description: Analyze and assimilate project-specific Claude configurations
name: meta-assimilate
---

# Assimilate Command

Examine the .claude/{agents,commands} of the project at path [path] and think deep if we could make use of them in the user scoped agents and commands. Either by copying and generalizing or assimilating into existing agents or commands if similar ones already exist.

Overview

This skill analyzes a project's .claude/agents and .claude/commands to determine which user-scoped Claude agents and commands can be reused, generalized, or assimilated. It proposes concrete actions: copy, adapt, or merge configurations into existing agents and commands to reduce duplication and improve consistency. The result is a prioritized plan for integrating project-specific behaviors into the user's agent set.

How this skill works

The skill inspects the project's .claude/{agents,commands} directory, parsing metadata, prompts, and invocation patterns. It compares discovered items against the user's current agents and commands, identifying exact matches, near-duplicates, and candidates for generalization. For each candidate it recommends whether to copy untouched, refactor into a generalized template, or merge into an existing agent/command with minimal changes.

When to use it

  • Onboarding a new project that includes .claude agents or commands you might want to reuse.
  • Consolidating duplicated or similar Claude configurations across multiple projects.
  • Auditing project-specific agents before sharing or open-sourcing a repository.
  • Preparing a standardized, user-scoped agent library from varied project configs.

Best practices

  • Run the analysis early to avoid diverging agent behavior across projects.
  • Favor small, well-documented generalizations rather than large, monolithic agents.
  • Keep original project configs intact until assimilation changes are validated.
  • Annotate merged or generalized agents with provenance and rationale.

Example use cases

  • Detecting a project-specific code-review agent and converting it into a reusable review template.
  • Finding many near-duplicate deployment commands and merging them into a single parameterized command.
  • Spotting outdated prompt phrasing in project agents and standardizing language across user agents.
  • Creating a prioritized checklist of candidates to assimilate for a developer onboarding sprint.

FAQ

Will this change project files automatically?

No. The skill produces recommendations and a plan. Changes should be applied after review and testing.

How does it decide between copying and generalizing?

It weighs similarity, parameterizability, and reuse potential; exact matches are copied, repeatable patterns are generalized, and overlapping functionality is merged.