tool-record-maintenance

Maintain canonical Tool catalog records with evidence, relationships, and revision history.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/rickvang/Persona-Library --skill tool-record-maintenance-rickvang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tool-record-maintenance
Source: https://github.com/rickvang/Persona-Library/tree/main/.agents/skills/tool-record-maintenance
Command: npx skills add https://github.com/rickvang/Persona-Library --skill tool-record-maintenance-rickvang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Keeping a Tool or MCP catalog accurate is hard: records drift, duplicates appear, availability gets confused with capability, and history is lost during merges or retirements. This Skill governs add, update, relate, reconcile, audit, retire, and supersede operations on canonical Tool records while strictly separating catalog metadata from actual Tool execution. ## Core Features & Use Cases - Record lifecycle management: Add, update, relate, reconcile, audit, retire, and supersede Tool records with preserved revision history and rationale. - Evidence-aware status tracking: Distinguish observed, reported, proposed, reviewed, and unknown states so a catalog entry never falsely proves a connector or permission is configured. - Relationship integrity: Connect Tools to Personas, Skills, Playbooks, recipes, and replacements, reporting broken or ambiguous links instead of guessing. - Use Case: A librarian needs to merge two overlapping MCP tool entries. The Skill compares identity, scope, risk, and evidence, recommends supersession, preserves both histories, and hands off a change-impact reconciliation pass. ## Quick Start Use $tool-record-maintenance to audit this Tool record for missing capability, permission, and evidence fields without executing the Tool.

Frequently Asked Questions about tool-record-maintenance

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

FAQPage Schema
How do I update a Tool catalog record without losing history?▼

Update only the named fields while preserving the previous revision, rationale, evidence status, and affected relationships. The Skill prepares a change set listing additions, changes, and removals, then applies it only when explicitly authorized.

How to merge duplicate Tool or MCP records safely?▼

Compare stable identity, capability, scope, workspace, risk, evidence, and revision history before merging. If records differ materially, preserve both or recommend supersession rather than silently collapsing them, and never delete historical records.

Does a Tool catalog record prove the connector is available?▼

No. A catalog record describes capability, scope, and evidence but never proves a connector, credential, workspace, or permission is configured. Actual runtime availability checks are routed to the tool-discovery-and-safe-execution skill.

What happens when a record update request lacks authorization?▼

The Skill stays read-only and returns a proposed change set instead of writing. Missing target, authorization, or required metadata results in a report of the gap, not a guessed write.

When should a Tool record be retired instead of deleted?▼

Retire or supersede a record when it is obsolete or replaced, marking it with rationale, revision context, and replacement information when known. Historical records are never deleted so audit trails and relationships remain intact.