archivist

Convert recurring knowledge into codified project rules under .agents/rules.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ericklemos/ai-tools --skill archivist-ericklemos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archivist
Source: https://github.com/ericklemos/ai-tools/tree/main/.agents/skills/archivist
Command: npx skills add https://github.com/ericklemos/ai-tools --skill archivist-ericklemos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Recurrent knowledge and proven patterns often remain implicit, causing teams to reinvent solutions and lose context.

Core Features & Use Cases

  • Converts recurring knowledge into durable project rules stored in .agents/rules.
  • Preserves decisions to prevent repeat mistakes and accelerate onboarding.
  • Enables cross-agent knowledge alignment by codifying patterns and constraints.

Quick Start

Transform a known recurring pattern into a formal rule to capture it for future use.

Frequently Asked Questions about archivist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert recurring project knowledge into durable engineering rules?

You can codify undocumented patterns into actionable project rules by storing them under the .agents/rules directory. This prevents repeat mistakes and accelerates team onboarding by preserving proven decisions.

What is the best way to retain implicit engineering knowledge for future projects?

The best way to retain implicit engineering knowledge is codifying proven patterns into durable project rules. This achieves cross-agent knowledge alignment and preserves decisions to stop teams from reinventing solutions.

How do I set up the SKILL.md file for project automation and memory management?

To set up project automation, create a SKILL.md file with YAML frontmatter containing a name and description. You can optionally add scripts, references, and assets directories to support the codified rules.

Does codifying project rules work for cross-agent knowledge alignment?

Codifying project rules enables cross-agent knowledge alignment by converting recurring knowledge into actionable constraints. All agents operate under the same patterns stored in the shared .agents/rules directory.

When should I avoid codifying team workflows into project rules?

Avoid codifying team workflows into project rules when the knowledge is not recurrent or proven. Codifying one-off solutions or non-recurring context adds unnecessary constraints without providing durable project value.