updating-service-skills

Detect implementation drift between service code and skill documentation.

4|1|Updated Nov 1, 2025
One-click install
npx skills add https://github.com/xtrm-dev/specialists --skill updating-service-skills
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: updating-service-skills
Source: https://github.com/xtrm-dev/specialists/tree/main/.xtrm/skills/default/updating-service-skills
Command: npx skills add https://github.com/xtrm-dev/specialists --skill updating-service-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill keeps expert persona documentation aligned with the actual codebase so skill instructions do not drift as implementation changes over time.

Core Features & Use Cases

  • Automatic Drift Detection: Triggers after write and edit operations to flag skills whose documented behavior no longer matches their territory.
  • Manual Sync Workflow: Helps you scan for drift, inspect the current skill definition, and update documentation to reflect new conventions, errors, or boundaries.
  • Registry-Aware Maintenance: Uses service territory definitions and sync timestamps to keep multiple expert skills organized and current across a project.

Quick Start

Ask the skill to scan for documentation drift in the repository and update the affected service skill so its instructions match the current implementation.

Frequently Asked Questions about updating-service-skills

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

FAQPage Schema
How do I detect documentation drift when service code changes?

Documentation drift is detected by triggering a scan after write and edit operations to flag skills whose documented behavior no longer matches their codebase territory. This tracks path ownership and last-sync timestamps to identify misaligned service instructions.

Can I manually scan and sync skill documentation to match my current codebase?

You can manually scan for drift, inspect the current skill definition, and update documentation to reflect new conventions. This sync workflow aligns expert persona instructions with the actual implementation boundaries and errors in evolving codebases.

How does PostToolUse hook integration work for skill synchronization?

PostToolUse hook integration applies a non-blocking advisory message pipeline to flag updated skills after write operations. It resolves path ownership and checks last-sync timestamps to trigger drift detection without interrupting the development workflow.

What is the best way to maintain multiple expert skills across a project?

Registry-aware maintenance uses service territory definitions and sync timestamps to organize multiple expert skills. By tracking path ownership and scanning for implementation drift, it keeps all service documentation current across the project.

Does this drift detection approach block my development workflow?

Drift detection uses a non-blocking advisory message pipeline to flag updated skills. It issues notifications about implementation drift without halting write or edit operations, ensuring the development workflow continues uninterrupted.