client-retire

Archive client-specific patterns and data as historical records.

3|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/martineserios/thebrana --skill client-retire
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: client-retire
Source: https://github.com/martineserios/thebrana/tree/main/system/skills/client-retire
Command: npx skills add https://github.com/martineserios/thebrana --skill client-retire

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps in systematically archiving client-specific data and patterns, ensuring that historical information is preserved without cluttering active knowledge bases.

Core Features & Use Cases

  • Pattern Archival: Identifies and archives client-specific patterns from memory databases or local files.
  • Confidence-Based Categorization: Differentiates between high-confidence, transferable patterns and those specific to a client, deciding their archival status.
  • Knowledge Preservation: Ensures no data is deleted, only tagged as historical, maintaining a complete record.
  • Use Case: When a client project concludes, use this skill to archive all associated learnings and patterns, marking them as historical for future reference.

Quick Start

Archive the client named 'Acme Corp' and its associated patterns.

Frequently Asked Questions about client-retire

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

FAQPage Schema
How do I archive client data and patterns when a project concludes?

Archiving historical client data works by identifying client-specific patterns in memory databases or local project files and tagging them with archival status and dates, ensuring active knowledge bases remain uncluttered while preserving a complete record.

Can I preserve transferable patterns while offboarding a client?

Yes, you can preserve transferable patterns during client offboarding because the archival process uses confidence-based categorization to differentiate between high-confidence, transferable patterns and client-specific data before applying historical tags.

Do I need a memory database to identify and tag historical client patterns?

You need access to either memory databases or local project files for pattern identification and tagging with archival status and dates, as the Skill requires these sources to systematically categorize and preserve historical client data.

What is the best way to manage knowledge preservation without deleting historical data?

The best way to manage knowledge preservation without deleting historical data is to tag client-specific learnings and patterns as historical, ensuring no data is deleted while keeping active knowledge bases free of concluded project clutter.

Does archiving client project learnings remove the information from my local files?

Archiving client project learnings does not remove information from local files; it systematically tags the data as historical to preserve a complete record while preventing concluded client patterns from cluttering active knowledge bases.