myco:skill-reference-and-manifest-drift-maintenance

Regenerates and validates generated tool manifests and skill reference docs in unifi-mcp apps.

777|101|Updated Apr 21, 2025
One-click install
npx skills add https://github.com/sirkirby/unifi-network-mcp --skill myco-skill-reference-and-manifest-drift-maintenance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: myco:skill-reference-and-manifest-drift-maintenance
Source: https://github.com/sirkirby/unifi-network-mcp/tree/main/.agents/skills/skill-reference-and-manifest-drift-maintenance
Command: npx skills add https://github.com/sirkirby/unifi-network-mcp --skill myco-skill-reference-and-manifest-drift-maintenance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generated artifacts in the unifi-mcp monorepo — per-app tool manifests (tools_manifest.json) and plugin skill reference docs with AUTO:tools markers — silently drift from the Python source because CI drift-checks only verify already-rendered content, never missing sections, markers, or stale descriptions. This Skill provides the checklists and procedures to keep those generated artifacts correct.

Core Features & Use Cases

  • Regeneration discipline: Regenerate manifests after any docstring, parameter, or behavior change and diff for content parity, not just field presence.
  • New tool category checklist: Add ToC entries, AUTO:tools:<category> marker blocks, and run the generator so new categories are actually discoverable in reference docs.
  • Merge conflict resolution: Resolve generated-manifest merge conflicts by regeneration from merged source, never by hand-editing the diff.
  • Dormant drift detection: Catch pre-existing documentation gaps surfaced when an unrelated PR trips the reference-check CI gate.
  • Use Case: A contributor adds a new tool category to apps/protect; this Skill ensures they add the ToC entry and AUTO markers, run the generator in a locked-dependency venv, and verify the section is populated before merge.

Quick Start

Use this skill to regenerate the tool manifest and skill reference docs after my changes to the network app's tool docstrings, and check for any missing AUTO:tools sections.

Frequently Asked Questions about myco:skill-reference-and-manifest-drift-maintenance

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

FAQPage Schema
How do I regenerate the tool manifest after changing a tool docstring?

Run the affected app's make manifest target (or make generate at the repo root for all apps) inside a venv synced to locked dependencies. Then diff the regenerated manifest for content parity with the docstring, not just field presence.

How do I add a new tool category to the skill reference docs?

Add a ToC entry and a section with AUTO:tools:<category> marker comments in the plugin's reference file, then run the generator and confirm the section is populated. Bumping the tool count alone leaves the new tools undiscoverable.

Why does CI pass even when my new tools are missing from the reference docs?

The drift-check only diffs already-rendered content against disk for markers that exist. A PR that skips the ToC entry and AUTO markers passes cleanly because there is nothing rendered to compare — this gap must be caught in review.

How do I resolve a merge conflict in tools_manifest.json?

Never hand-resolve it. Accept the conflicted merge, regenerate the manifest from the merged Python source using the app's make manifest target in a locked-dependency venv, and stage the regenerated file.

Why did an unrelated PR suddenly fail the reference-check CI gate?

The gate only fires when generated files change in the current PR, so drift from an earlier PR can sit dormant until another change touches the same files. Bundle the missing section and markers fix into the triggering PR and regenerate.