skill-maintainer

Synchronize AI skill definitions and documentation with evolving validation policies.

1|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill skill-maintainer-tsuji-tomonori
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-maintainer
Source: https://github.com/tsuji-tomonori/diopside-v3/tree/main/.opencode/skills/skill-maintainer
Command: npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill skill-maintainer-tsuji-tomonori

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that your AI skills and their associated documentation, validation rules, and execution procedures remain perfectly synchronized, especially when core documentation or validation policies change.

Core Features & Use Cases

  • Automated Skill Updates: Automatically updates SKILL.md and TEMPLATE.md files to reflect changes in documentation standards or document types.
  • Consistency Enforcement: Enforces consistent naming conventions, linking rules, and validation checks across all skills and related configuration files.
  • Use Case: When a new document type is introduced or a validation rule is updated in the docs/ directory, this Skill automatically propagates those changes to all relevant skills, ensuring the entire system remains coherent and functional.

Quick Start

Use the skill-maintainer skill to synchronize .opencode/skills with updated documentation and validation rules.

Frequently Asked Questions about skill-maintainer

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

FAQPage Schema
How do I synchronize AI skill definitions with updated documentation standards?

To synchronize AI skills with updated documentation, you apply this Skill to automatically update SKILL.md and TEMPLATE.md files to reflect changes in document types and validation policies. It enforces consistent naming conventions and linking rules across all related configuration files.

What happens to validation rules when a new document type is introduced in the docs directory?

When a new document type is introduced in the docs directory, the synchronization process automatically propagates those changes to all relevant skills. This ensures the entire system remains coherent and functional by updating execution procedures and validation scripts.

Do I need to manually update TEMPLATE.md files when operational guidelines change?

You do not need to manually update TEMPLATE.md files when operational guidelines change. The Skill enforces strict update flows for both SKILL.md and TEMPLATE.md files, automatically reflecting evolving documentation standards and validation policies.

How does skill maintenance enforce consistency across configuration files?

Skill maintenance enforces consistency by applying strict update flows for validation scripts and related configuration files. It ensures consistent naming conventions, linking rules, and validation checks across all skills when changes occur in the docs directory.

What is the best way to maintain system integrity when glossary terms change?

The best way to maintain system integrity when glossary terms change is to synchronize skills with the updated docs directory. This process applies strict update flows to SKILL.md, TEMPLATE.md, and validation scripts to keep the system coherent and functional.

Can I use this synchronization process for skills outside the .opencode directory?

This synchronization process is designed specifically for skills within the .opencode/skills directory. It targets SKILL.md and TEMPLATE.md files alongside validation scripts to maintain system integrity when documentation or validation policies change.