ops-direct-invoke-workflow-maintain

Guides safe modification of ops-direct-invoke workflow files, agents, skills, and init scripts.

Updated Sep 15, 2026
One-click install
npx skills add https://github.com/WangWindow/CANN-BatchMatMulMaxsum --skill ops-direct-invoke-workflow-maintain-wangwindow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ops-direct-invoke-workflow-maintain
Source: https://github.com/WangWindow/CANN-BatchMatMulMaxsum/tree/main/.agents/skills/ops-direct-invoke-workflow-maintain
Command: npx skills add https://github.com/WangWindow/CANN-BatchMatMulMaxsum --skill ops-direct-invoke-workflow-maintain-wangwindow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Modifying a multi-repository agent workflow (base repo plus operator repos linked via symlinks) risks breaking contracts, overriding the wrong layer, or desynchronizing linked components. This Skill enforces a mandatory pre-modification review process so every change to workflow files follows design constraints and compatibility rules. ## Core Features & Use Cases - Mandatory Trigger Gate: Any addition, modification, or deletion of workflow files (AGENTS.md, agents, skills, init.sh, or operator-repo overrides) must load this Skill first, including changes to the Skill itself. - Per-Target Modification Guides: Routes maintainers to dedicated references for editing workflow orchestration, pluggable plugins, virtual skills, fixed agents, or init scripts. - Contract & Compatibility Review: Provides a review checklist covering SOLID constraints, symlink consistency, plugin registration, silent-mode behavior, and backward compatibility of the distributed example/init.sh CLI contract. - Use Case: Before renaming a virtual skill in the base repo, load this Skill to verify the change against the contract compatibility clauses and run the post-modification self-check. ## Quick Start Before editing any workflow file, ask the AI to load the ops-direct-invoke-workflow-maintain skill and follow its modification guide for the target file type.

Frequently Asked Questions about ops-direct-invoke-workflow-maintain

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

FAQPage Schema
How do I modify the ops-direct-invoke workflow safely?

Load the ops-direct-invoke-workflow-maintain skill before any change. It routes you to the correct reference guide based on the target file type, then requires a self-check against the review checklist after editing.

How do I override a virtual skill in an operator repository?

Create the implementation under <repo>/agent/skills/<logical-name>/ with the same directory name and SKILL.md name field as the base skill. Then rerun the repo's agent/init.sh so the symlink binding switches to your override.

Can I change the init.sh CLI parameters of the base repo?

Only as an additive change. The distributed example/init.sh in operator repos depends on the existing CLI contract, so breaking changes require notifying users via a structured questionnaire and keeping backward compatibility for at least one release.

Why must the maintenance skill be triggered before editing workflow files?

Workflow source files span two repositories joined by symlinks, and edits can break logical-name contracts or override bindings. The skill enforces design constraints and post-change checks to prevent cross-repo breakage.

What happens if I add a new skill without rerunning init?

The new skill will not be symlinked into the runtime directory and agents cannot load it. The skill mandates rerunning the appropriate init script whenever skills or agents are added, deleted, or renamed.