trainer

Update SKILL.md and AGENTS.md files to reflect recent project changes.

18|3|Updated Jan 2, 2026
One-click install
npx skills add https://github.com/Niller2005/PolyFlup --skill trainer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trainer
Source: https://github.com/Niller2005/PolyFlup/tree/main/.opencode/skill/trainer
Command: npx skills add https://github.com/Niller2005/PolyFlup --skill trainer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains and synchronizes the Skills knowledge base with the latest project developments to keep documentation accurate.

Core Features & Use Cases

  • Monitors project changes and updates relevant .opencode/skill/*/SKILL.md files.
  • Documents new features, tools, or architectural patterns as skills.
  • Refines existing skill descriptions and manages AGENTS.md.

Quick Start

Review recent commits and update the relevant .opencode/skill/*/SKILL.md files to reflect the latest project changes.

Frequently Asked Questions about trainer

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

FAQPage Schema
How do I keep project documentation synchronized with recent code commits?

Synchronize project documentation with recent code commits by reviewing commit history and updating SKILL.md files and AGENTS.md to reflect new features and architectural patterns.

What is the best way to automate knowledge base updates when features evolve?

Automate knowledge base updates by monitoring project changes and applying defined workflows to update SKILL.md files, ensuring documentation stays accurate as features and patterns evolve.

How do I document new architectural patterns as skills in an existing knowledge base?

Document new architectural patterns by adding entries to relevant .opencode/skill/*/SKILL.md files and refining existing skill descriptions to capture the latest project developments.

Do I need any external dependencies to maintain SKILL.md files across all skills?

No external dependencies are required to maintain SKILL.md files. The workflow operates independently to monitor changes, review commits, and apply updates across all skills.

Why does my project knowledge base have outdated skill descriptions after recent changes?

Outdated skill descriptions occur when commits introducing new tools or patterns are not followed by updates to the corresponding SKILL.md files and AGENTS.md documentation.

When should I update AGENTS.md instead of individual SKILL.md files?

Update AGENTS.md when managing broader agent instructions across all skills, while individual SKILL.md files should be updated to document specific features or architectural patterns.