quark-torch-skill-sync

Detects upstream Quark changes that invalidate skill instructions or contracts.

154|27|Updated Jun 19, 2024
One-click install
npx skills add https://github.com/amd/Quark --skill quark-torch-skill-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quark-torch-skill-sync
Source: https://github.com/amd/Quark/tree/main/.claude/skills-impl/meta/torch/quark-torch-skill-sync
Command: npx skills add https://github.com/amd/Quark --skill quark-torch-skill-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintainers detect when upstream Quark changes have made existing skill instructions outdated, inconsistent, or incorrect.

Core Features & Use Cases

  • Source Drift Auditing: Compares skill assumptions against Quark source files and documentation.
  • Update Classification: Labels changes as mechanical, semantic, or breaking so teams know what can be safely updated and what needs review.
  • Maintenance Use Case: Use it after a Quark upgrade to identify new quantization schemes, changed model support, renamed flags, or removed APIs before users get bad guidance.

Quick Start

Ask the Skill to audit the current Quark repository and report which skills need updates.

Frequently Asked Questions about quark-torch-skill-sync

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

FAQPage Schema
How do I detect upstream changes that break existing Quark quantization templates?

Run a maintenance audit against the current Quark repository to verify source file dependencies and compare them against skill assumptions. This classifies drift as mechanical, semantic, or breaking.

What is source drift auditing for Quark skill maintenance?

Source drift auditing compares existing skill instructions against current Quark source files and documentation. It identifies when upstream changes to docs, CLI flags, or export behavior make previous guidance outdated or incorrect.

How do I check if a Quark upgrade removed APIs or renamed CLI flags?

Run a maintenance audit on the Quark repository to verify source file dependencies. This identifies removed APIs, renamed CLI flags, and changed model support by comparing current implementation details against skill assumptions.

Can I use this audit to verify new quantization schemes after a Quark upgrade?

Yes, you can run a maintenance audit after a Quark upgrade to identify new quantization schemes and changed model support. This verifies export behavior and source dependencies before users receive outdated guidance.

What is the difference between mechanical, semantic, and breaking drift in Quark skills?

Breaking drift invalidates skill contracts and requires manual review, while semantic drift changes instruction meaning and mechanical drift allows safe updates. This classification helps teams prioritize maintenance after upstream Quark changes.