skill-harmonization

Topics in the source

• Skill Harmonization
• Input and Prerequisites
• Authority and Mode
• Build the Portfolio
• Evidence Boundary
• Analyze Repository-Centered Relationships
• Externally Managed User Installations
• Classify Every Material Finding

If a slash or dollar invocation already supplied these instructions, follow them directly. In that case, do not invoke this skill again through a skill tool. Treat the current Git repository and relevant user-installed skills as one repository-centered portfolio. Inventory it mechanically. Distinguish defects from judgment calls and deliberate relationships. Then report, plan, or implement according to the invoking task's authority. Success means every repository skill was considered against relevant repository and user candidates. Every conclusion has path and client evidence. Observations remain separate from inference. The selected mode ends with appropriate findings, recommendations, validation, and deliberate no-change conclusions. [task] is optional free-form guidance. Use it to narrow the question, desired outcome, or authorized implementation scope. If it is absent, infer intent from the surrounding request. An invocation without write intent is read-only. 1. Require ai-skillet 1.0.0 or newer on PATH. If it is unavailable or too old, stop and ask the user to install or upgrade it. 2. Require git on PATH, then resolve the current repository with git rev-parse --show-toplevel

This is an excerpt. Refer to the complete source and its current requirements.